On Tue, Dec 27, 2011 at 2:05 PM, Paul Gilmartin <[email protected]> wrote: > 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 In TSO ISPF SDSF, you can type SET DISPLAY ON to show your seleciton criteria. You probably have OWNER=userid PREFIX=*. This result is a good bypass to allow 8 character TSO userids. -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all?
---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
