On Sat, 30 Jul 2011 12:34:44 -0500, Ed Gould wrote: > >If that were the only issue then maybe. TSO also has built in code that >insists that say if you use the output command (not the only command) that >insists that the job name you are working on is your userid plus 1 character. >Eight character job names is fixed so now you can't access your output. That >is only one of the built in restrictions, there are more. > None of which matters if the 8-character logon name is mapped to a 7-character TSO ID. Other control blocks are unaffected; the SUBMIT and OUTPUT commands are unaffected.
BTW, who still uses OUTPUT nowadays that SDSF and (E)JES exist? >> >> http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/bpxzb2b0/3.7.4.3 >> >> This already exists. It can map an 8-character logon ID to a 7-character >> TSO ID. It should be compatible with all existing TSO control blocks. It appears to have been invented to provide compliance with customers' corporate naming standards. It's a kludge, but it fits the purpose. Why not extend it beyond OMVS to TSO? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
