On 6/3/2015 9:58 AM, Thomas Conley wrote:
On 6/3/2015 4:36 AM, Lucas Rosalen wrote:
Hey Tom,
Read your article. VERY nice I must say!
I know this is from 2012, so I guess now with z/OS 2.1 the issue below
has
been fixed, right? Now each ULOG session has its own ID if I recall it
correctly....
" SDSF also has an issue with multiple logon. A user logged on to SYSA
goes
into SDSF LOG/ULOG, then logs on to SYSB and enters SDSF LOG/ULOG. If the
user issues a command on SYSB from SDSF, the command response won’t
appear
in the SYSB LOG/ULOG; it appears in the SYSA ULOG. By default, SDSF sets
the Extended Multiple Console Support (EMCS) console id to userid, so all
command output is routed to the system first establishing the console
id."
Regards and keep up the good job!
On Jun 1, 2015 4:06 PM, "Thomas Conley" <[email protected]>
wrote:
Lucas,
Thanks for your kind words. We did a lot of work on multiple logon, so
it's nice to know it's paying off. Thanks also for pointing out that
this has been fixed in SDSF. I just researched this because I didn't
know for certain that SDSF added this feature in z/OS V2R1. It's called
console name modification, and if ULOG senses that the console name,
typically user id, is already in use, it will add characters until it
finds a unique console id. This feature removed the last inhibitor to
multiple logon.
Regards,
Tom Conley
Point of clarification, this only works for console id's of 7 characters
or less. If you have an 8-character console id, that id will be used
for all your SDSF sessions. If you clear the console id or set it to
your user id, you should get the console name modification.
Regards,
Tom Conley
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
