On 4/16/2021 1:04 PM, Jesse 1 Robinson wrote:
I take the same approach to SYSMDUMP and to SYSABEND: tell people not to direct them to sysout. If you find one, trash it. Be prepared to fight this up the food chain. Make sure you have allies in the right places. It could get nasty.
I consider //SYSMDUMP DD SYSOUT=* to be the best way to manage batch job dumps. We've done this for years with excellent results.
Writing your SYSMDUMP dump to a DASD data set practically ensures you will end up with an out-of-sync condition at some point when you go back to try to diagnose a batch job failure because people often re-submit jobs causing the dump data set to be deleted. If you have your SVC dump as part of the job's SYSOUT, you have the job output (messages, report, etc.) and the SVC dump together in one consistent package. And, when the job is purged, the dump goes with it.
We even have a special (E)JES CAI plug-in for this. A single line command copies the SYSMDUMP to DASD and invokes IPCS to initialize it. Easy peasy.
-- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ -------------------------------------------------------------------------------- This e-mail message, including any attachments, appended messages and the information contained therein, is for the sole use of the intended recipient(s). If you are not an intended recipient or have otherwise received this email message in error, any use, dissemination, distribution, review, storage or copying of this e-mail message and the information contained therein is strictly prohibited. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this email message and do not otherwise utilize or retain this email message or any or all of the information contained therein. Although this email message and any attachments or appended messages are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way from its opening or use. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
