I really want to thank several of you guys for the help.

Moving between operating systems would seem easy, but some times it's just an unexpected tripping hazard that causes me the most problems. Like this dump stuff. Someone turned off dumps in the operating system and I thought I was doing something wrong, not that the system was doing something unexpected. (Sometimes, I just want to kick the last systems programmer that set things here up "strange".)

Tony Thigpen

Seymour J Metz wrote on 10/30/20 2:31 PM:
Well, you already know about DAE, controlled by ADYSETxx, so I'll address the 
other part.

The contents are controlled by macro parameters and installation defaults in 
PARMLIB members, possibly changed with a CHNGDUMP command; normally SYSABEND 
includes more data than SYSUDUMP.

Dump processing normally looks for predefined ddnames; you should only have one 
of these in a step:

SYSMDUMP
     Unformatted dump
     Usually DSN=permanent.name
     Can be read by
         IPCS in batch
         IPCS from the TSO READY prompt
         IPCS panels in ISPF
     Controlled by IEADMR00

SYSABEND
     Formatted dump
     Usually SYSOUT=*
     Controlled by IEAABD00

SYSUDUMP
     Formatted dump
     Usually SYSOUT=*
     Controlled by IEADMP00


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

________________________________________
From: IBM Mainframe Assembler List [[email protected]] on behalf 
of Tony Thigpen [[email protected]]
Sent: Friday, October 30, 2020 9:02 AM
To: [email protected]
Subject: Re: SDUMPs

Seymour, others,

Formatted or unformatted dumps does not matter to me. I actually prefer
an unformatted dump as that is what I read all the time on z/VSe.

But, as I move deeper into z/OS, I do want to learn to use some of it's
tools, such as IPCS.

Let's back up a second and let me ask what may be a basic question to
z/OS gurus.

Right now, if I put the ABEND macro into the source, it creates a new
dump in IPCS. But, if I create a SOC1 (using DC X'0000' in the code), it
does not put a new dump into IPCS.

1) Should it have put a new dump in IPCS?
2) If so, is there some 'option' in the system that may be blocking the
creation of the SOC1 dump?

3) Is there a simple way to force the SOC1 dump to go to SYSOUT as an
unformatted dump?

FYI, I am on a test z/OS system that I can IPL or change, as needed
without messing anyone up.

Tony Thigpen

Seymour J Metz wrote on 10/30/20 5:07 AM:
Well, I started with formatted (there were no unformatted dumps and no IPCS) 
dumps, and they are a royal pain. Except for the most trivial cases, it's a lot 
more convenient with IPCS.



--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

________________________________________
From: IBM Mainframe Assembler List [[email protected]] on behalf 
of Mike Hochee [[email protected]]
Sent: Thursday, October 29, 2020 11:39 PM
To: [email protected]
Subject: Re: SDUMPs

Hi Tony,
I frequently use the procedure Gary mentioned which results in a formatted 
dump. I suspect IPCS might be overkill, but I don't know your situation. I'm 
sure folks exist who cut the teeth on MVS dump reading by starting out with 
unformatted dumps and IPCS, but I don't know of any. The formatted SYSUDUMP is 
pretty straightforward.

If you have any questions, there is a section in the chapter on ABEND dumps in 
this manual... 
https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/zOSV2R3ga320905/$file/ieav100_v2r3.pdf
  The zap utility mentioned is also in there if you need it, and called SPZAP.

HTH,
Mike

Reply via email to