Well, it's Friday night and I'm trying to watch Burn Notice. On one member
of my 1.9 sandbox sysplex, I see this:
ISG343I 18.52.17 GRS STATUS FRAME LAST F E SYS=B0
S=SYSTEM SYSIKJUA ROBINSS
SYSNAME JOBNAME ASID TCBADDR EXC/SHR STATUS
B0 0090 00AFFB00 EXCLUSIVE OWN
Because we exclude--or rather don't include--SYSIKJUA in the conversion to
SYSTEMS scope, I can logon to other members of this sysplex with the same
userid. We also tell JES2 to allow multiple TSO logon, but the whole
solution requires both GRS and JES2 changes. Plus accommodations for
conflicting data sets.
If I'm wrong, I owe Ted a drink at SCIDS--from the CASH bar!!!
Ted MacNEIL
<[EMAIL PROTECTED]
CA> To
Sent by: IBM [email protected]
Mainframe cc
Discussion List
<[EMAIL PROTECTED] Subject
.EDU> Re: Stupid Question of the day.
06/20/2008 04:52
PM
Please respond to
IBM Mainframe
Discussion List
<[EMAIL PROTECTED]
.EDU>
>One impediment to multiple logon is the enqueue on QNAME(SYSIKJUA). You
can enable multi-system logon by blocking propagation of that enqueue to
other
members of a sysplex.
It's a simple parm under JES2.
You don't have to worry about ENQ's for the SYSIkJUA, rather just with the
allocated DSNs.
-
Too busy driving to stop for gas!
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
