This makes absolutely no sense in English. 837 and 08 are both hex codes. If you really mean you need to locate the program that was executing when it got the ABEND, you probably need a full system dump and a linkage editor map of the load module. Even then it will be difficult as the actual location of the ABEND is in some end of volume module or in the z/OS nucleus, not in your program. The location of the SVC X'37' instruction will be in a I/O module loaded by OPEN, not in your program.utpalpal07 wrote: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.
Even your assumption it was an Assembler program that got the error is true only in the sense a library module linked with your program that performed the Assembler read or write is an Assembler program. but the real culprit is the program that called the library module
Message IEC028I, which accompanied the S837 ABEND has information about the DD name and dataset name of the dataset being used at the time of the 837 ABEND; this will be of more use in locating the program that got the error than the dump analysis.
I went back to your initial post. After rereading it, I'm not sure you got an 837 ABEND. I think you got either a B37 or E37 ABEND. Both are space errors; the difference between them is subtle and even after 44 years I never understood the difference between them. Both ABENDs produce an IECnnnI message with additional information which will almost certainly be of more use than dump analysis.