Bob Wright wrote:
>
> Miklos Szigetvari wrote:
> > We produce SYSMDUMP's with DISP=MOD, and the SYSMDUMP dataset contains a
> > number of DUMP's
> > Any method to select the second etc. dump?
> > ( I see I could use GENER to copy from the 'DR2 H' header)
> > Any better idea maybe ?
>
> Using DISP=MOD is a good idea. ISPF, for one, can see some applications
> ABENDs that produce dumps and, in turn, conclude that its "physical
> screen task" is a potential villain. When that happens, you'll get two,
> related dumps from a single incident. The first, generated closest to
> the point of error is likely to be the best one, and it can be directly
> examined using IPCS. The header record for the 2nd will be treated as a
> logical EOF for IPCS purposes. But you asked about the 2nd, 3rd, ....
>
> The IPCS COPYDUMP subcommand was designed to address this situation,
> allowing you to manually walk through the contents of a data set and
> select which logical dump(s) that you want copied to data sets by
> themselves. The many return codes that can be generated should, in
> principle, also allow you to come up with a command procedure that helps
> you perform the processing your way.
>
> --
> Bob Wright - MVS Service Aids
Another method of handling programs that produce multiple dumps is to
use FREE=CLOSE to allow multiple dump DDs. e.g.
//TEST1 EXEC PGM=SHRMAIN,REGION=5M
//STEPLIB DD DSN=SASDTP.TEST.LOAD,DISP=SHR
//CTRANS DD DSN=SASDTP.LC750.LOAD,DISP=SHR
// DD DSN=LSD.LC750.LOAD,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSTERM DD SYSOUT=*
//LOG DD SYSOUT=*
//SYSMDUMP DD DSN=SASDTP.SYSMDUMP,DISP=SHR,FREE=CLOSE
//SYSUDUMP DD SYSOUT=*,FREE=CLOSE
//SYSMDUMP DD DSN=SASDTP.SYSMDUM2,DISP=SHR,FREE=CLOSE
//SYSUDUMP DD SYSOUT=*,FREE=CLOSE
If the last dump DD has FREE=CLOSE, then dumps taken after that DD is
closed will not be captured. To insure that all dumps are
captured put a SYSUDUMP DD as the last dump DD and omit the
FREE=CLOSE.
For example:
//SYSMDUMP DD DSN=SASDTP.SYSMDUMP,DISP=SHR,FREE=CLOSE
//SYSUDUMP DD SYSOUT=*,FREE=CLOSE
//* use a separate DSN for each SYSMDUMP!
//SYSMDUMP DD DSN=SASDTP.SYSMDUM2,DISP=SHR,FREE=CLOSE
//SYSUDUMP DD SYSOUT=*,FREE=CLOSE
//SYSUDUMP DD SYSOUT=*
This would capture the first and third dumps as machine dumps, the
second and forth as separate formatted dumps and the remaining
dumps concatenated in one sysout file.
--
Don Poitras - zSeries R & D - SAS Institute Inc. - SAS Campus Drive
mailto:[EMAIL PROTECTED] (919)531-5637 Fax:677-4444 Cary, NC 27513
----------------------------------------------------------------------
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
