IAM Catalog Return Codes
The following is a list of return codes and reason codes that IAM will set for a file DEFINE. When a file is defined under IDCAMS, these codes appear in the IDC3009I message. IDCAMS may print out other messages that relate to the failure code. Whenever possible, IAM uses codes that will have the same or similar meaning for VSAM files, however that is not always possible. There will be an IAM error message, with the IAMW prefix that should identify the error in more detail. Also, for most allocations, there will also be error messages generated by the failed dynamic allocation request, which IAM will print out. Due to the way IDCAMS displays messages, the error messages printed by IAM will actually appear before the card images for the actual DEFINE. Then, IDCAMS will print out its own error messages based upon the codes that IAM set.
Return Code | Reason Code | Error description: |
|---|---|---|
8 | 6 | Invalid type specified on a DELETE request. |
8 | 38 | Duplicate data set name found in the catalog, or on the volumes to which the data set is being defined. |
16 | 0 | SMS has failed the allocation request. Refer to the associated SMS error messages for additional information on the exact cause of the error. |
22 | 8 | The user attempted to define a cluster of a type not supported by IAM. IAM does not support LINEAR type of VSAM Clusters. |
22 | 12 | The user attempted to define an IAM AIX, PATH, or RRDS type of data set. The version of IAM being used is not licensed for the type of file that the user is attempting to define. |
42 | nnnn | MVS/ESA DADSM allocation of the data set failed. The reason code is the return code from DADSM. |
44 | 12 | The work area provided by the caller of a request for information from the catalog for an IAM file was not large enough to contain all of the requested information. |
54 | nnnn | MVS/XA DADSM allocation of the data set failed. The reason code is the return code from DADSM. |
56 | 6 | User is not authorized to define the data set, according to the security system. |
58 | nnnn | On a DEFINE RECATALOG request, the attempt to OBTAIN the VTOC information for the specified data set failed. The reason code is the return code from the OBTAIN service. |
58 | 4 | A CVAF service request issued by IAM during the define of an IAM file failed. CVAF indicated that the volume on which the data set was defined was not mounted. There should be a corresponding IAMW50 error message. |
58 | 8 | A CVAF service request issued by IAM during the define process of an IAM file failed. CVAF indicated that the DSCB for the IAM file was not found on the volume to which the IAM file was defined. There should be a corresponding IAMW50 error message. |
58 | 12 | A CVAF service request issued by IAM during the define process of an IAM file failed. The CVAF return code and reason code are on the associated IAMW50 error message. |
60 | 4 | A catalog information request was issued (locate SVC) which appeared to be for an IAM file, however either an error occurred during IAM processing, or the file is not an IAM file. Normally, this return code will only be set if an //IAMDEBUG DD DUMMY statement is included in the JCL. |
62 | 0 | The initialization of the IAM file being defined failed. There should be IAMWxx messages indicating the cause of the error. |
62 | 84 | IAM found an error within the block of the file containing the alternate index and path information. |
62 | 88 | There was insufficient space to add additional alternate index or path information. Using a larger block size for the base cluster may correct the problem. |
68 | 20 | The define request failed because there was insufficient space on the specified volumes to contain the data set. |
72 | 4 | During a define of an IAM file, IAM was not able to find one or more of the requested volumes online. |
80 | 2 | Attempted to define an AIX for an RRDS type of data set. As per VSAM restrictions, AIXs cannot be used for RRDS type of data sets. |
80 | 4 | During a define of an alternate index or path, the related data set or path entry data set was not found. Make sure that the related data set name or path entry data set name is specified correctly. |
80 | 10 | A define of an alternate index or path was missing the related or path entry name. |
80 | 12 | During a define of an alternate index or path, the related data set or path entry specified was invalid for the type of data set being defined. Make sure that the related data set is an IAM data set of the appropriate type (base for an alternate index define, and base or alternate index for a path define.) |
86 | 4 | During a define recatalog of an IAM data set, IAM encountered a failure attempting to determine the attributes of the file. The file most likely is not an IAM file. |
86 | 6 | During a define recatalog of an IAM data set, IAM could not find the data set on the specified volume. |
96 | 4 | Maximum record size for data set exceed IAM's maximum record size. |
96 | 8 | The base cluster record size is not large enough to contain the specified alternate key, or the calculated minimum alternate index record size exceeds the record size defined for the alternate index. |
132 | xx | During the define of an IAM file, the internal parameter list usually generated by IDCAMS was missing data. The reason code indicates the particular field that was not provided. This most likely is not a user error, but rather an error on the part of the software issuing the define. |
132 | 2 | No VOLUME FVT was found in the parameter list. |
132 | 4 | No AMDSB FVT was found in the parameter list. |
132 | 8 | No Average LRECL FVT was found in the parameter list. |
132 | 10 | No Space FVT was found in the parameter list. |
132 | 26 | No SPACE was found the FPL . |
132 | 34 | No attribute FPL was found (RGATTR FPL) on the define of an IAM Path or alternate index. |
132 | 48 | No AMDSB in the FPL. |
136 | 2 | No VOLUME information length. |
136 | 6 | No CLUSTER FVT found. |
136 | 18 | No Average LRECL found in the FPL |
140 | 36 | The IAMOVRID override statements contained an error, either in syntax or an unknown keyword was specified. |
140 | 72 | Duplicate volume found in volume list. |
140 | 120 | The define of an IAM file failed because it was assigned to a DATACLASS that specified COMPACTION (SMS Compression). IAM provides compression services so the SMS Compression can not be utilized. |
168 | 2 | IAM's internal device characteristics table does not contain an entry for the type of device on which the user is attempting to define an IAM file. If the device is a valid DASD device, Contact BMC for support. |
176 | 0 | The define of an IAM file failed because there was insufficient room in the VTOC on the specified volumes to contain an entry for the new file. The data set will have to be allocated on a different volume, or some data sets will need to be deleted from the target volume. Another option is to enlarge the size of the VTOC. |
184 | 4 | The define of an IAM file failed because the data set was in use by another job. |
192 | 0 | During the file define, IAM determined that the maximum record length being requested is longer than IAM supports for files without the SPANNED attribute. IAM can support records up to 32,760 bytes long if they are not spanned. |
204 | 0 | The key length and the key offset exceeds the specified record length. |
240 | 4 | IAM was unable to determine the device characteristics for the volume requested on the file define request. |
240 | 36 | On the file define, the required DD statement for the volumes on which the data set is to be defined was not found, or was not provided. This return code should normally not be seen by an end user. |