:30 PM
Subject:Accountability (was: multiple TSO Sessions (try this))
Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU
Ted MacNEIL wrote:
Unique mapping of userid to person is a valid issue.
You must be accountable for what you do.
Sharing of ids negates
jo.skip.robin...@sce.com
From: Elardus Engelbrecht elardus.engelbre...@sita.co.za
To: IBM-MAIN@LISTSERV.UA.EDU,
Date: 01/29/2014 10:30 PM
Subject:Accountability (was: multiple TSO Sessions (try this))
Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU
Ted
, 2014 9:38 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Accountability (was: multiple TSO Sessions (try this))
There was a time when I promoted (at least) two userids for system support
folks. SLED DASD was far less reliable than today's virtual arrays, It was
a dreadfully monotonous occurrence
[mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Skip Robinson
Sent: Thursday, January 30, 2014 9:38 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Accountability (was: multiple TSO Sessions (try this))
There was a time when I promoted (at least) two userids for system support
folks. SLED DASD was far
On Thu, 30 Jan 2014 14:35:19 -0400, Clark Morris wrote:
On 30 Jan 2014 09:55:32 -0800, in bit.listserv.ibm-main you wrote:
Every single TSO user in my shop is assigned two ID's. No one has ever asked
for a third, but many people only use one of their assigned ID's. We have
never had an
Ted MacNEIL wrote:
Unique mapping of userid to person is a valid issue.
You must be accountable for what you do.
Sharing of ids negates that.
Indeed. As an unpopular RACF guy, I have a battle just about this. :-)
Subsequent audit trails proved my and your point.
It is not about 'I must win', but
