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.
. . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Pommier, Rex Sent: Friday, April 16, 2021 10:32 AM To: [email protected] Subject: (External):Re: [External] Re: Print a SYSMDUMP *** EXTERNAL EMAIL - Use caution when opening links or attachments *** Some of ours do too, and after a couple warnings we just start whacking their jobs from the spool because they're filling it up. Rex -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Mark Jacobs Sent: Friday, April 16, 2021 11:37 AM To: [email protected] Subject: [External] Re: Print a SYSMDUMP Some of our new developers have //SYSMDUMP DD SYSOUT=* in their JCL. Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get&[email protected] ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, April 16th, 2021 at 12:30 PM, Seymour J Metz <[email protected]> wrote: > Well, back when AMDPRDMP was a thing, you could print a SYSMDUMP, but why > would you want to? Searching a large dump on SPOOL is a RPITA, and doing it > on paper is worse. Yes, IPCS has its faults, but it's so much nicer than the > older alternatives. > > > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > -------------------------------------- > > Shmuel (Seymour J.) Metz > > http://mason.gmu.edu/~smetz3 > > From: IBM Mainframe Discussion List [[email protected]] on > behalf of Peter Relson [[email protected]] > > Sent: Friday, April 16, 2021 12:23 PM > > To: [email protected] > > Subject: Re: Print a SYSMDUMP > > My answer, being nit-picky, is: no, you cannot print a SYSMDUMP, aside > > from printing the dump records themselves such as in hex but you can > > direct IPCS to write its output to a data set that you could then > print, > > after doing whatever IPCS commands you have chosen to do. > > For example, from some old notes (and maybe there are better options > now) > > Allocate data set IPCSPRNT with RECFM VBA LRECL 255 BLKSIZE 6144 or > with > > RECFM VBA LRECL 137 BLKSIZE 27998 > > TSO ALLOC F(IPCSPRNT) DA(IPCSPRNT) > > IPCS SYSTRACE ALL print > > IPCS CTRACE COMP(SYSxxx) FULL print noterm > > IPCS Close Print > > Peter Relson > > z/OS Core Technology Design > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
