IBM Mainframe Forum

Hi all,

I want to know the hex code of abend 837-08.

As i got hex code of:
abend SB30-04: X'04B37000' , and
abend SE37-04: X'04E37000'

Please help.

Regards
Utpal

837 is the hexadecimal code.

Hi Akatsukami,

Is hex code of 837-08 is 837 only?

I am not able to find it in the SPOOL or anywhere.
Please explain me:
If i can use X'0083700' for the 837 abend.

regards
Utpal

What do you need to know for?

Looking at your previous examples, if they are correct:

X'08837000'

But what use it is to you I don't know. Where do you get your previous examples? I've not come across an abend-code stored like that.

837 is a hex code. The 08 is another hexadecimal code called a reason code that provides additional information. X'08837000' most likely is the contents of register 1 when the ABEND SVC was called. The 08 in the first 8 bits of the register is just a code to to tell ABEND what it should be doing and has nothing to do with the ABEND itself.

The meaning of a system 837 ABEND code is in the MVS System Codes manual for your release. Look it up yourself. If there is something about the explanation you do not understand, add to this topic and someone may assist you.

utpalpal07 wrote:Hi Akatsukami,

Is hex code of 837-08 is 837 only?

I am not able to find it in the SPOOL or anywhere.
Please explain me:
If i can use X'0083700' for the 837 abend.

regards
Utpal

I think that you are referring to the contents of register 1. You needn't concern yourself with it unless you are writing HLASM. The IEF450 message should tell you the abend and reason codes; searching for them in the dump is unnecessary and useless.

An abend code of x37 ususally means the abend is SOMETHING to do with space. And why do you find it impossible to start your topic in the correct part of the forum? What do you think the DEBUGGING & TESTING part of the forum is for? Just padding so that it talkes long to scroll to the bottom? Topic moved.

thanks guys very useful info.

x37 ABENDs refer to the end of volume function, and that covers a multitude of sins, ranging from I/O errors to space problems.

Now a reasonable person might ask, "I/O errors!!!??? What does that have to do with end of volume?" The answer is sort of convoluted. Output tape end of volume is initiated by an I/O error when the end of tape marker is detected while writing an output record. There is still some physical tape left, so the output record completes writing, and then end of volume is called to analyze the I/O error. If this analysis indicates end of volume it writes a tape mark, trailing labels and another tape mark. End of volume then rewinds and unloads the tape and asks for another tape. A similar sequence is done for input; the I/O error this time is for a tape mark. Input end of volume either arranges for the end of data portion of your program to be entered if the labels indicate end of dataset, or, much like output, gets the next volume. In any event, end of volume gets to check all I/O errors that are not "real" I/O errors that the lower level I/O error analysis corrects before the I/O error is returned to the application.

I was unwilling to actually lookup the 837 code before; that's utpalpal07's responsibility. I finally did look it up just now. It appears to me there was some issue in the volume switch, which I didn't really understand, and which utpapal07 will have to investigate himself.

Hi steve

Thanks for the info. I investigate the prog i was getting 837-08 abend. but i need a hex code for the abend to detect using assembler prog.
But thanks guys for help.