IEC020I 001-rc,mod,jjj, sss,ddname[-#],dev,ser,dsname or 001-rc,mod,jjj, sss,code
Explanation
The first form of the message is followed by one
of the lines:
- NO ERROR HANDLING, (SYNAD), EXIT SPECIFIED
- ERROR OCCURRED WHILE CLOSING DATA SET
- NON-ACCEPTABLE ERROR
- DCB EROPT=ABE OR AN INVALID CODE, AND/OR NO SYNAD EXIT SPECIFIED
- GET ISSUED AFTER END-OF-FILE
The second form of the message is followed by one of the
lines:
- NO SYNAD EXIT SPECIFIED
- EROPT IS 'ABE' OR NOT SPECIFIED
- HFS/REMOTE FILE POSITIONING ERROR
A 001 system completion code was issued for the current task because of an I/O error or simulated I/O error.
In the
message text:
- rc
- The return code.
- mod
- The name of the module.
- 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 serial number of the volume.
- dsname
- The data set name.
- code
- One of the following:
- USS
- The DCB is open to a z/OS UNIX file.
- JES
- The DCB is for a subsystem such as JES2 or JES3.
- Three or four hexadecimal digits
- The DCB is for a device and these are the device number.
For partitioned concatenated data sets, dsname is the name of the first data set in the concatenation and is not necessarily the data set causing the error.
The unit address, volume serial number, and data set name fields do not appear in the message text when it applies to a subsystem data set, such as SYSIN or SYSOUT or to a z/OS UNIX file or directory.
- If the return code is 0, the logical record length and block size specified in the data control block (DCB), DCB extension (DCBE), or DD statement differ from the logical record length and block size indicated in the data set.
- If the return code is 1, an I/O error occurred during BDAM, BSAM,
BISAM, QSAM, QISAM, or BPAM and no SYNAD exit was specified by the
user. For BSAM or BPAM, one of the following conditions might be true:
- RECFM=U was specified on the DCB macro instruction, but no logical record length was specified.
- A write was attempted to a data set that was opened for input.
- A read was attempted to a data set that was opened for output.
- For concatenated data sets, some data set in the concatenation has attributes that are different from the attributes of the first data set in the concatenation. For example, some data set may have a different block size from the first data set and OPEN could not determine this.
- If the return code is 2, an error was encountered while attempting to close the data set.
- If the return code is 3, for QSAM, an unacceptable error occurred
because of one of the following:
- The caller returned from the SYNAD.
- The caller did not provide a SYNAD.
- If the return code is 4, for QSAM, ABE or an incorrect value for EROPT parameter in the DCB and/or no error handling (SYNAD) exit was specified.
- If the return code is 5, for QSAM, a GET was issued after end-of-file.
- If the return code is 6, an error occurred while the POINT function was reading the UNIX file to find the desired position.
System action
With the first form of the message, if OPEN/CLOSE/EOV tracing is in effect, perhaps due to DIAGNS=TRACE, pertinent control blocks are recorded on the GTF data set. The task abnormally ends.
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.
Programmer response
Correct any errors that caused the abnormal
end. Then run the job step again. Corrective procedures for the problems
mentioned above are as follows:
- If no error analysis routine was available, specify the address of a SYNAD routine in the SYNAD operand of the DCB or DCBE macro instruction.
- If the EROPT parameter in the DCB is incorrect, correct the value of the EROPT operand in the DCB macro instruction or in the DCB subparameter of the appropriate DD statement. If desired, specify the ACC or SKP option for the EROPT operand.
- Be sure the problem program does not issue a GET macro instruction after an end-of-data condition.
- If an out-of-space condition was detected, change the JCL SPACE parameter in the DD statement for the data set to specify a larger primary quantity or add a secondary quantity.
- If the logical record length and/or block size is incorrect, correct the value of LRECL and/or BLKSIZE in the DCB macro instruction or in the DCB subparameter of the DD statement.
- If the POINT macro instruction is incorrect, correct the relative track address or block number operand.
- If a hardware error has occurred, see the explanation of the accompanying IEA000I error message.
Source
DFSMSdfp
Module
IGG019DN, IFG0551D, IFG0554T, IGC0005E, IGG019LI, IGG019AH
Routing code
11
Descriptor code
6