SYSMDUMP to SYSOUT can be either really smart or pretty dumb. If your intent is to use SDSF XDC (or some XWTR-like device) to capture them to real DASD datasets when needed; and your spool is adequately sized to handle them, it's a fairly clever way to avoid all the space allocation hassle. This technique would generally want a special sysout class so they can be managed appropriately.
If you thought it was actually going to be viewable or "printable" then yeah, not so smart. sas On Fri, Apr 16, 2021 at 1:32 PM Pommier, Rex <rpomm...@sfgmembers.com> wrote: > 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 <IBM-MAIN@LISTSERV.UA.EDU> On Behalf > Of Mark Jacobs > Sent: Friday, April 16, 2021 11:37 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [External] Re: Print a SYSMDUMP > > Some of our new developers have //SYSMDUMP DD SYSOUT=* in their JCL. > > Mark Jacobs > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
