Robert, Unless I am misunderstanding you I think you are incorrect. Our production people submit jobs that do not belong to their userid's all the time and have no issue (we have no exits). If you are talking about the list/log Datasets at exit of ISPF that is set up by the user and will JCL if incorrect information is not supplied on the job statement.
Ed Sent from my iPad On Jul 30, 2011, at 3:10 PM, "Robert A. Rosenberg" <[email protected]> wrote: > At 12:34 -0500 on 07/30/2011, Ed Gould wrote about Re: Eight Position TSO > Logonid: > >> Paul: >> >> 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. >> >> Ed > > Automatic Jobs submitted by ISPF have the same restriction. They use your > defined JCL (which as a max 7 character Jobname) and append an extra > character. Also, the ISPF view output command (3.8?) uses your Jobname plus 1 > character as it search/select criteria. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
