The only technical reason I know of to manage the SDSF console name is avoid conflict with another product. In our case SMCS (native VTAM function) is set up to employ userid as the console name. So in SDSF I take my six-character userid and append SYSCLONE on each system. Only need to do it once because it's remembered. It's guaranteed to be unique and easily identifiable.
I would raise holy hockey sticks if someone generated a random and therefore untraceable console name. . . 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] From: Jon Perryman <[email protected]> To: [email protected], Date: 10/04/2013 11:37 AM Subject: Re: SET CONSOLE every time you invoke SDSF ULOG Sent by: IBM Mainframe Discussion List <[email protected]> When you set a console name value, it is saved to the profile and becomes the default. My guess is that you aren't running your exec and just seeing the last console value set by your exec. Don't set the console to a random value. You won't be able to see who issued commands in the system log. Security is difficult to create for it. My suggest is to use ISPF variables &ZUSER and &ZSCREEN. You don't need an exec. Just modify the command to PARM(SET CONSOLE &ZUSER.&ZSCREEN) Jon Perryman. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
