Only ca. 150 pages on paper (excerpts from CEEDUMP and SYSUDUMP,
and compile listings, of course), so that the students can write notes
on it,
the rest of the dumps is in the machine, in PDF format (landscape shape).
The students read them on the screen, works pretty well,
or they go to SYSVIEW
of course we did the same thing (tons of paper) some 25 years ago.
Am 27.11.2014 10:43, schrieb Bernd Oppolzer:
Only ca. 150 pages on paper (excerpts from CEEDUMP and SYSUDUMP,
and compile listings, of course), so that the students can write notes
on it,
the rest of the dumps is in the
Bernd Oppolzer wrote:
of course we did the same thing (tons of paper) some 25 years ago.
Years ago I and my (mostly ex) colleagues sifted through dump lists, syslog,
job printouts, timesheets, RACF logs (RACFRW - four lines PER event!),
schedules of jobs, etc. We have lots of trolleys, racks,
LE runtime is TERMTHDACT(UADUMP,,96)
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
@LISTSERV.UA.EDU
Subject: Re: SOC1 and SYSUDUMP and CEEDUMP
There is - it is named SSRANGE for the Enterprise COBOL compilers, at least up
through 4.2.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email
Peter Ten Eyck wrote:
LE runtime is TERMTHDACT(UADUMP,,96)
Ok. I will bite. I see in LE book, this:
Under non-CICS, if the appropriate DD statement is used, you will get a system
dump of your user address space.
A$$suming you're not running CICS, did you used that DD statement?
(Even after
] On
Behalf Of Peter Ten Eyck
Sent: Tuesday, November 25, 2014 6:27 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SOC1 and SYSUDUMP and CEEDUMP
LE runtime is TERMTHDACT(UADUMP,,96)
--
For IBM-MAIN subscribe / signoff / archive
Lizette Koehler wrote:
Also these share presentations may be helpful
http://www-03.ibm.com/systems/z/os/zos/features/lang_environment/conference/share.html
Ah, yes. I remember now. Thanks Lizette!
Peter Ten Eyck, are you using a SLIP? According to that presentation, you
should not use a SLIP
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Elardus Engelbrecht
Sent: Tuesday, November 25, 2014 8:14 AM
Peter Ten Eyck wrote:
LE runtime is TERMTHDACT(UADUMP,,96)
Ok. I will bite. I see in LE book, this:
Under non-CICS, if the appropriate DD
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Elardus Engelbrecht
Sent: Tuesday, November 25, 2014 8:42 AM
Lizette Koehler wrote:
Also these share presentations may be helpful
http://www-03.ibm.com/systems/z/os/zos/features/lang_environment/confer
On 11/25/2014 8:19 AM, Chase, John wrote:
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Elardus Engelbrecht
Sent: Tuesday, November 25, 2014 8:42 AM
Lizette Koehler wrote:
Also these share presentations may be helpful
On Tue, 25 Nov 2014 07:27:23 -0700 Lizette Koehler stars...@mindspring.com
wrote:
:You would need to see what module the CEEDUMP is indicating is the issue.
When you get an SYSUDUMP you would need to use IPCS and VERBX LEDATA to get to
the regs to see what is going on.
A nit. IPCS runs
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Steve Comstock
Sent: Tuesday, November 25, 2014 9:46 AM
On 11/25/2014 8:19 AM, Chase, John wrote:
[ snip ]
Indeed. We're currently working a PMR in which, to get an SVCDUMP of a
S0C4 before LE's condition
Thanks for the good feedback. I had the programmer use the SYSUDUMP DD for this
program... which did produce a SOC1 dump. This dump was sent to Abend-Aid and
the programmer was able to make a correction to the code and get the program
running cleanly.
I still do not know what it is about that
As I told already in my previous post on this topic:
there are certains types of errors, especially when code area is overwritten
(S0C1 can be a symptom for that kind of error), when LE error handler is
not able to cope with
program errors (maybe LE control blocks are damaged too). If you are
On Wed, 26 Nov 2014 01:33:00 +0100, Bernd Oppolzer wrote:
I do classes on dump diagnose, BTW,
Many years ago I did a dump class - as an adjunct to the MVS Internals class
Amdahl used to offer.
Hand-outs for the class included multiple fanfold listings - each several
inches thick. which we had
I have a COBOL program that is getting a SOC1 and produces a dump when the
SYSUDUMP DD is code in the failing step. If CEEDUMP is coded instead of
SYSUDUMP no dump is produced.
This program is complied with the same COBOL parameters and run in the same LE
environment as other COBOL programs
Dump information is only written to CEEDUMP following an S0C1 abend,
if the S0C1 was handled by LE. This should be the normal case in a LE
environment.
But in this case, if you don't get CEEDUMP information written following
the
S0C1, I guess that THIS S0C1 is not handled by LE, but it is a
One more idea:
I once had a strange S0C1 abend because due to an index range error
large parts of the program code were overwritten, and even the LE error
handler was unable to diagnose the error correctly, although under normal
circumstances it should be able to do so.
This was PL/1, not
How is your termthdact coded for the le environment?
Lizette
-Original Message-
From: Peter Ten Eyck peter_tene...@farmfamily.com
Sent: Nov 24, 2014 2:38 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: SOC1 and SYSUDUMP and CEEDUMP
I have a COBOL program that is getting a SOC1 and produces
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
On Behalf Of Bernd Oppolzer
Sent: Monday, November 24, 2014 5:11 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SOC1 and SYSUDUMP and CEEDUMP
One more idea:
I once had a strange S0C1 abend
21 matches
Mail list logo
