Absolutely. My logon proc contains this: //ISPPROF DD DISP=SHR,DSN=TSOSKIP.$SYS&SYSCLONE..ISPPROF
This DD resolves correctly on each member of the plex. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jake Anderson Sent: Thursday, July 14, 2016 9:27 AM To: [email protected] Subject: (External):Re: Already logged on message - Wrong System ID Hi, It is a system wide defaults they have set and I am not sure if I can modify. So from a Userid individual perspective. Can i control my ISPFPROF allocation by having &SYSNAME ? On Thu, Jul 14, 2016 at 9:50 PM, Jesse 1 Robinson <[email protected]> wrote: > During the course of setting up z/OSMF 2.1/2.2, I learned that there > is now an option to actually share a single profile dataset. This is > needed for z/OSMF ISPF interface where the web access would otherwise > clash with the same user logged on to TSO on the same system. This of > course introduces the risk of dueling updates. I prefer to keep > separate profile data sets on each system because some settings may > differ, but the same feature should allow sharing the profile among systems. > > The controlling option is SHRPROF. It can be specified on entry to ISPF: > ISPF SHRPROF options , including > > <RESET> > <WAIT <n>> n: 0 to 9999 > <RETRY <n>> n: 0 to 99 > <PROMPT|NOPROMPT> > <CONFLICT SYSTEM|ISPF|APPLID|REFLIST|EDIT|BATCH|OTHER > <KEEP|DISCARD|PROMPT>> > > Or SHRPROF can be made permanent for all users. Aside from z/OSMF, > whether a profile data set is actually shared depends on the allocation. > . > . > . > J.O.Skip Robinson > Southern California Edison Company > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 323-715-0595 Mobile > 626-302-7535 Office > [email protected] > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Lizette Koehler > Sent: Thursday, July 14, 2016 8:46 AM > To: [email protected] > Subject: (External):Re: Already logged on message - Wrong System ID > > What level of z/OS? > > If you create unique ISPF Datasets for things like PROFILE You look at > IKJTSOxx in SYS1.PARMLIB for LOGONHERE You make sure you have SHR On > those files that can be shared between LPARs in a plex. > > And review the TSO Customization manual for logging on to more than > one system in a Sysplex, > > You should be able to logon to multiple LPARs in a plex. > > I can do this successfully in a 5 member plex. I can log on to all > systems but the datasets that need to be unique are unique. > > > It always helps to fully explain your problem you are trying to solve, > rather than make the list guess as to your true issue. > > Lizette > > > > > -----Original Message----- > > From: IBM Mainframe Discussion List > > [mailto:[email protected]] On Behalf Of Jake Anderson > > Sent: Thursday, July 14, 2016 6:53 AM > > To: [email protected] > > Subject: Re: Already logged on message - Wrong System ID > > > > Hi Liz, > > > > "Did you logon to LPAR2 and forget to logoff when you tried to > > logon to LPAR1?" > > > > > > You are correct.. So this become a pain when we try to logon other > > LPARs in sysplex without being aware of Our ID logged on to the > > other > System. > > > > On Thu, Jul 14, 2016 at 7:01 PM, Lizette Koehler > > <[email protected]> > > wrote: > > > > > 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
