--------------------<snip>------------------
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.
Any thoughts?
-------------------<unsnip>-----------------
Unless there's a very specific reason, I recommend that SUB=MSTR be
avoided. Others may disagree, but I prefer to have JES up and running as
soon as possible, so that messages, dumps, etc. from started tasks may
be captured. I typically recommend that JES be started as early as
possible in the IPL sequence/procedure so that messages, etc. can be
captured as much as possible from started tasks; makes debugging a lot
simpler when you've got a real sysout, and SYSLOG won't always capture
everything you need.
Whoever is giving you the recommendations for "GEORGE" needs some
education. With a SYSOUT=*, it should be failing for a JCL error if it's
started before JES. The reason he offers is (vulgar term for organic
fertilizer).
----------------------------------------------------------------------
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
