IAM Open and Close Error Codes
In keeping with the VSAM application programming interface, most errors that occur during Open or Close will not cause an abend. Rather, a non-zero return code is passed in register 15, and an error code is set in the ACBERFLG field of the ACB. The error code can also be retrieved by the SHOWCB macro, requested for the failing ACB. Request FIELDS=ERROR in the SHOWCB macro to obtain the error code. Most of the IAM Open or Close failures will result in an IAMWxx error message being generated. Refer to the message for additional information.
Return Code | Error Code (Decimal) | Error Code (Hex) | Description of Error Condition: |
|---|---|---|---|
04 | The CLOSE for the IAM file failed. See reason codes below. This could also be returned on OPEN to indicate that there was a warning message issued for one or more files being opened. The ACBERFLG should be checked for each ACB being opened. | ||
04 | 4 | X'04' | A CLOSE was requested for an ACB that was already closed. |
04 | 100 | X’64’ | This is a warning that on an open for a PATH or base cluster with an alternate index(es) in an upgrade set, one or more of the alternate index data sets were found to be empty. |
04 | 136 | X'88' | Insufficient storage in region to close the file. Most likely, there is insufficient below the line storage to obtain work areas for the file close. Perhaps, by closing other files first, if possible, will correct this circumstance. It may be necessary to raise the value of the REGION parameter for this job step. |
04 | 144 | X'90' | The CLOSE for an IAM file being loaded or reorganized failed, due to insufficient DASD space to write out the file's index. Delete and redefine the file with more DASD space. |
08 | Open Error Occurred. The file is not opened, see reason codes below for further information. | ||
08 | 128 | X'80' | DD Statement for the specified data set is not in the JCL. This also will be issued when one of the macros issued by IAM to OPEN the data set fails, such as OPEN, DEVTYPE, or TRKCALC. |
08 | 136 | X'88' | Insufficient storage in region to open the file. Most likely, there is insufficient extended private storage, however, there could also be insufficient below the line storage. Check message IEF374I to determine how much storage was used. Most likely increasing the REGION parameter will solve the problem. |
08 | 152 | X'98' | RACF, or other system security software, indicated that the user was not allowed the type of access to the file that was being requested by the ACB on the OPEN macro. |
08 | 160 | X'A0' | The application attempted to open an IAM file for input processing, however, either the file had never been loaded, or an attempted file load or reorganization failed. Or, the application attempted to open an unloaded file with a STRNO value not equal to 1. |
08 | 167 | X’A7’ | IAM-RLS has encountered an abend attempting to open or close this data set. |
08 | 168 | X'A8' | The specified file was already being processed by another job or user, and could not be opened for the processing that the application requested. Check for an IAMW04 or IAMW30, which will, when possible, include the name of the job that had the file opened. Rerun the failing job after the identified job terminates. |
08 | 182 | X’B6’ | The Open was failed because the IAM-RLS was not active. |
08 | 184 | X'B8' | An I/O error occurred while trying to open the indicated file. This error code should be accompanied by either an IAMW37 or an IAMW07 error message, indicating the nature of the I/O error. |
08 | 188 | X'BC' | Open processing encountered a problem while attempting to Open the file. If the file was being loaded, an invalid or unsupported record length was specified for the file. This error may also be due a problem with the extended data areas of the file. There should be an IAMWxx message indicating the reason for the error. |
08 | 192 | X'C0' | Open processing failed for a file load, due to an invalid file attribute being specified. This should be accompanied by an IAMW20 error message, indicating the improperly specified attribute. |
08 | 196 | X’C4’ | Open processing failed on a PATH because the alternate index object of that PATH was empty. |
08 | 209 | X’D1’ | The open for this file failed under IAM-RLS. Review the IAM-RLS log for additional information. |
08 | 232 | X'E8' | An attempt was made to Open a loaded IAM file for reloading with ACB MACRF=RST, however, the file was defined with the NOREUSE attribute, and the IAM Global Option was set to ENABLE=NOREUSE. The file must be deleted and redefined to be reloaded. |
08 | 240 | X'F0' | The file was already open by another ACB (or DD) in this address space, and the current attempt to OPEN the file failed because the time stamp for file load was different than the time stamp in the previously opened ACB. Close all open ACB for this data set in this address space, and then they can be reopened. |
08 | 241 | X'F1' | The IAM VSAM Interface was not able to find a proper version of the IAM processing module required to OPEN this file. |
08 | 242 | X'F2' | The file was being opened for OUTPUT with an expired trial version of IAM. |
08 | 248 | X'F8' | Internal IAM error, the Open request failed. |
08 | 254 | X'FE' | The IAM VSAM Interface either was unable to successfully LOAD the required IAM processing module, or a version was loaded that does not match the version of the IAM VSAM Interface (VIF) that is active. |