It looks like you are installing Teradata Director. Recheck Appendix A. Or just issue "S TDP4,MSGCLASS=R,SUB=JES2" and be happy... maybe? (Your happiness depends upon whether the INITRTN performs much beyond allowing the JES subsys to be the default for sysin/sysout services. My quick glance at Appendix A's leads me to claim that it is optional, so I would guess you could be happy.) --
On Thu, 13 Aug 2009 16:03:10 -0400, Lizette Koehler wrote: >I recently added a subsystem using SETSSI. I did not realize when I issued the command it had an INITRTN on it. > >Now I have to run the jcl from SYS1.PROCLIB rather than my OEM proclib dataset. > >The message I get when I start it is > >S TDP4,MSGCLASS=R >IEF196I 1 //TDP4 JOB MSGCLASS=R, >IEF196I // MSGLEVEL=1 >IEF196I 2 //STARTING EXEC TDP4 >IEF196I STMT NO. MESSAGE >IEF196I 2 IEFC612I PROCEDURE TDP4 WAS NOT FOUND >IEFC452I TDP4 - JOB NOT RUN - JCL ERROR >IEE122I START COMMAND JCL ERROR > >The other STCs of the same product run out of OEM proclib. Is this due to the missing INITRTN on the SETSSI command? I have TDP1, TDP2, TDP3. ---------------------------------------------------------------------- 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
