IEC143I 213-rc,mod,jjj,sss, ddname[-#],dev,volser,dsname(member)

Explanation

An error occurred during the processing of an OPEN macro instruction for a data set on a direct access device. This is probably a user error.

In the message text:
rc
Associates this message with system completion code 213 and with the return code.
mod
The name of the module in which the error was detected.
jjj
The job name.
sss
The step name.
ddname[-#]
The data definition (DD) name, followed by a concatenation number (#) if the DD statement is part of a concatenation and not the first DD statement in the concatenation.
dev
The device number.
volser
The volume serial number.
dsname(member)
The data set name. Member name if specified. If the value of dsname in the message is …PATH=.SPECIFIED…, the problem was with a z/OS® UNIX file.
Explanations of the hexadecimal return codes follow.
Return Code
Explanation
04
One of the following:
  • An I/O error occurred in reading the format-1 data set control block (DSCB). Refer to the information in the accompanying message IOS000I to determine the cause of the I/O error.
  • The format-1 DSCB for the data set could not be found on the first volume (the volume indexed by the volume sequence number) specified by the DD statement or the catalog. For this case, make sure that the DSNAME and VOLUME parameters in the DD statement or in the catalog are correct.
  • The data set name in the JFCB passed to OPEN has been incorrectly modified.
  • The volume serial number of the data set name supplied in the JFCB passed to OPEN was not available to the job because it was being used by some other job. (It's possible that the volume serial number in the JFCB of either this job or the other job which is already using the volume, has been incorrectly modified.) Either the data set was being opened for INPUT and some other job had exclusive control of the data set (either referenced the data set in a DD control statement with DISP of OLD or MOD, or issued an OPEN TYPE=J macro instruction with processing option INOUT, OUTIN, OUTPUT, OUTINX, EXTEND, or UPDATE), or the data set was being opened for an option other than INPUT (INOUT, OUTIN, OUTPUT, or UPDATE: requiring exclusive control of the data set) and some other job was using the data set (either referenced the data set in a DD control statement, or issued an OPEN TYPE=J macro instruction).
08
An OPEN macro instruction was issued for a password-protected data set, but the system was unable to locate the PASSWORD data set. Make sure that the PASSWORD data set exists on the system residence volume. If this data set does not exist, build it and run the job step again.
0C
An I/O error occurred in reading a format-1 DSCB for a direct-sequential or indexed-sequential data set, or the format-1 DSCB could not be found on the volume specified by the DD statement for a direct-sequential or indexed-sequential data set. Ensure that the DSNAME and VOLUME parameters in the DD statement are correct.
10
OPEN failed because the data set type was large format sequential, but the access method was not QSAM, BSAM or EXCP or the DCB did not specify DSORG=PS.
14
OPEN failed because the data set type was large format sequential, but the application program could not access the whole data set on the volume. Both of the following are true:
  • The access method is either EXCP being opened for UPDAT or output processing or the access method is BSAM with the NOTE or POINT function requested and is being opened for output processing.
  • BLOCKTOKENSIZE=LARGE is not specified on the DCBE.
15
OPEN failed because the data set type was large format sequential but the application program could not access the whole data set on the volume. All of the following are true:
  • The access method is EXCP, BSAM or QSAM being opened for UPDAT or output processing.
  • BLOCKTOKENSIZE=LARGE is not specified on the DCBE.
  • BLOCKTOKENSIZE(REQUIRE) is specified in PARMLIB member IGDSMSxx.
16
OPEN failed because the data set type was large format sequential, but the application program could not access the whole data set on the volume. All of the following are true:
  • The access method is either EXCP or it is BSAM with the NOTE or POINT function requested
  • The DCB is being opened for input processing.
  • BLOCKTOKENSIZE=LARGE is not specified on the DCBE.
  • The data set has more than 65535 tracks allocated on the volume.
17
OPEN failed because the data set type was large format sequential, but the application program could not access the whole data set on the volume. All of the following are true:
  • The access method is EXCP, BSAM or QSAM being opened for input processing.
  • BLOCKTOKENSIZE=LARGE is not specified on the DCBE.
  • The data set has more than 65535 tracks allocated on the volume.
  • BLOCKTOKENSIZE(REQUIRE) is specified in PARMLIB member IGDSMSxx.
18
An I/O error occurred in writing back a format-1 DSCB.
1C
An OPEN macro instruction was issued for an ISAM data set, and failed because ISAM is no longer supported. For OPEN to succeed, the data set must be converted to VSAM.
20
During an open, a volume contained more than 16 extents of the indicated data set.
24
During an open, a volume of the indicated data set had a type of split cylinder allocation that is not supported under the operating system.
28
An OPEN macro instruction was issued for a demountable direct-access data set, UNIT=SYSDA, but the unit already contained 127 users, the maximum number. This should never occur for any currently supported direct-access devices.
2C
The DFSMShsm format-1 DSCB-not-found module encountered an error.
30
An attempt was made to open a partitioned data set (PDS) for OUTPUT,DISP=SHR. The PDS is already open in this condition, and a DCB is already open for output to the data set. The data set might be on the same system or on another system that is sharing the volume. Access was not serialized before the attempt to open the data set.
34
An OPEN macro instruction was issued for a compressed-format data set created with tailored compression on a system that does not support accessing such a data set.
38
An OPEN macro instruction was for a partitioned data set extended (PDSE) and one of the following conditions was not satisfied:
  • A DCB key length of zero is required if output operations are to be performed on a PDSE or extended-format data set.
  • A key length of zero or eight is required if input operations are to be performed on the directory of a PDSE.
3C
An OPEN macro instruction was issued with a RECFM value that specified a format different from that specified by the format-1 DSCB, and the data set was a PDSE or compressed data set.
40
An OPEN macro instruction was issued for a PDSE with a DCB specification indicating MACRF=(E). MACRF=(E), EXCP, is not supported for PDSEs.
44
The program issued an OPEN macro to extend a UNIX file with binary records, but the DCB record format was F(B) and the size of the file was not evenly divisible by the record size in the DCBLRECL. Either the OPEN option was EXTEND or OUTINX, or DISP=MOD was coded with an OPEN option of OUTPUT or OUTIN.
48
OPEN detected a bad return from the extended cache attribute facility.
4C
OPEN was issued for output against a PDSE and the DCB indicated a DSORG of PS, but no member was specified.
50
OPEN detected an error return code from an SMS service while processing a PDSE.
52
An OPEN macro instruction was issued to a data set that resides on a read-only device, but the system does not support the combination of access method and OPEN macro option. The supported non-VSAM access methods are BSAM, QSAM and EXCP, The OPEN option must be INPUT, INOUT, or UPDAT.
56
An OPEN macro instruction was issued to a data set that resides on a device that requires the user program to indicate that it can tolerate reading inconsistent data due to concurrent writes. The program did not specify CONCURRENTRW=(YES,TRKLOCK) on the DCBE macro. For more information, see z/OS DFSMS Macro Instructions for Data Sets.
58
An attempt was made to change the DSORG value in the Format1 DSCB for an SMS-managed data set either from PS to PSU or from PO to POU. Unmovable data sets are not supported on SMS-managed volumes.
60
OPEN detected an error return code from the resident convert routine while processing a PDSE.
64
An incorrect OPEN option was specified for a PDSE.
68
An OPEN macro instruction was issued for a PDSE with RECFM = FB(S) and LRECL = 0.
6C
An OPEN macro instruction issued for a PDSE requested a QSAM update, but locate mode was not specified in MACRF.
70
OPEN detected a cross-system share conflict for the PDSE.
74
OPEN detected a member share option conflict for the PDSE.
78
An OPEN macro instruction was issued against a PDSE; however, the primary space amount was zero.
7C
An OPEN macro instruction for output was issued against a PDSE, but a DFSMSdss dump (or equivalent function) was in progress.
81
Bypassing decryption for an encrypted extended format data set is requested via the UDA (UDANOENCRYPTION). However, either the data set is open for update or output, or the data set is compressed format but UDACI is not specified.
82
BSAM CI mode processing is requested via the UDA (UDACI), however it is not supported for a zEDC compressed data set.
83
During open processing for an encrypted extended format data set, the system detected that either the encryption cell in the catalog does not exist or the key label in the encryption cell does not exist.
84
OPEN detected a bad return code from the SETLOCK macro instruction while attempting to get or release the local lock around a branch entry GETMAIN. The data set is a PDSE or extended-format data set.
85
During open processing for an encrypted extended format data set, an unexpected error was received from the ICSF service CSNBKRR2 used to process the key label associated with the data set. In this case, additional diagnostic information can be found from the return code and reason code returned from the service.
86
During open processing for an encrypted extended format data set, on return from the ICSF service used to process the key label associated with the data set, the system detected that the encryption type of the data key associated with the key label was not of a supported encryption type. Only encryption keys of type AES256 are supported for extended format data sets.
87
During open processing for an encrypted extended format data set, an unexpected error was received from the BCFXCRYP service used to prepare for encryption processing for this data set. In this case, additional diagnostic information can be found from the return code and reason code returned from the service.
88
An OPEN macro instruction was attempted for a path, using a DCB, but the system does not support the combination of access method and OPEN macro option. With BSAM and QSAM, OPEN supports any options except RDBACK and UPDAT. With BPAM, the system supports only the INPUT option of OPEN.
89
An attempt was made to open a new encrypted non-compressed Start of changeextendedEnd of change format sequential data setStart of change, or basic or large format data set,End of change for output with QSAM using a BLKSIZE less than 16 bytes. However, the minimum blocksize supported for encrypted non-compressed Start of changeextendedEnd of change format sequential data setsStart of change, and encrypted basic or large format data sets,End of change is 16 bytes.
Start of changeThis also applies for an attempt to open a new encrypted basic or large format data set for output, where LRECL is specified and LRECL is < 16 bytes with RECFM=F(B(S)) or LRECL is < 12 bytes with RECFM=V(B(S)). This avoids the potential for failures due to an attempt to write a block less than 16 bytes during writing or QSAM buffer flushing at CLOSE.End of change
8C
An OPEN macro instruction was attempted for an HFS data set, using a DCB. You cannot use BSAM or QSAM OPEN to open a data set with DSNTYPE=HFS.
90
An OPEN was attempted for a PDSE data set while a restore operation was in progress.
91
During open processing for an encrypted extended format sequential data set, the system determined that the data key in the CKDS associated with the key label for the data set is not the same data key used to encrypt the data set.
Start of change93End of change
Start of changeDuring open processing, the access method encryption macro, IGGENC, detected that an input parameter to the service was incorrect. In this case, the message includes additional diagnostic information (return code and reason code) returned from the macro.End of change
94
An OPEN macro instruction was attempted against an extended-format data set, but the access method is not BSAM or QSAM, or is BDAM load mode.
Start of change95End of change
Start of changeDuring open processing, the access method encryption macro, IGGENC, detected that a field in the encryption cell for the data set is not valid. In this case, the message includes additional diagnostic information (return code and reason code) returned from the macro.End of change
Start of change96End of change
Start of changeDuring open processing, the system was unable to obtain storage required for encryption processing. In this case, the message includes additional diagnostic information (return code and reason code) returned from the service. End of change
98
An OPEN was issued for an extended-format data set that consists of more than one stripe, but the volumes specified were not in the correct ascending sequence.
Start of change99End of change
Start of changeDuring open processing, the system was unable to open the data set. See additional diagnostic information (4- byte return code and 4-byte reason code) to identify the reason.
DIAG=keylength, RC=8, RSN=1
An attempt was made to open an encrypted basic or large format data set with a non-zero key length. DIAG has the key length.
DIAG=BDAM, RC=8, RSN=2
BDAM attempted to open an encrypted basic or large format data set. DIAG indicated BDAM open detected the error.
DIAG=IGGENC, RC=8, RSN='0000000000001511'X
An attempt was made to open an encrypted basic or large format data set with a BSAM or QSAM DCB and the DCBEDSENCNP bit was specified or the flag was on in the encryption cell indicating the blocks in the data set do not have prefixes. The DCBEDSENCNP bit means that the application program is writing/reading encrypted blocks without prefixes. BSAM and QSAM access is not supported with encrypted basic and large format data sets that do not have block prefixes.
DIAG=IGGENC, RC=8, RSN=0000000000001521'X
An attempt was made to open an encrypted basic or large format data set with an EXCP DCB, however, the settings for DCBEDSENDNP and the flag in the encryption cell indicating blocks in the data set do not have prefixes, are not consistent. The DCBEDSENCNP bit means that the application is writing/reading encrypted blocks with no prefix. The flag in the encryption cell means that the blocks in the data set do not have prefixes. For other than the first open for output, either both must be off or both must be on. When attempting to access an existing encrypted basic or large format data set which does not contain block prefixes, the non-prefixed blocks setting in the application and the data set encryption cell must both be on.
DIAG=IGGENC, RC=X'00000008', RSN=X'00000000 00001531'
An attempt was made to open an encrypted basic or large format data set with a BSAM or QSAM DCB and the DCBEDSENCNP bit was specified or the non-prefixed bit (VVREDSENCNP) was on in the encryption cell indicating the blocks in the data set do not have prefixes. The DCBEDSENCNP bit means that the application program is writing encrypted blocks without prefixes. BSAM and QSAM access is not supported with encrypted basic and large format data sets that do not have block prefixes.
End of change
Start of change9AEnd of change
Start of changeAn attempt was made to open an encrypted basic or large format data set with an EXCP DCB and DCBE DSENCRYPT=OK was not specified.End of change
9C
An OPEN macro instruction was issued with a DCB that pointed to a data control block extension (DCBE) that had a nonzero DCB pointer. The DCB address in the DCBE must be zero before OPEN is issued.
A0
OPEN detected a bad return code from TRKCALC while processing an extended-format data set.
A4
OPEN detected a bad return code from a system service used in calculating the high-allocated relative byte number (RBN) of an extended-format data set.
A8
OPEN detected that the stripes of an extended-format data set were not consistent.
AC
OPEN detected that the last volume indicator in the volume label of one of the stripes of an extended-format data set was set incorrectly.
B0
OPEN detected that the last volume indicator was not set in the last stripe of an extended-format data set.
B4
OPEN detected that the volume sequence number in the volume label of one of the stripes of an extended-format data set was incorrect.
B8
An OPEN was attempted against an extended-format data set with a DCB that specified EXCP. EXCP is not supported for extended-format data sets.
BC
An OPEN macro instruction was issued; however, the DCB specified BDAM and OPTCD=A, which is invalid.
C0
An OPEN macro instruction was attempted against an extended-format data set; however, one or more of the stripes did not satisfy the hardware requirements of an extended-format data set.
C4
An OPEN was issued for an extended-format data set, which is not supported on this level of the system.
C8
An attempt was made to open a compressed data set for update. The update option is not supported for compressed data sets.
CC
The compressed indicator is on in the DSCB, but the extended format-indicator is off.
D0
OPEN encountered an error attempting to access the catalog while processing a data set in the compressed format.
D4
OPEN was unable to calculate a physical block size for a data set in the compressed format.
D8
OPEN detected that no physical block size was found in the catalog for a compressed-format data set.
DC
Error return code from compression services OPEN.
E0
A null dictionary token was found in a catalog for a compressed-format data set open for input, and the data set is not empty.
E2
During open processing, an error was encountered in reading a tailored dictionary from a compressed-format data set.
E3
During open processing, an invalid dictionary token for a tailored compressed-format data set was encountered.
E4
OPEN encountered an I/O error while attempting to read in the last block of a compressed-format data set.
E5
During open processing, an invalid tailored dictionary was found within a compressed-format data set.
E6
During open processing, an error was encountered from compression services in validating a tailored dictionary for a compressed-format data set.
E7
During open processing, an error was returned from the routine responsible for processing the tailored dictionary of a compressed-format data set (the IGG019VT routine).
E9
During open processing, a physical sequential data set was found within a partitioned concatenation.
EA
During open processing for an extended format data set with tailored compression, a volume sequence number other than 1 was found on the format-1 DSCB on the first volume. The DSCB might be incorrectly modified, or a volume is missing or out of sequence causing the data set to be defective.
F0
An error occurred in reading the format-1 DSCB on one of the volumes of an extended-format data set during the calculation of the size of the data set because GETSIZE=YES was coded in the DCBE macro.
F1
An error was received from the zEDC Rendezvous service when an attempt was made to Open an extended format sequential data set with zEDC compression during task or address space termination.
F4
An error occurred in reading a DSCB on one of the volumes of a compressed-format data set during the calculation of the size of the data set because GETSIZE=YES was coded in the DCBE macro.
F8
The OPEN function for BSAM or QSAM access to a UNIX file found that the file type is not supported. For example, BSAM and QSAM do not support an external link.
FA
During open of a zEDC compressed format data set, an invalid physical blocksize (VVRNCISZ) was found in the catalog.
FB
During open of a new zEDC compressed format data set an invalid physical blocksize was derived.
FC
The OPEN function for BSAM or QSAM access to a UNIX file found that the file does not exist.
FD
An attempt was made to open a physical sequential data set for output with DISP=SHR when the data set was already opened for output processing and enhanced data integrity MODE(ENFORCE) was active.
FE
During open processing for an extended format sequential data set with zEDC compression, an unexpected error was received from the zEDC rendezvous service.
FF
During open processing for an extended format sequential data set with zEDC compression, an unexpected error was received from module (IGG019VS) responsible for initializing task level control blocks to be used for zEDC compression processing.

System action

The system ends the task, unless the DCB ABEND exit routine specifies that the error is to be ignored. For return code 30, DFSMSdfp also issues message IEC813I.

Operator response

Start a generalized trace facility (GTF) trace, and re-create the problem. Enter the following reply to message AHL100A:
TRACE=SYS,USR,SLIP
In the DD statement for the data set in error, specify these values:
DCB=DIAGNS=TRACE

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 databases for a fix for the problem. If no fix exists, contact the IBM® Support Center. Provide the SYSOUT output for the job.

Programmer response

Correct any user error that caused the abnormal end of the task, as indicated by the return code in the message text. Rerun the job.

Return code 04 indicates a probable user error. If an OPEN TYPE=J macro instruction is issued to a data set not referenced in a DD JCL statement, the normal procedures for data set protection are not performed with the JOB is initiated, but must be performed at open time when no recovery is possible. The issuer of such an OPEN TYPE=J must ensure that no other JOB is processing the data set in a manner which is in conflict with the processing requested by the OPEN macro instruction. This can best be accomplished by not using the OPEN TYPE=J macro instruction to open to a data set which is not already referenced in a DD control statement, and not opening with a processing option of INOUT, OUTIN, OUTPUT, OUTINX, EXTEND or UPDAT unless the DD control statement indicates DISP=OLD OR DISP=MOD. Ensure that the JFCB has not been incorrectly modified.

For return code 10, (a) update the DSORG to be PS or (b) update the access method to be either EXCP, BSAM or QSAM.

For return code 14, (a) update the DCB to point to a DCBE macro with BLOCKTOKENSIZE=LARGE and if necessary modify the program to handle large format data sets as described in z/OS Using Data Sets, or (b) if the data set contains 65535 or fewer tracks, ensure the OPEN option is INPUT (with BSAM or EXCP) or UPDAT (with BSAM).

For return code 15, (a) update the DCB to point to a DCBE macro with BLOCKTOKENSIZE=LARGE or (b) if the data set contains 65535 or more tracks, ensure the OPEN option is OUTPUT, OUTIN, OUTINX, INOUT or EXTEND (with any access method) or UPDAT (with BSAM or QSAM).

For return code 16, (a) update the DCB to point to a DCBE macro with BLOCKTOKENSIZE=LARGE or (b) if the data set contains 65535 or more tracks, ensure the OPEN option is INPUT (with BSAM or EXCP) or UPDAT (with BSAM).

For return code 17, (a) update the DCB to point to a DCBE macro with BLOCKTOKENSIZE=LARGE or (b) if the data set contains 65535 or more tracks, ensure the OPEN option is INPUT (with any access method) or UPDAT (with BSAM or QSAM).

For return code 2C, contact the IBM Support Center.

For return code 30, see message IEC813I to determine who owns the PDS resource that is preventing this open from being successful.

For return code 38, set the key length to zero if output operations are to be performed, or set the key length to zero or eight if input of the directory is to be attempted. Rerun the job. Optionally, you can rerun the job with no changes if allocation of the PDSE is changed to the allocation of a PDS.

For return code 3C, you can change the record format so that the blocked attribute can be removed or added. A fixed data set, however, cannot be accessed as variable, and a variable data set cannot be accessed as fixed. Rerun the job after changing the DCB to utilize the record format consistent with the DSCB.

For return code 44, change the file name, the file length, or the record format.

For return codes 48, 50, and 60, contact the system programmer.

For return code 4C, output to a PDSE directory is not allowed. If you attempt to write to the PDSE, either specify a member name or specify DSORG = PO. If you attempt to access the directory, open it for input.

For return code 64, verify that the DCB does not specify an option that is not allowed for a new library, such as RDBACK.

For return code 68, verify that the DCB specifies a correct LRECL if RECFM = FB is specified.

For return code 6C, QSAM update can be used only with locate mode. Modify the DCB to specify locate mode in MACRF.

For return code 70, ensure that share restrictions are not violated for a PDSE accessed by multiple computer processor complexes (CPCs).

For return code 74, ensure that the PDSE member is not being opened for update-in-place (UPDAT).

Contact the system programmer for the following return codes: D0, D4, D8, DC, E0, and E4.

For return code E9, DSORG=PO is specified in the DCB, but one or more of the concatenated data sets are not PDSs or PDSEs. BPAM concatenation requires that all the concatenated data sets be PDSs or PDSEs. Correct the error and rerun the job. In this case, the message displays the concatenation number and the data set name for the first data set in the concatenation, and, therefore, does not identify the data set in error.

For return code F8, choose a different file.

For return code FC, change the file name or create the file.

For return code FD, opening a PS data set for output while it is already open for output is not allowed by the enhanced data integrity function. Correct the application, have the system programmer add this data set name to the exclude list in the PARMLIB member IFGPSEDI, or bypass enhanced data integrity processing by setting the DCBEEXPS bit on in the DCBE or by specifying the "bypass data set integrity" option in the program properties table or the dynamic allocations options. For information about specifying the "bypass data set integrity" option, see z/OS MVS Initialization and Tuning Reference.

For return code EA, run the IEHLIST utility with LISTVTOC FORMAT for the data set on each of the data set volumes. The volume sequence number, which is returned in the 'SEQNO' column, must be 1 for the first data set on the first volume. Subsequent volume sequence numbers must be greater by one and in ascending sequence. If the volume sequence numbers are correct check the catalog to verify that the volumes are cataloged in the correct order.

Problem determination

Not applicable

Source

DFSMSdfp

Module

IFG0194A

Routing code

11

Descriptor code

6