On Wed, 29 Aug 2012 08:06:59 -0500, Elardus Engelbrecht wrote:
>
>In z/OS V1R4, JES2 stopped preventing duplicate TSO/E logons. As a result,
>duplicate instances of a given userid could logon at the same time to
>different systems in the same JES2 MAS, depending on system settings. For
>example, this can occur if the SYSIKJUA enqueue is set to scope SYSTEM in a
>sysplex. Steps must be taken to prevent duplicate logons. Otherwise:
>
>- Users might not receive all messages or notices.
>- Logon reconnect after disconnect can fail.
>- Applications such as ISPF could break.
>- Other unexpected results could occur.
>
Most of this is due to IBM's not properly distinguishing between a
session ID and a user ID and ought to be fixed. A conspicuous
example is misdirection of notifications of completion of HSM
background requests.
>Of course we ENABLED duplicate logons due to practical reasons. I wish I have
>Mark's address for his webpage about this...
>
http://www.mzelden.com/mvsutil.html
(GIYF. And it's in his .sig) Lots of neat stuff; much of it reflected on
cbttape.org.
But I don't see mention of multiple LOGONs. IIRC, he's discussed it here. But
see:
http://www.mzelden.com/mvsfiles/$sngltso.txt
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
