Forget the part about STEP level ENQ. All ENQs are done by the CONSOLE address space, and so STEP is not relevant.
-- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets® 9151 Boulevard 26 • N. Richland Hills • TX 76010 (817) 255-3225 phone • [email protected] • www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets® is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. –The Chesapeake Life Insurance Company®, Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of McKown, John > Sent: Thursday, September 13, 2012 12:41 PM > To: [email protected] > Subject: Re: Console LOGON and SYSPLEX > > I did a command that I have which lists ENQ information. I found an > entry like: > > Qname=SYSZCNZ > Rname=USERID#????????|consname| > Jobname=CONSOLE (which was the name of the z/OS SMCS console the user > was logged on to) > Type=EXCL (Exclusive) > Status=OWNED > Scope=SYSPLEX > > Where the ??????? is 8 character RACF id (padded with blanks if > necessary) and the "consname" is the name of the console. > > This certainly looks like it could be the ENQ done by console support. > You could change the scope from SYSPLEX to SYSTEM via the GRS RNL, or > even to STEP to allow the same user onto multiple consoles on a single > system image. However, I wonder if this is wise. I don't know why the > scope is SYSPLEX and not SYSTEM or even why it is issued. It may be > that the USERID logged on my be used in other parts of the system and > is assumed to be unique within the SYSPLEX. If so, who knows what would > happen if you change this ENQ? > > from SG247605, section 27.1.1 > <quote> > The new console data structures no longer require sysplex-wide > serialization to make most updates. The system on which a console is > active owns the data, and will hold ENQ SYSZCNZ CONNAME#consname. The > other systems may not display the newest data. > </quote> > > So, there may be data structures in the CONSOLE address space which are > dependent on this ENQ be SYSPLEX-wide. Or, perhaps, it is a way for > z/OS to "know" which system is actually controlling a specific console. > I'm a bit confused by this because, in a SYSPLEX, the console names > must be unique. And the ENQ for the USERID#... has the console id in > it. So why does console to a "generic" ENQ search, ignoring the console > name. In the words of Vinnie Babarino: "I'm so confused!" (John > Travolta in "Welcome Back Kotter"). > > -- > John McKown > Systems Engineer IV > IT > > Administrative Services Group > > HealthMarkets® > > 9151 Boulevard 26 • N. Richland Hills • TX 76010 > (817) 255-3225 phone • > [email protected] • www.HealthMarkets.com > > Confidentiality Notice: This e-mail message may contain confidential or > proprietary information. If you are not the intended recipient, please > contact the sender by reply e-mail and destroy all copies of the > original message. HealthMarkets® is the brand name for products > underwritten and issued by the insurance subsidiaries of HealthMarkets, > Inc. –The Chesapeake Life Insurance Company®, Mid-West National Life > Insurance Company of TennesseeSM and The MEGA Life and Health Insurance > Company.SM > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] > > On Behalf Of Juan Mautalen > > Sent: Thursday, September 13, 2012 11:46 AM > > To: [email protected] > > Subject: Console LOGON and SYSPLEX > > > > Hi: > > > > We have 2 Lpars in sysplex (z/OS 1.11), say LparA and LparB. Consoles > > are configured with LOGON(OPTIONAL) on both systems. Each system has > > its own RACF database. > > > > If an operator is already logoned to an LparA console and tries to > > logon to an LparB console, then logon fails with the following > message: > > > > CNZ0005I LOGON REJECTED. REASON=USERID ABC123 IN USE ON SYSTEM SYSA > > CONSOLE MSTRSYSA > > > > Is this normal behaviour? > > Is there any configuration change that can be made to allow the same > > operator to logon to consoles on both systems at the same time? > > > > Thanks in advance for your help, > > > > JUAN MAUTALEN > > > > --------------------------------------------------------------------- > - > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: INFO IBM- > MAIN > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
