Page 1 of 1

S04E abend

PostPosted: Fri May 06, 2011 3:35 pm
by vinod_rana
CAn anyone please explain what is S04E abend.

Re: S04E abend

PostPosted: Fri May 06, 2011 3:53 pm
by NicC
Why do you think that this should be in the JCL area and not the bend and debugging area? What is it about the explanation in the manual that you do not understand?

Re: S04E abend

PostPosted: Fri May 06, 2011 4:32 pm
by NicC
Whoops - wrong forum for that title but there is a similar here - Debugging & Testing

Re: S04E abend

PostPosted: Sun May 08, 2011 2:51 am
by DFSHDC40
DB2? - need a reason code to get any further with your diagnosis, when DB2 Universal Database for z/OS Codes Manual will be extremely useful

Re: S04E abend

PostPosted: Mon May 09, 2011 2:51 pm
by Anuj Dhawan
Start from here:

04E

Explanation: When the system detects an error in internal IBM DATABASE 2 (DB2¦) processing, it will abnormally end a connected user task (TCB) or one of its own internal tasks. For information about the reason codes associated with this abend code, see DB2 Messages and Codes.

System Action: The system abnormally ends the connected user task or the DB2 internal task.

Application Programmer Response: Check register 15 of the SDWA section'General Purpose Registers at Time of Error', and locate the accompanying reason code. In addition, check the information displayed at the user's terminal, and in the corresponding logrec data set entry.

System Programmer Response: If the error recurs and the program is not in error, look at the messages in the job log for more information. Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the SYSOUT output for the job and the logrec data set error record.


If you want to know about this abend out of curiosity, suggest you get familir with manuals. If there is an actual abend, it might have some other reason/s too; e.g. once the problem was with a module referencing outside the array bounds. Since the SSRANGE option was not on, this was not being handled causing the program to fail at some other point with a S04E.