Jake, Some additional details will help Are you using a session manager? Are you logging on with an APPL (LOGON APPL(xxxx) ) command?
Have you verified your definitions for the two lpars are set up correctly? Did you code LPAR1 Appl for LPAR2 and so forth? Please provide a display of your session definitions for TSO D NET,ID=xxxxxxxx,E You need to make sure all of your connection definitions are correct first before looking to MIM. I am not aware of how MIM might affect a logon. A Session manage could affect your logon. If all connections are correct, then check how your TSO environment is set up. Are your ISPF datasets (like PROFILE) unique? Do you have a logon CLIST/REXX that allocates unique files? Did you logon to LPAR2 and forget to logoff when you tried to logon to LPAR1? Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Jake Anderson > Sent: Thursday, July 14, 2016 4:38 AM > To: [email protected] > Subject: Already logged on message - Wrong System ID > > Hello, > > I am trying to access one of an LPAR1 within a sysplex. Where I get a message > as you already logged on to LPAR1. When I have someone to check my ID from > other system its shows that My ID is active in LPAR2. > > We have MIM but we have not enabled Parallel Logon facility serialization. > > I am curious why z/OS is displaying a wrong System Name instead of the One my > ID is active ? > > Its like I am logged into LPAR2, but when I try accessing LPAR1, it shows that > you are already logged on to LPAR1.. > > This gets resolved after My ID is cancelled from LPAR 2. > > Are there any EXITS or REXX which can tell me the correct System Name when I > try to logon to other LPAR within the same sysplex(Shared RACF and no MIM > serialization). > > Did any of you face this kind of situation and found a remedy ?(Here in our > MIM serialization for IKJUA IS not allowed) > > > > Jake > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
