Posted: Mon Aug 09, 2004 11:45 am Post subject: ABEND=S000 U4000 REASON=00000000
Hello,
I am getting this abend and I find it really wierd. This is because I do not get this abend when I am using another input dataset (processed by the module being executed) and when I run this new dataset through, I get this abend. The new dataset is much much larger in size, but I do not seem to understand why I get such an abend. I would have expected a space abend for the larger input dataset at most. Would anybody have an idea on this abend and can they throw some light?
Code:
IBM002I R3BBKAJ0 INTERRUPT DURING PROGRAM MANAGEMENT LIBRARY ROUTINES,
PROGRAM TERMINATED
IEA995I SYMPTOM DUMP OUTPUT
USER COMPLETION CODE=4000
TIME=11.49.16 SEQ=32593 CPU=0000 ASID=0210
PSW AT TIME OF ERROR 078D1E00 8000E8BE ILC 2 INTC 0D
ACTIVE LOAD MODULE ADDRESS=00007BE8 OFFSET=00006CD6
NAME=IBMBLIIA
DATA AT PSW 0000E8B8 - 00181610 0A0D0000 000000A0
Joined: 26 Nov 2002 Posts: 12378 Topics: 75 Location: San Jose
Posted: Mon Aug 09, 2004 12:09 pm Post subject:
Manoj,
Check this for a detailed explanation of IBM002I
Code:
Message ID: IBM002I
Upper Case (UE) Version: job-name INTERRUPT DURING PL/1 MANAGEMENT
LIBRARY ROUTINES, PROGRAM TERMINATED.
Mixed Case (EN) Version: job-name An interrupt occurred during PL/1
program management library routines, the
program is being terminated.
Description: This is a PL/1 run-time message which indicates that an
interrupt occurred in a PL/1 program management routine
(or a routine invoked by a PL/1 management routine)
during the processing of a PL/1 condition. The program
was terminated with a return code of 4000. 'job-name' is
replaced in the message text by the name of the job which
was affected. A dump is produced if a SYSUDUMP or
SYSABEND dd statement is available.
This message indicates that a disastrous error (i.e.,
overlaying sections of code and/or control blocks)
occurred while the program was executing. This type of
error is usually caused by:
-arrays extending their bounds
-use of the SUBSTR function with invalid arguments
-execution of a GO TO statement with a label
reference which is invalid (or unitialized)
User Action: If arrays and/or the SUBSTR function are used in the
program, then enable SUBSCRIPTRANGE and/or STRINGRANGE,
recompile, and re-execute the program. If GOTO
statements containing label variables are used, then
enable CHECK for those label variables, recompile, and
re-execute the program.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum