On Tue, 18 Dec 2007 11:26:53 -0500, Lizette Koehler <[EMAIL PROTECTED]> wrote:
>I am getting ready to do some general housekeeping/clean up and was hoping to find an ROT for starting STCs with SUB=MSTR. > >I am not sure if all STCs need to be started with SUB=MSTR or if there are specific reasons to start one that way instead of normal (JES2) > >For example, my STC called GEORGE has SYSOUT= in the JCL. But the vendor insists I start it with SUB=MSTR because the vendor is concerned that the JES data sets would not be accessible/available. > >Of couse, for PDR, this makes it interesting as I have to extract any messages produced by the STC from SYSLOG. > No reason to normally. I don't know if there is a ROT. I don't start a task with SUB=MSTR unless the vendor recommends it first, then I need to look at the reason why. I think our automation product and SMC (which controlls allocation for Sun/STK robotic and virtual tape software) are it. An automation product that starts JES2 must run SUB=MSTR since it must start before JES2. Anything that must start before JES2 is a valid reason to run SUB=MSTR. I'm not sure what you are saying about "GEORGE". SYSOUT= can't be in a SUB=MSTR started PROC. But I think you are saying data sets are being used for SYSOUT and the vendor wants it started SUB=MSTR so sysout is not lost? Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.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
