If your "handy dandy sysout management tool" happens to be SDSF, be sure to use line command XFC (or its command line equivalents) to maintain proper formatting of the output data set.
-- -- Don Imbriale temporarily retired On Wed, Jan 6, 2010 at 2:32 PM, Wayne Driscoll <wdri...@us.ibm.com> wrote: > Or you can use SYSMDUMP DD SYSOUT=class > And then use your handy dandy sysout management tool to save the dump to a > disk dataset, and use IPCS. > See http://bama.ua.edu/cgi-bin/wa?A2=ind0709&L=ibm-main&P=R28921&I=1&X=- > > > =============================================== > Wayne Driscoll > OMEGAMON DB2 L3 Support/Development > wdrisco(AT)us.ibm.com > =============================================== > > > > From: > Don Poitras <sas...@sas.com> > To: > IBM-MAIN@bama.ua.edu > Date: > 01/06/2010 01:10 PM > Subject: > Re: Where have the control blocks gone? -- Now down in the dumps > Sent by: > IBM Mainframe Discussion List <IBM-MAIN@bama.ua.edu> > > > > Thompson, Steve wrote: > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On > > Behalf Of Don Poitras > > Sent: Wednesday, January 06, 2010 12:10 PM > > To: IBM-MAIN@bama.ua.edu > > Subject: Re: Where have the control blocks gone? > > > > <SNIPPAGE> > > > > Use FREE=CLOSE on the SYSMDUMP DD. > > <Snip> > > > > That only works if you are not interested in any other ABEND or dump > > producing event that occurs. > > > > If DISP=MOD would work for SYSMDUMP, I could figure out how to split the > > dumps by processing the file with REXX or some such. > > > > [I have a special case with my stuff -- the things I work on are > > multi-threaded, multi-tasking and one failure may not be related at all > > to another.] > > > > Let me give you an example: Program "DRIVER" is running. In a daughter > > TCB a program is writing to DASD and gets an Sx37. Let's say that 10 > > seconds later, under a different TCB the program I am interested in > > (SHUCKS) finally gets the S0C3 I set up. That's the dump I really want > > to look at. > > > > But let's have even more fun. Before I can get to the dump DSN with > > IEBGENER (which would have to be invoked within this JOBSTEP to deal > > with the DISP=OLD...), another program under a different TCB ABENDS. I > > just lost the dump I'm really interested in. In this case, my only > > choice for this is a SLIP. > > > > So the SYSMDUMP just can't handle this level of complexity. > > > > Welcome to the world of a developer. Thankfully, I have the ability to > > issue MVS commands and can set SLIPs when and as I need them. > > > > But for the typical programmer/analyst in a production world situation > > that does get to use IPCS, you don't get to do this. > > > > There's the rub. > > You can have multiple SYSMDUMPs. e.g. > > //SYSMDUMP DD DISP=SHR,DSN=SASDTP.SYSMDUMP,FREE=CLOSE > //SYSMDUMP DD DISP=SHR,DSN=SASDTP.SYSMDUM2,FREE=CLOSE > > and if you just can't stand not getting _every_ dump, code a SYSUDUMP > as the last one (without FREE=CLOSE): > > -- > Don Poitras - zSeries R & D - SAS Institute Inc. - SAS Campus Drive > mailto:sas...@sas.com (919)531-5637 Fax:677-4444 Cary, NC 27513 > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
