Rick Fochtman wrote:
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.
Sysout support should not be required for message and dump capture. The SVC dump is written to DASD. And, when analyzing the dump using IPCS, the MTRACE shows the messages written prior to the dump capture.
We like to get the network started ASAP, without waiting for JES. Therefore, we run both VTAM and TCPIP with SUB=MSTR.
With things set up properly, we can even logon to TSO/E with SUB=MSTR in order to fix a problem that's preventing JES from initializing! (Of course, these days we do mostly rolling IPL in a sysplex, so that "trick" hasn't been needed in quite some time. But, it still works!)
-- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [EMAIL PROTECTED] http://www.phoenixsoftware.com/ ---------------------------------------------------------------------- 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
