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 auditor ask us why we do this. I don't know what productivity is >gained by our applications programmers who use both, but I know we systems >guys sometimes need to reply to a console message from one session to free up >another session.
I had a systems programmer-id plus an applications id so that I could test to make sure that an applications programmer had all the appropriate access and only that access. I can see two or more ids for applications programmers to they can properly test their applications from a user point of view. Clark Morris > >Greg Shirey >Ben E. Keith Company > > > >-----Original Message----- >From: IBM Mainframe Discussion List [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 less reliable than today's virtual arrays, It was >a dreadfully monotonous occurrence for a DASD failure to hang up a system >or an entire shared complex. A TSO user could easily get hung up trying to >untangle the mess. A unencumbered second userid could sometimes be used to >dig into the rubble for search and rescue. Modern DASD as well as robust >RAS improvements have made that scenario increasingly rare. With >multi-plex logon now SOP, I no longer maintain multiple userids. > >Note also that 'accountability' is in no way compromised by multiplicity >as long as each userid has one and only one owner. The state has no >problem with a person owning multiple vehicles, while the practice of a >vehicle being owned jointly by lots of people would cause havoc in the >insurance marketplace. > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
