Jcl Errors, Abends and their Remedies



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

Jcl Errors, Abends and their Remedies

Postby kaviyarasan » Thu Feb 21, 2008 9:17 am

May i get a list of jcl errors, abends and their remedies. or else a reference book for this?
kaviyarasan
 
Posts: 3
Joined: Mon Feb 18, 2008 8:44 am
Has thanked: 0 time
Been thanked: 0 time

Re: Jcl errors, abends and their remedies

Postby kaviyarasan » Thu Feb 21, 2008 10:30 am

and also i have a abend code of se37 how to solve this error.
kaviyarasan
 
Posts: 3
Joined: Mon Feb 18, 2008 8:44 am
Has thanked: 0 time
Been thanked: 0 time

Re: Jcl errors, abends and their remedies

Postby MrSpock » Thu Feb 21, 2008 11:28 am

kaviyarasan wrote:and also i have a abend code of se37 how to solve this error.


1. Go to IBM:LookAt - z/OS Message Help.
2. Enter SE37 where it says 1. Enter a Message ID.
3. Select your platform.
4. Click on GO.
5. Read the results.

Explanation: The error occurred when an output operation was requested. The data set was on a direct access or magnetic tape device. This system completion code is accompanied by message IEC032I. Refer to the explanation of message IEC032I for complete information about the task that was ended and for an explanation of the return code (rc in the message text) in register 15.
Application Programmer Response: Respond as indicated for message IEC032I.

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 JCL and the program listing for the job.

Source: DFSMSdfp


1. Go to IBM:LookAt - z/OS Message Help.
2. Enter IEC032I where it says 1. Enter a Message ID.
3. Select your platform.
4. Click on GO.
5. Read the results.

Explanation: The error occurred when an output operation was requested. The data set was on a direct access or magnetic tape device.
In the message text:


rc
Associates this message with system completion code E37 and with the return code.

jjj
The job name.

sss
The step name.

ddname[-#]
DDname (followed by a concatenation number if it is part of a concatenation and not the first DD statement in the concatenation).

dev
The device number.

ser
The volume serial number.

mod
The name of the module in which the error occurred.

diagcode
The DADSM Extend diagnostic code, if available.


| dsname(member)
The data set name. Member name if specified.


The values of hex return codes and their meanings are as follows:

Return Code Explanation

04
A data set opened for output used all space available to or on the current volume, and no more volumes were available. Change the JCL to specify more volumes.

Not enough volumes were specified for the data set, through the SER, volume count, or REF subparameter of the VOLUME parameter of the DD statement. When all the volumes were filled, the program attempted to write another record.

For a partitioned data set on a direct access volume or for a VIO data set, all space was filled when the program attempted to write another record. (A partitioned data set or a VIO data set can reside on only one volume with a maximum of 65535 tracks.)

For a partitioned data set on a direct access volume, 16 extents had been used when the program attempted to write another record.


08
A multi-volume physical sequential data set was being written on a direct access device. All space was filled on the volume, and an attempt was made to obtain space on the next specified volume. Either the space was not available on that volume, the data set already existed on that volume, or there is no space available in the VTOC or the VTOC index. The message contains the volume serial number of the last volume used.

0C
An installation DADSM exit, IGGPRE00, rejected the extend request.


System Action: The task is ended unless the error is to be ignored as specified in the DCB ABEND exit routine. If the error is to be ignored, the system will attempt to close the DCB before returning to the user.
Operator Response: Start a generalized trace facility (GTF) trace, and re-create the problem. Reply to message AHL100A with:




TRACE=SYS,USR,SLIP


On the DD statement for the data set in error, specify:



DCB=DIAGNS=TRACE


Application Programmer Response: Probable user error. Correct the errors causing the abnormal end as indicated by the return code in the message text as follows:
For return code 04, case 1, specify at least one more volume than the number of volumes previously used for the data set. For case 2, specify a different volume for the partitioned data set or specify more space for the VIO data set.

For case 3, either specify a volume for the data set, use a utility program to reorganize the volume so that data sets will not be fragmented (that is, no more than 16 extents used for this data set), or change the program so that a device will be free when a volume must be mounted.

For return code 08, either specify a new volume to continue the data set or make sure that enough space is available on the volumes already specified. Ensure that the data set does not already exist on the volumes to be used. In all cases, rerun the job.

For return code 0C, consult your installation procedures.

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.

Source: DFSMSdfp

Detecting Module: IFG0554P

Routing Code: 11

Descriptor Code: 6
User avatar
MrSpock
Global moderator
 
Posts: 807
Joined: Wed Jun 06, 2007 9:37 pm
Location: Raleigh NC USA
Has thanked: 0 time
Been thanked: 4 times

Re: Jcl errors, abends and their remedies

Postby kaviyarasan » Thu Feb 21, 2008 12:24 pm

thank you MrSpock
kaviyarasan
 
Posts: 3
Joined: Mon Feb 18, 2008 8:44 am
Has thanked: 0 time
Been thanked: 0 time


Return to JCL

 


  • Related topics
    Replies
    Views
    Last post