Explanation
The error occurred during processing of a CLOSE macro instruction for a data set on a direct access device or a subsystem data set.
In the message text:
- rc
- Associates this message with system completion code 614 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.
- dsname(member)
- The data set name. Member name if specified.
The explanation for the hex return code is as
follows:
- Return Code
- Explanation
- 04
- Either an I/O error occurred writing a file mark for a data set on a direct access device during processing of a CLOSE macro instruction or I/O prevention has completed.
- 08
- A file mark should have been written on an output data set. The DCBFDAD field in the DCB indicated an extent number in the DEB greater than the number of extents in the data set. Consequently, it could not be determined where the file mark should have been written.
- 0C
- The close subsystem executor module was passed an error return code in register 15 after issuing the IEFSSREQ macro to connect to the subsystem. This indicates the subsystem was not operating.
- 10
- A spooled or subsystem data set or a z/OS® UNIX file could not be closed by a subsystem. The failing DCB could not be closed. Generally there is another message to explain the failure further.
- 14
- A CLOSE macro instruction detected an error return code from an SMS service while processing a PDSE data set.
- 18
- During the execution of a CLOSE macro instruction, an error was returned from a system function called to process a PDSE containing program objects.
- 1C
- During the execution of a CLOSE macro instruction, an error was returned from a system function called to process a PDSE containing program objects.
- 20
- CLOSE detected a bad return code from a system service used in calculating DS1LSTAR for a stripe of an extended format data set. The DS1LSTAR field is in the data set label (DSCB or data set control block). It identifies the last user block on the volume.
- 24
- An error occurred when the system attempted to write a software file mark at the end of an extended format data set. This was during execution of a CLOSE macro instruction.
- 28
- A catalog error occurred attempting to update the catalog record for an attribute extension data set during execution of a CLOSE macro instruction.
- 30
- Statistics (compressed and uncompressed data sizes) in the catalog are incorrect for a data set in the compressed format. The data set may be damaged.
- 34
- Error attempting to access a catalog while processing a data set in the compressed format.
- 38
- During close processing, an error was encountered while processing the dictionary token or the tailored dictionary of a compressed format data set created with tailored compression.
- 3C
- During close processing, an error was encountered while attempting to compress a user block for a compressed format data set using tailored compression.
- 40
- During close processing, an error was returned from the routine (IGG019VT) responsible for processing the tailored dictionary of a compressed format data set.
- 44
- During close processing, while attempting to store a dictionary token in the catalog for a compressed format data set being created with tailored compression, it was discovered that a dictionary token had been stored in the catalog since the time this DCB was opened. This implies that instruction with a TYPE=T operand.
- 48
- Data conversion requested for an ISO/ANSI Version 4 tape. The system encountered a problem attempting to free resources obtained for conversion tables used during input processing.
- 4C
- Data conversion requested for an ISO/ANSI Version 4 tape. The system encountered a problem attempting to free resources obtained for conversion tables used during output processing.
- 54
- CLOSE detected that processing of a newly derived tailored dictionary and associated data did not complete successfully.
58
- During close processing for an extended format sequential data
set with zEDC compression, while preparing to flush the intermediate
compression buffer (ICU), an unexpected error was encountered attempting
to serialize the autodata area for the call to the internal compression
routine (IGG019VX).
- 5C
- During close processing for an extended format sequential data
set with zEDC compression, an unexpected error was received from the
internal compression routine (IGG019VX) while attempting to flush
the intermediate compression buffer (ICU).
- 60
- During close processing for an extended format sequential data
set with zEDC compression, it was determined that the zEDC Compression
Services compress/decompress (FPZ4ABC) service was unexpectedly still
in progress.
- 64
- During close processing for an extended format sequential data
set with zEDC compression, an error return code was encountered from
the zEDC Compression Services memory deregister (FPZ4DMR) service.
The SAM internal control block (SSCB) diagnostic area contains the
error return and reason code returned from the service.
System action
The task is ended unless the error is to be ignored as specified in the DCB ABEND exit routine.
Operator response
Start a generalized trace facility (GTF) trace,
and re-create the problem. Reply to message AHL100A with:
TRACE=SYS,USR,SLIPOn
the DD statement for the data set in error, specify:
DCB=DIAGNS=TRACESystem 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.
Programmer response
If an I/O error has occurred, a defective volume or device may be the cause. Save the output from the failing job to aid in the analysis of the problem.
Rerun the job specifying a different volume or device. If a scratch volume was being used when the I/O error occurred, request a different volume. If that does not solve the problem, request a different device in the UNIT parameter of the DD statement. If a specific volume is needed, try requesting a different device in the UNIT parameter of the DD statement. Rerun the job.
Source
DFSMSdfp
Module
IFG0232G
Routing code
11
Descriptor code
6