Using ceedump offset and address



JES, JES2, JCL utilities, IDCAMS, Compile & Run JCLs, PROCs etc...

Using ceedump offset and address

Postby vivek naik » Thu Apr 26, 2012 9:51 am

Hi

A failed job created a CEEDUMP file. I would like to know what does it tell about the failed program.

Also in sysout file "From compile unit <program name> at entry point DLITCBL at compile unit offset+000057BA at entry offset +00004132 at address 150AAEC2." message was written. How is this message useful in finding the source of error?

Any manual suggestion for these topics?
Which manual should i refer to know about output files of the job?

Sorry BillyBoyo , Robert Sample and dick scherrer if i wrote anything wrong :geek: :)
Working On A Dream
vivek naik
 
Posts: 6
Joined: Wed Jan 18, 2012 11:24 am
Has thanked: 0 time
Been thanked: 0 time

Re: Using ceedump offset and address

 

Re: Using ceedump offset and address

Postby halfteck » Thu Apr 26, 2012 11:32 am

I suspect people on here might appreciate an actual abend / completion code that accompanied the failure
halfteck
 
Posts: 42
Joined: Tue Nov 08, 2011 8:47 pm
Has thanked: 0 time
Been thanked: 0 time

Re: Using ceedump offset and address

Postby vivek naik » Thu Apr 26, 2012 1:11 pm

Here is the complete message

CEE3250C The system or user abend U1001 R=NULL was issued.
From compile unit <program name> at entry point DLITCBL at compile unit offset +000057BA at entry offset +00004132 at address 150AAEC2.
Working On A Dream
vivek naik
 
Posts: 6
Joined: Wed Jan 18, 2012 11:24 am
Has thanked: 0 time
Been thanked: 0 time

Re: Using ceedump offset and address

Postby dick scherrer » Thu Apr 26, 2012 9:17 pm

Hello,

Nothing "wrong" but a bit incomplete :)

Suggest you find the cause of a User 1001 Abend (U1001). This is code generated rather than a System Abend (Sxxx). It will be documented for the code that was running.

What are you running at the time of the abend (the answer is NOT jcl)? JCL doesn't abend, programs abend.
Hope this helps,
d.sch.
User avatar
dick scherrer
Global moderator
 
Posts: 6304
Joined: Sat Jun 09, 2007 8:58 am
Has thanked: 3 times
Been thanked: 91 times

Re: Using ceedump offset and address

Postby vivek naik » Fri Apr 27, 2012 9:16 am

Hi

Yes Program abended. :D
I found the cause of error. It was wrong run date card used. Still working on the resolution. Not good with analysis so its taking time :( .
My point in asking this question is not to find the resolution of the abend.

The address "150AAEC2" and offset "+000057BA" mentioned in the sysout message, what information i can get from them regarding error? what do they tell about the abend?

Any manual where i can read about these things. I searched jcl manuals nothing in them.

Thank You
Working On A Dream
vivek naik
 
Posts: 6
Joined: Wed Jan 18, 2012 11:24 am
Has thanked: 0 time
Been thanked: 0 time

Re: Using ceedump offset and address

Postby BillyBoyo » Fri Apr 27, 2012 1:06 pm

For a manual, try "Language Environment Debugging Guide", there should be one for your version of z/OS.

The "address" in this case is the storage address where the failing instruction was. The "offset" is the displacement of that address from the start of the program containing the address (usually). You can correlate the "offset" to the instruction addresses in your compile listing.
BillyBoyo
Global moderator
 
Posts: 3804
Joined: Tue Jan 25, 2011 12:02 am
Has thanked: 22 times
Been thanked: 264 times

Re: Using ceedump offset and address

Postby dick scherrer » Fri Apr 27, 2012 9:06 pm

Hello,

From my perspective, the addresses/ofsets/instructions are of more use when there is a System Abend (Sxxx) rather than a User Abend (Unnnn).

For User Abends, there is (or should be) documentation about what can cause a particular User abend. Often User Abends are accompanied by some kind of message as well.
Hope this helps,
d.sch.
User avatar
dick scherrer
Global moderator
 
Posts: 6304
Joined: Sat Jun 09, 2007 8:58 am
Has thanked: 3 times
Been thanked: 91 times


Return to JCL

 


  • Related topics
    Replies
    Views
    Last post