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. I don't see how you could block recognition of that
enqueue on a single system. This enqueue represents the individual TSO user
instance and has nothing to do with data set allocation.
.
.
JO.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
[EMAIL PROTECTED]
Doug Henry
<[EMAIL PROTECTED]
K.COM> To
Sent by: IBM [email protected]
Mainframe cc
Discussion List
<[EMAIL PROTECTED] Subject
.EDU> Re: Stupid Question of the day.
06/20/2008 01:53
PM
Please respond to
IBM Mainframe
Discussion List
<[EMAIL PROTECTED]
.EDU>
On Fri, 20 Jun 2008 15:20:09 -0500, Eric Bielefeld <eric-
[EMAIL PROTECTED]> wrote:
>we had a sysplex. I wondered why
>my ISPF profile dataset was different, and the other sysprog there
explained
>to me about the enque, which for the profile DS is DISP=OLD. You have to
>write the logon exec or clist to take into account the system it is on,
and
>allocate a name that's different on each system.
One of the enhancements with z/OS 1.9 is " Users are able to share ISPF
profiles across different systems in the same sysplex".
Doug
----------------------------------------------------------------------
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
