Thanks Tom. I suspected that my answer was out of date. On each of our systems, I have had a unique console id for so long that the 'undefined default' never occurs any longer.
For those who make use of the VTAM console application SMCS, similar issues exist. By default, SMCS adopts the operator's userid as a console id. This may clash with SDSF. Furthermore, SMCS cannot be run concurrently on multiple member of the same sysplex unless a non-default console id is specified. Despite this limitation, I like SMCS a lot. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Tom Conley Sent: Tuesday, May 25, 2021 1:39 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: MVS command display *** EXTERNAL EMAIL - Use caution when opening links or attachments *** On 5/25/2021 3:43 PM, Jesse 1 Robinson wrote: > SDSF uses extended consoles to manage command output. A given console and be > active on only one system at a time. If you have a MAS, output from a command > issued on one member may well appear on another system. If you have only one > member in your SDSDF plex, then never mind. Otherwise: > > 1. Logon to one system. > 2. Get into SDSF. > 3. Issue SET CONSOLE ? > 4. You will see this something like this (sorry for the screwy > formatting) > +------------------------------------------------+ > | Set Console Name | > | | > | Type a console name or leave blank to use | > | your user ID as the console name. | > | | > | Extended console name your-userid | > | | > | | > | F1=Help F12=Cancel | > +------------------------------------------------+ > > Repeat this procedure on all sharing systems. The default name is your userid > id. On multiple systems, the id may be identical on all sharing systems. If > the ids are identical, a command issued on one system will display on > whichever system initialized first. You can set the console id on each system > to (more or less) anything you want. As long as the id is unique, a command > will be responded to on the system where it's issued. > FYI, SDSF fixed this situation a long time ago. It is supposed to detect that a console id in a sysplex is already in use, and create a unique console id for the sysplex. If it can't create a unique console id, you're supposed to get an error message. If this is really your problem, you should open a case to have Rocket fix this. Regards, Tom Conley ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
