More accurately, single ID, single LPAR, single application, multiple session facility.
That is an application issue. E.g., we have two TORs using a single AOR/FOR pair. For some transactions we disallowed using both AORs at the same time in the transaction's security signon part because the transaction was not sophisticated enough to build temp storage queue names to distinguish simultaneous signins (and related issues). And it was deemed not worth the effort to correct that. For TSO and whatever TCAS is called now, the issue becomes having the address space name created be different from the userid. What would that break? To have the session manager handle that wrinkle using e.g. morphing the userid used at signon and then having the security system or application handle the authorization via unmorphing the userid is messy. btdtgt-scars. I am reminded of the old commercial with the tag line "It's not nice to fool mother nature." IBM Mainframe Discussion List <[email protected]> wrote on 06/13/2007 12:45:27 PM: > Do session managers in any way alleviate the problem of DDNAME > collisions? Do multiple IDs cause concern to security auditors? > I still wish for the advent of the single ID single LPAR multiple > session facility. > -- gil ----------------------------------------- The information contained in this communication (including any attachments hereto) is confidential and is intended solely for the personal and confidential use of the individual or entity to whom it is addressed. The information may also constitute a legally privileged confidential communication. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this communication in error and that any review, dissemination, copying, or unauthorized use of this information, or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. Thank you ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
