John McKown wrote >How do you do that? I looked in the book for 1.12. I remember from long ago a >bit to set to suppress the ENQ on the userid ( SYSIKJUA <id> ). But I cannot >find that bit in the documentation.
Are you refering to this entry in GRSRNLxx member? RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSIKJUA) RNAME(<tso id>) This is to ENABLE concurrent TSO logon with same id on several LPAR. Mark Zelden has a page about this on his webpage. Also see in TSO/E Customization v1.12, these snippets about 'SYSIKJUA' and 'reconnection': TSO generic resource support: Reconnection support ensures that a user's address space is kept for a specified reconnect interval after a TSO user loses connectivity to the TSO system. During this interval, if the user tries to reconnect, he will be automatically reconnected to the system, application, and address space that he originally had. Preventing duplicate logons: 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. Of course we ENABLED duplicate logons due to practical reasons. I wish I have Mark's address for his webpage about this... Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
