Technical issues notwithstanding, I would suggest that the behavior was driven (at least in part) by audit demands that multiple logons with a single ID be blocked to prevent users from sharing ID's.
Giving one user multiple ID's is also perceived to be a sharing ID risk. I guess the audit approved path would be to require the user to sign on, perform the task, then sign off. Indeed, our last audit looked at inactivity time outs. -----Original Message----- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Don Williams Sent: Friday, April 23, 2010 10:15 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Multiple logon SMCS possibility Several years ago, I asked IBM why they prohibit users from concurrent sign-on to multiple consoles, and was told that it is working as designed. He noted that I was not the first to complain. I hope that IBM will change their design and allow users to sign-on to multiple consoles. Until then, you'll have give users multiple ids to circumvent that restriction. In many shops that means you'll have to get a security policy waiver before assigning multiple ids to the same person. NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
