S04E abend



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

S04E abend

Postby vinod_rana » Fri May 06, 2011 3:35 pm

CAn anyone please explain what is S04E abend.
vinod_rana
 
Posts: 8
Joined: Thu Apr 21, 2011 12:58 pm
Has thanked: 0 time
Been thanked: 0 time

Re: S04E abend

Postby NicC » Fri May 06, 2011 3:53 pm

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?
The problem I have is that people can explain things quickly but I can only comprehend slowly.
Regards
Nic
NicC
Global moderator
 
Posts: 3025
Joined: Sun Jul 04, 2010 12:13 am
Location: Pushing up the daisies (almost)
Has thanked: 4 times
Been thanked: 136 times

Re: S04E abend

Postby NicC » Fri May 06, 2011 4:32 pm

Whoops - wrong forum for that title but there is a similar here - Debugging & Testing
The problem I have is that people can explain things quickly but I can only comprehend slowly.
Regards
Nic
NicC
Global moderator
 
Posts: 3025
Joined: Sun Jul 04, 2010 12:13 am
Location: Pushing up the daisies (almost)
Has thanked: 4 times
Been thanked: 136 times

Re: S04E abend

Postby DFSHDC40 » Sun May 08, 2011 2:51 am

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
If the code hasn't been changed, why is the LKED date today?
User avatar
DFSHDC40
 
Posts: 41
Joined: Sat Oct 16, 2010 4:16 pm
Location: IMS.SDFSRESL
Has thanked: 0 time
Been thanked: 0 time

Re: S04E abend

Postby Anuj Dhawan » Mon May 09, 2011 2:51 pm

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.
Anuj
Anuj Dhawan
 
Posts: 273
Joined: Mon Feb 25, 2008 3:53 am
Location: Mumbai, India
Has thanked: 6 times
Been thanked: 4 times


Return to JCL

 


  • Related topics
    Replies
    Views
    Last post