> -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Paul Gilmartin > Sent: Tuesday, December 27, 2011 2:05 PM > To: IBM-MAIN@bama.ua.edu > Subject: Re: Eight-character TSO Userid Support > > On Tue, 27 Dec 2011 10:42:02 -0800, Donald Zeunert wrote: > > >Re: Eight-character TSO Userid Support > > > >One item that has not been mentioned. The 7 char TSO userid > was so that when you submit batch jobs it automatically > appended 1 char to make a unique jobname to execute. If your > TSOID is 8 then and you submitted a batch job it would either > have to have > 8 char jobname, same and you'd have to logoff > for it to run, or something not associated w/ your userid > which would require SDSF or 3rd party spool product RACF > (SAF) rules to allow you to view it. If jobname becomes > 8 > that impacts lots of SMF records, RACF(SAF) rules, and lets > not forget the 80 character punch card limitation for those > pushing for 24 char userids. I know some sites already use > TSO batch job names w/o TSOID prefix, but these are still 8 > char names that need to be unique. > > > This topic entirely mystifies me. I'm looking at the SDSF > STATUS display which > shows me 123 of my jobs (I need to clean up). Of these, 110 > do _not_ begin > with my userid, including one which I just submitted with the > SUBMIT primary > command from an ISPF VIEW panel. 13 do begin with my user > ID, including > my TSO session and several that I recall submitting other > than from a TSO/ISPF > SUBMIT command. > > I don't know why people entertain this fantasy of a UserID+1 > job name rule > and use it as a refutation of the possibility of 8-character userids. > > -- gil
A RACF id can be 8 characters. But, in that case, they cannot have a TSO segment. So they cannot be used to logon to TSO. If you try, you get a message of some sort from the TSO logon process. They can be used for batch jobs, UNIX shell accounts, ftp accounts, CICS logons, and probably others (like DB2 and IMS, but I don't know). The userid+1 is a very old "restriction" which is part of the OUTPUT|CANCEL|STATUS command. But it can be ignored by using TSO exit IKJEFF53. It never applied to SDSF, which uses either the SDSF parms or SAF controls. The TSO submit command, as best as I can tell, only looks at the job name in the JCL being submitted. If the job name is equal to the TSO id, then it either prompts for a unique character to append or appends one itself (depending on the PROFILE PROMPT setting). I submit jobs all the time which don't begin with my RACF id. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets® 9151 Boulevard 26 . N. Richland Hills . TX 76010 (817) 255-3225 phone . john.mck...@healthmarkets.com . www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets® is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company®, Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
