SETSSI and Pitfalls

2009-08-13 Thread Lizette Koehler
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

Re: SETSSI and Pitfalls

2009-08-13 Thread Bob Rutledge
By default, a started task matching a subsystem name starts under the master scheduler. http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2B680/7.3.1?SHELF=EZ2ZBK0GDT=20080604022956 Bob Lizette Koehler wrote: I recently added a subsystem using SETSSI. I did not realize when I

Re: SETSSI and Pitfalls

2009-08-13 Thread Binyamin Dissen
On Thu, 13 Aug 2009 16:03:10 -0400 Lizette Koehler stars...@mindspring.com 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

Re: SETSSI and Pitfalls

2009-08-13 Thread Nemo
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

Re: SETSSI and Pitfalls

2009-08-13 Thread Brian Peterson
And, the manual doesn't come right out and say this, but this default behavior can be overridden as follows: Instead of: S TDP4,MSGCLASS=R Use instead: S TDP4,MSGCLASS=R,SUB=JES2 This makes the started task run under JES2 instead of *MASTER*, which is the default for subsystems. Brian On

Re: SETSSI and Pitfalls

2009-08-13 Thread Mark Zelden
On Thu, 13 Aug 2009 16:03:10 -0400, Lizette Koehler stars...@mindspring.com wrote: I recently added a subsystem using SETSSI. I did not realize when I issued the command it had an INITRTN on it. You're SOL until you can IPL. There probably should be an extra warning in the commands manual

SUB=MSTR and proclibs; was SETSSI and Pitfalls

2009-08-13 Thread Gibney, Dave
Am I wrong. I keep my MSTRJCL and my JES2PARM proclib definitions in sync. SUB=MSTR and SUB=JES2 will start the same PROC. On the other hand, in this case, I think I'd go with IEFJOBS DD in MSTRJCL. Then I would specify the OEM PROCLIB using JCLLIB. Or, since I've never needed such a feature,

Re: SETSSI and Pitfalls

2009-08-13 Thread Barbara Nitz
Lizette, I recently added a subsystem using SETSSI. and once you've overcome the actual definition thing, beat up on the vendor. There is a bit that they should have been set that says that JES2 is always the primary subsystem for this product. That would avoid the same problem (the