VSE/VSAM Return and Error Codes

When VSAM returns control after it processed a VSAM macro (other than ACB, RPL, or EXLST), register 15 contains a return code indicating success or failure of the requested operation. A return code of X'00' usually indicates a successful operation.

If register 15 indicates that the requested operation failed, VSAM also provides an error code. Error codes are listed and explained below, grouped by the type of request and by the return code in register 15.

This listing of the error codes is included because they are displayed in some of the system messages that may be originated by VSAM. To examine VSAM error codes during execution of your problem program:

Use keyword ERROR of the SHOWCB or TESTCB macro for OPEN, CLOSE, and TCLOSE.
Use keyword FDBK of the SHOWCB or TESTCB macro for a request macro. GET, PUT, POINT, ERASE, ENDREQ, and WRTBFR are request macros.
Test register 0 for a control block manipulating macro (GENCB, MODCB, SHOWCB, and TESTCB).

Unless explicitly provided as part of the explanation for a reason code, programmer and operator responses are:

Programmer Response: Correct your program and rerun the job.

Operator Response: None.

Error Code Dec	Error Code Hex	Reg 15=	Error Code Issued By	Explanation
1	X'01'	X'04'	CBMM	The control block manipulation request is invalid.
2	X'02'	Not zero	CLOSE	CLOSE or TCLOSE found an invalid control block structure for this ACB.
		X'04'	CBMM	The BLK = operand does not specify an ACB, RPL, or EXLST, or the operand has been omitted.
		X'08'	OPEN	OPEN found an invalid control block structure for this ACB.
3	X'03'	X'04'	CBMM	An invalid keyword has been specified.
4	X'04'	Not zero	CLOSE	The ACB was already closed.
		X'00'	Request Macros	VSAM detected an end-of-volume condition.
		X'04'	CBMM	The block or list at the indicated address is not of the type specified in the macro.
		X'08'	OPEN	This ACB is already open.
		X'08'	Request Macros	VSAM encountered end of file (during sequential retrieval), or the search argument is greater than the highest existing key (or relative record number) in the file.
		X'0C'	Request Macros	VSAM failed to read data as requested. The error may be caused by conditions such as VSAM finding an unformatted record when expecting a formatted one, a volume containing data other than that expected, or an I/O error. Ensure that, in the SYNAD exit routine, your program issues a DUMP macro. Save the dump you obtain and the SYSLOG output for later problem determination.
5	X'05'	X'04'	CBMM	For SHOWCB/TESTCB the macro attempts to access a closed ACB; the ACB must be open
6	X'06'	X'04'	CBMM	For SHOWCB/TESTCB the OBJECT operand refers to a nonexistent index.
7	X'07'	X'04'	MODCB	The referenced EXLST does not contain an entry for the exit you specified in MODCB/SHOWCB.
8	X'08'	X'00'	Request Macros	VSAM detected a non-unique key in the alternate index.
		X'04'	GENCB	Virtual storage available in the partition is insufficient to generate the requested block(s) or list(s). Programmer Response: Rerun the job in a larger virtual partition.
		X'04'	CBMM	Register 0 contains the error code. Register 15 may also contain X'08' indicating the execute form of the macro was used in an attempt to change a nonexistent entry in the referenced parameter list, or X'0C' indicating the request was not executed because an error had occurred while a VSAM phase was loaded. Register 0 then contains the return code from CDLOAD.
		X'08'	Request Macros	An attempt was made to store a record with a duplicate key, or a duplicate record was found for an alternate index with the UNIQUEKEY option, or a record already exists at the accessed record location.
		X'0C'	Request Macros	VSAM failed to read index-set records of an index. The error may be caused by conditions such as VSAM finding an unformatted record when expecting a formatted one, a volume containing data other than that expected, or an I/O error. Ensure that, in the SYNAD exit routine, your program issues a DUMP macro. Save the dump you obtain and the SYSLOG output for later problem determination.
9	X'09'	X'04'	GENCB	The work area provided in the program is too small to generate the requested block(s) or list(s). Programmer Response: Recompile the program with a larger work area specified.
		X'04'	SHOWCB	The work area provided in the program is too small to display the requested fields.
		X'04'	SHOWCB	In case LSRINF or EXTINF is specified the work area provided in the program is enough to display the header of the matrix. However the work area is too small to display all the matrix information. System Action: As much information as possible is displayed. Programmer Response: Check the header to see how much space is needed for VSAM to return all the matrix information. Issue another SHOWCB call with required area to get all the matrix information.
10	X'0A'	X'04'	CBMM	One of your EXLST operands specifies the L sub-parameter, but does not provide a new address, or the operand specifies neither an address nor one of the sub-parameters A and N.
11	X'0B'	X'04'	MODCB	The macro attempts to modify an active RPL; the RPL must be inactive.
12	X'0C'	X'00'	Request Macros	Issue a WRTBFR macro because there are no more unmodified buffers into which to read the contents of a control interval (shared resources only).
		X'04'	CBMM	Register 15 may also contain X'08' indicating the execute form of the macro was used in an attempt to change a nonexistent entry in the referenced parameter list, or X'0C' indicating the request was not executed because an error had occurred while a VSAM phase was loaded. Register 0 then contains the return code from CDLOAD.
		X'04'	MODCB	The macro attempts to modify an open ACB; the ACB must be closed. Register 15 may also contain X'08' indicating the execute form of the macro was used in an attempt to change a nonexistent entry in the referenced parameter list, or X'0C' indicating the request was not executed because an error had occurred while a VSAM phase was loaded. Register 0 then contains the return code from CDLOAD.
		X'08'	Request Macros	VSAM detected a record out of sequence in a key-sequenced or relative-record file (possibly a duplicate key or record number), or a user's request which is inconsistent with his previous request.
		X'0C'	Request Macros	VSAM failed to read sequence-set records of an index. The error may be caused by conditions such as VSAM finding an unformatted record when expecting a formatted one, a volume containing data other than that expected, or an I/O error. Ensure that, in the SYNAD exit routine, your program issues a DUMP macro. Save the dump you obtain and the SYSLOG output for later problem determination.
13	X'0D'	X'04'	MODCB	The address in the EXLST field to be activated is 0.
14	X'0E'	X'04'	CBMM	The specified parameters are inconsistent.
		X'08'	OPEN	The symbolic unit in the EXTENT statement is invalid.
15	X'0F'	X'08'	OPEN	Extent block processing failed. Programmer Response: Restructure your program so that fewer files are open concurrently. In a multiprogramming environment, rerun the job together with other jobs that require fewer extent blocks. If the problem persists, save the job stream and take a system dump before contacting your IBM® Support Center.
		X'04'	GENCB	The area specified in the WAREA operand does not begin on a full word boundary.
		X'04'	SHOWCB	The work area provided in your program does not begin on a full word boundary.
16	X'10'	X'00'	Request Macros	A control-area split occurred because there was not enough space to make an index entry in a sequence set record. Some data control intervals could not be used in the control area that was split.
		X'08'	Request Macros	No record found. If a relative-record file was being accessed, VSAM may have detected a deleted or invalid record at the accessed record location.
		X'0C'	Request Macros	VSAM failed to write data as requested. The error may be caused by conditions such as VSAM finding an unformatted record when expecting a formatted one, a volume containing data other than that expected, or an I/O error. Ensure that, in the SYNAD exit routine, your program issues a DUMP macro. Save the dump you obtain and the SYSLOG output for later problem determination.
		X'04'	CBMM	An invalid control block address was specified in the (ACB\|EXLST\|RPL) = address parameter.
17	X'11'	X'08'	OPEN	The address in an ASSGN statement for a VSAM volume was set to IGN. Programmer Response: Change the device address in the ASSGN statement to that of the VSAM volume being opened.
18	X'12'	X'08'	OPEN	The address in an ASSGN statement for a VSAM volume was set to UA. Programmer Response: Change the device address in the ASSGN statement to that of the VSAM volume being opened.
19	X'13'	X'08'	OPEN	Unable to assign a logical unit for the device on which the required volume is mounted. Either: A programmer logical unit is not available in this partition (available programmer logical units have been used by ASSGN statements, or VSAM automatic assignments for files, catalogs or catalog recovery areas (CRA). For recoverable catalogs, VSAM always assigns a programmer logical unit for each CRA), or An extent block is not available in the system (temporary assignments use these), or The device on which the volume is mounted is reserved (Attention Routine VOLUME command), or The device on which the volume is mounted is 'down' (Job Control command DVCDN). Programmer Response: The automatic assign function failed because the device with the required volume is in 'down' status, reserve status, or because no programmer logical units were available. Use the Job Control command LISTIO NPGR to check the number of logical units available in the partition. If there are not enough logical units available, increase their number using the Job Control command NPGR. The total number of logical units for all partitions must not, however, exceed the number specified in the NPGR parameter at supervisor generation. Rerun the job. If this is a multistep job, separate it into several jobs. Instruct the operator to ensure that the device on which the volume mounting is done is in 'up' status and unreserved before replying 'NEWPAC'.
20	X'14'	X'04'	SHOWCB	STRMAX or TRANSID were specified, but LSR was not specified in the ACB.
		X'08'	Request Macros	The requested record is contained in a control interval that is already held in exclusive control by another request.
		X'0C'	Request Macros	VSAM failed to write index-set records of an index. The error may be caused by conditions such as VSAM finding an unformatted record when expecting a formatted one, a volume containing data other than that expected, or an I/O error. Ensure that, in the SYNAD exit routine, your program issues a DUMP macro. Save the dump you obtain and the SYSLOG output for later problem determination.
21	X'15'	X'04'	SHOWCB	In case LSRINF or EXTINF is specified the work area provided in the program is too small to display the header of the matrix (less than the minimum required 32 bytes). System Action: No information is displayed. Programmer Response: Recompile the program with a larger work area specified.
24	X'18'	X'08'	Request Macros	The requested record is on a volume or extent that cannot be accessed because no extent blocks are available. Programmer Response: Try to find the reason for the non-availability of the volume or extent. If circumstances indicate that no more extent blocks are available, rerun the job together with other jobs that require a smaller number of extent blocks. If you cannot correct the error situation, contact your IBM Support Center.
		X'0C'	Request Macros	VSAM failed to write sequence-set records of an index. The error may be caused by conditions such as VSAM finding an unformatted record when expecting a formatted one, a volume containing data other than that expected, or an I/O error. Ensure that, in the SYNAD exit routine, your program issues a DUMP macro. Save the dump you obtain and the SYSLOG output for later problem determination.
28	X'1C'	X'00'	Request Macros	The record retrieved by a GET-with-no-update may be a duplicate of a record in another CI. Eliminate duplicate records by processing the data using keyed access with update. For sequential processing, this error code is set on for only the first record of the CI.
		X'08'	Request Macros	All extents of the file are full, and VSAM cannot sub-allocate any additional extents to the file for one of the following reasons: No secondary allocation was specified and no space of the required class was found to be available for primary space sub-allocation on an additional volume (if one was specified). The maximum number of extensions for the file has been exceeded. No space of the required class is available for additional secondary allocations. During an extent of an unique file residing in a recoverable catalog, there was no space defined to build the CRA on the candidate volume.
32	X'20'	X'00'	Request Macros	For a SAM ESDS with variable length records, a POINT or direct GET was issued that specified an RBA of zero. Positioning has been done to the first record of the file, which is actually at RBA 8.
		X'08'	OPEN	The OPEN disposition specified for the file conflicts with other file characteristics. DISP=NEW was specified for an input file DISP=NEW was specified for a file using local shared resources.
		X'08'	Request Macros	An invalid RBA has been specified.
34	X'22'	X'08'	OPEN	The volume serial number(s) specified in the EXTENT statement(s) do not match those recorded in the catalog entry. An EXTENT statement is required for each volume to be accessed; for example, for each volume on which your base cluster and alternate index(es) reside.
36	X'24'	X'08'	Request Macros	The key of the record to be inserted does not fall in an existing key range in the file.
40	X'28'	X'08'	OPEN	No space is available on any volume for primary allocation of a dynamic file. Programmer Response: Use LISTCAT to determine the volumes allocated to the file's primary allocation value, the file USECLASS specification, and the space allocation status of these volumes. Either: Delete obsolete files occupying data space with matching classes (CLASS, USECLASS/USECLASS parameters), or Define additional data space(s) of the required class on any of the volumes, or Using the ALTER command ADDVOLUMES parameter, add volume(s) to the file that contains sufficient unallocated space of the required class to satisfy the file's primary allocation value. Then rerun your job.
		X'08'	Request Macros	VSAM could not obtain a sufficiently large contiguous area of virtual storage. Programmer Response: Rerun the job in a larger partition.
41	X'29'	X'04'	OPEN	A BACKUP for a VSAM object is to be performed, but the VSAM object is currently being updated by another task. The opening process for this object will continue, thus possibly resulting in an inconsistent object entry in the backup file. Programmer Response: Once BACKUP has ended, message IDC11310I, which heads the two BACKU reference lists BECR and BOCR, shows the name of the object which was backed up and warns you of a possible inconsistency in the BACKUP file. Rerun BACKUP for this object.
44	X'2C'	X'08'	Request Macros	The work area you have supplied (in the AREA = addr operand for the RPL) is not large enough for the requested data record.
46	X'2E'	X'08'	Request Macros	Not enough buffers are available to process the request (non-shared resources only). See return code x'98' for a similar error with shared (LSR) Buffers. Programmer Response: Modify your VSAM definitions to allow more buffers for your application. If the problem persists, contact IBM support.
48	X'30'	X'08'	OPEN	An attempt was made to open a NOALLOCATION file which is not reusable (REUSE). Such a file is really a model and cannot be opened. Programmer Response: Make sure the file ID in your DLBL statement does not specify the name of a default model.
		X'08'	Request Macros	One or more VSAM processing phases cannot be loaded because the virtual partition being used is too small. Programmer Response: Rerun the job in a larger virtual partition.
50	X'32'	X'08'	OPEN	One or more VSAM processing modules cannot be loaded because the user's virtual partition is too small. Programmer Response: Have your program executed in a larger virtual partition.
52	X'34'	X'08'	Request Macros	VSAM has detected an internal logic error. Programmer Response: This error should have resulted in an SDUMP being issued. If not, re-run the failing job with "// OPTION DUMP" specified. Then print the SDUMP, and save the dump, console log and any SYSLST output, and contact IBM support.
56	X'38'	X'08'	Request Macros	An error occurred during dynamic assignment of a volume. A programmer logical unit is not available in this partition (assignment statements for SYS`xxx` use these), or An extent block is not available in the system (temporary assignments use these). The device on which the volume is mounted is 'down' (job control command DVCDN).
58	X'3A'	X'08'	Request Macros	An attempt has been made to add records to a file resulting in the total size of the file exceeding X'FFFFFFFF' (4.3 billion bytes). The request has been rejected. Programmer Response: Reorganize the file to reduce the size below the X'FFFFFFFF' limit.
63	X'3F'	X'08'	Request Macros	Error during upgrade-reset processing which was likely caused by insufficient LSR buffers condition. Potential corruption of the alternate index may occur (pointer without associated base record). Programmer Response: Verify the consistency of all the alternate indexes in the upgrade-set and rebuild it if required. Consider enlarging the LSR pool assigned to the affected clusters.
64	X'40'	X'08'	OPEN	An attempt was made to open a NOCIFORMAT file using an ACB. VSAM does not support files that are not in CI format. Programmer Response: Change your program to use managed SAM to access the file, or change the DLBL statement to specify a file other than SAM ESDS. Rerun the job.
		X'08'	Request Macros	As many requests are active as the number specified in the STRNO = n operand for the ACB, or BLDVRP macro; therefore, another request cannot be started.
65	X'41'	X'08'	OPEN	An attempt was made to open a SAM ESDS but the VSAM Space Management for SAM Feature is not installed on the system. Programmer Response: Install the VSAM Space Management for SAM Feature in your system and rerun the job. If you do not want to install the VSAM Space Management for SAM Feature, change the DLBL statement to specify a file other than SAM ESDS and rerun the job
66	X'42'	X'08'	OPEN	An attempt was made to open a DTF with file characteristics that are incompatible with the field's characteristics in the VSAM catalog. Examples of these incompatibilities are: The DTF BLKSIZE is too large to fit in the maximum RECORDSIZE defined for the file. The DTF implies a CI format file but the file is NOCIFORMAT. Only DTFPH may be used with NOCIFORMAT files. For managed-SAM access of a SAM ESDS, this message may be considered for informational purposes only. Note: For DTFPH, BLKSIZE is taken to be the DTFPH CISIZE minus 7. Programmer Response: If the file was explicitly defined, you must change your program to be compatible with the files, change the file by explicitly deleting it and redefining it to agree with your program, or use a different file. If the file was implicitly defined, you can cause open to implicitly delete it and implicitly redefine it to agree with your program by specifying DISP=NEW. During implicit deletion, the operator will be requested to authorize deletion if the expiration date previously specified for the file has not passed.
67	X'43'	X'08'	OPEN	An attempt was made to open an unexpired file for output using a DTF. For managed-SAM access of a DAM ESDS, this message may be considered for informational purposes only. Programmer Response: This VSAM OPEN return code will be handled internally by the VSAM Space Management for SAM Feature by requesting operator authorization to delete the unexpired file. This message is accompanied by message 4233A. If authorization is granted, OPEN will complete successfully assuming no other complications.
68	X'44'	X'08'	OPEN	The file to be opened has a name which begins with 'DEFAULT.MODEL. ...' This is an invalid prefix.
		X'08'	Request Macros	The type of accessing for the request does not match the type of accessing in the ACB when the file was opened; for example: ADR or CNV was specified, but keyed access is requested. IN was specified (explicitly or by default), but an update request is made. GET UPD ADR is requested but ADR was not specified on the ACB when the SHAREOPTIONS (4) KSDS was opened.
69	X'45'	X'08'	OPEN	An attempt was made to open a file which is not a SAM ESDS using a DTF. Programmer Response: Probable job control error. Make sure that your DLBL statement specifies a file ID which you know is a SAM ESDS.
70	X'46'	X'08'	OPEN	An invalid file ID was detected during implicit define or implicit delete. For managed-SAM access of a SAM ESDS, this message may be considered for informational purposes only. Programmer Response: Probable job control error. Make sure that the file ID specified in your DLBL statement meets the criteria for a valid VSAM file ID.
71	X'47'	X'08'	OPEN	Allocation specification for implicit define conflict with the file characteristics specified in the DTF and VSAM is not able to resolve the conflict. For managed-SAM access of a SAM ESDS, this message may be considered for informational purposes only. Programmer Response: Probable job control error. Make the average record size specified in the DLBL statement not larger than the block size specified in your DTF.
72	X'48'	X'08'	OPEN	The file ID specified in your DLBL statement was not found in the catalog and insufficient allocation information was specified for an implicit define. For managed-SAM access of a SAM ESDS, this message may be considered for informational purposes only. Programmer Response: Add space allocation parameters to your job control statements. This may be done by specifying the number of tracks and blocks in the EXTENT statement or by specifying RECORDS and RECSIZE on the DLBL statement for device independent allocation.
73	X'49'	X'08'	OPEN	The value of any parameter RECORDS/CYL/BLK in DLBL statement for SAM ESDS is more than 16,777,215. Programmer Response: Check and correct parameters in DLBL statement
		X'08'	Request Macros	Keyed access is requested for an entry-sequenced file.
74	X'4A'	X'08'	OPEN CLOSE	VSAM ACBs can be located in 31-bit storage. However, due to end-of-list delimiter issues, if a 31-bit ACB is passed to OPEN or CLOSE, it must be the only element in the list. This error code indicates that another ACB or DTF was detected in an Open or Close list containing a 31-bit ACB.
76	X'4C'	Not zero	CLOSE	Disposition processing failed during CLOSE. System Action: CLOSE processing continues to successful completion assuming no other complications. Message 4226I or 4227I will be issued at end-of-job step for this file. Programmer Response: Be aware that a file which you expected to be deleted may still exist, or a file which you expected to be unallocated may still be using space, or a file which you expected to be reset may still have secondary allocation, or check if a file is defined reusable. Use Access Method Services commands (for example: LISTCAT, DELETE) to clean up files as required.
		X'08'	Request Macros	Addressed or control-interval insertion is requested for a key-sequenced or relative-record file.
78	X'4E'	X'08'	OPEN	A catalog management error was detected during implicit delete. Message 4A37I is issued to provide the catalog management return code and reason code which are used to diagnose the problem. For managed-SAM access of a SAM ESDS, this message may be considered for informational purposes only.
		X'08'	Request Macros	Addressed or control-interval access is requested for an Extralarge key-sequenced dataset.
79	X'4F'	X'08'	OPEN	A catalog management error was detected during implicit define. Message 4A37I is issued to provide the catalog management return code and error code which are to be used to diagnose the problem. For managed-SAM access of a SAM ESDS, this message may be considered for informational purposes only.
80	X'50'	X'08'	OPEN	An attempt was made to have two volumes mounted on the same device when direct or keyed processing is specified in the ACB, or the operator did not mount the required volume. Programmer Response: Request a valid programmer logical unit. Reassign the programmer logical unit (ASSGN SYS`xxx`) or request a device that is already assigned. Ensure that the operator mounts the correct volume.
		X'08'	Request Macros	An ERASE macro is issued for an entry-sequenced file (directly or via a path) or for a file for which control-interval processing has been specified.
84	X'54'	X'08'	Request Macros	Locate mode was specified for a PUT request or for processing in a user buffer.
88	X'58'	X'08'	Request Macros	Positioning error; the problem program: Issued a sequential GET without having VSAM positioned for this GET. If MACRF=LSR is used, VSAM does not position itself automatically after OPEN. Changed from addressed to keyed access without having VSAM positioned for keyed-sequential retrieval. Issued a sequential PUT insert request for a relative-record file without having VSAM positioned for this request. Attempted to improperly switch between forward and backward processing.
92	X'5C'	X'04'	OPEN	Warning: MACRF=LSR (shared resources) is specified, but no OPEN/CLOSE/TCLOSE message area was specified. Ignore this error code if there is no ACB with the option DFR specified in the resource pool.
		X'08'	Request Macros	A PUT for update or an ERASE is issued without a preceding GET for update.
96	X'60'	X'04'	OPEN	The file to be opened for input was found to be unusable because catalog recovery for this file failed. Programmer Response: Either correct the situation that caused the catalog recovery operation for this file to fail, or recreate the file.
		X'08'	Request Macros	Attempt was made to change the prime key of a record that is being updated, or an attempt was made to change an alternate key that has the UNIQUEKEY attribute. A sequence error occurred during sequential updating. For example, during REPRO REPLACE, two separate updates to the same record were attempted.
100	X'64'	X'04'	OPEN	OPEN encountered an empty alternate index that is part of an upgrade set.
		X'08'	Request Macros	Attempt was made to change record length during update with addressed access or to change record length for a relative-record file.
104	X'68'	X'04'	OPEN	The time stamp of the volume on which the file is stored is lower than the system time stamp in the file's catalog entry. The extent information in the catalog entry may not agree with the extent information in the volume's VTOC. Programmer Response: If problems occur due to inconsistent extent information, display the VTOC and execute the Access Method Services LISTCAT command and compare the extent information. Possibly the wrong volume was mounted. If the correct volume was mounted, recover the file to make sure that the volume and catalog time stamps agree. Rerun the job. A possible reason may also be an invalid IPL date. In this case, the time stamp must be recovered.
		X'08'	Request Macros	Invalid or conflicting RPL option or parameters: SKP together with BWD. LRD without BWD. CNV together with BWD. ARG parameter was not specified when required. UPD together with NSP. NSP is specified for an ERASE request. For local shared resources, the ACB address is not the same as for a previous request that used the same RPL. Mismatch between RPL Length and RPL Subtype field. For shared resources, WRTBFR was issued, but: TRANSID was greater than 31, or The shared resource option (LSR) was not specified, or The LRU percentage value was not between 0 and 100.
105	X'69'	X'08'	Request Macros	ACB corrupted or not properly opened.
106	X'6A'	X'08'	Request Macros	Invalid use of the extended user buffer (XBF) optioncode: the file being processed is not an ESDS, or a request other than GET or PUT was issued
108	X'6C'	X'04'	OPEN	The system time stamps of the data of a file and its index do not match; this indicates that either the data or the index has been updated separately and that data integrity problems may result if the file is processed now. Programmer Response: If data integrity problems arise, revert to a valid backup copy of the file.
		X'08'	Request Macros	The RECLEN value specified for the RPL was one of the following: Larger than the allowed maximum. Equal to zero. Smaller than key length plus relative key position. Not equal to record (slot) size specified for a relative-record file. For alternate index upgrade processing, the alternate index contains too many duplicate keys. Increase the maximum record length to accommodate more keys.
110	X'6E'	X'08'	OPEN	VSAM attempted to open an empty file (no records in it) only for input (MACRF = IN was specified for the ACB) or a file that was not properly closed on initial loading. Programmer Response: Change your program to specify MACRF=OUT in the ACB if you want to process empty files. For managed-SAM access of a SAM ESDS, this message may be considered for informational purposes only.
112	X'70'	X'08'	Request Macros	Length of the generic key specified for the RPL is too large, or the specified value is equal to zero.
113	X'71'	X'00'	OPEN	OPEN tried to execute the Catalog Check Service Aid in order to check the validity of this file's catalog records. Either the CDLOAD failed, or the service aid encountered I/O errors. The file has been opened successfully. Programmer Response: Run the Catalog Check Service Aid; it will identify catalog errors for you. Follow the directions for the error messages that it issues.
114	X'72'	X'00'	OPEN	The catalog Check Service Aid was invoked during OPEN processing and detected a catalog irregularity, or there was insufficient storage for Catalog Check processing. Programmer Response: This access to the data is allowed, but there are errors in the catalog structure that you should find. Because this information was collected during OPEN processing, it cannot be printed. Run the Catalog Check Service Aid against the entire catalog; it will identify catalog errors for you. Follow the directions for the error messages that it issues. If Catalog Check finds no errors, the problem was due to insufficient storage. Rerun the original job.
115	X'73'	X'00'	OPEN	The catalog Check Service Aid was invoked during OPEN processing and detected an error. Programmer Response: Because this information was collected during OPEN processing, it cannot be printed. Run the Catalog Check Service Aid against the entire catalog; it will identify catalog errors for you. Follow the directions for the error messages it issues. If Catalog Check finds no errors, the problem was due to insufficient storage. Rerun the original job.
116	X'74'	X'04'	OPEN	The file to be opened was not successfully closed the last time it was processed. One of the following has happened: OPEN tried to verify the catalog records for the file but did not complete verification. The file is a SAM ESDS in non-CI format, so OPEN did not try to verify its catalog records. The file is an ESDS being opened in CNV mode. There are two ways this could happen: Your job stream contains a VERIFY command. (VERIFY opens files in CNV mode.) The verification is successful; ignore this error code. You requested CNV mode on the RPL. Open did not try to verify the file's catalog records. The previous time the file was opened was the initial load of the file, and SPEED was specified. OPEN did not try to verify its catalog records. Programmer Response: Depends on the processing done during the preceding run. If records were only retrieved, no programmer action is required. If records were added, deleted, or updated, and CNV mode was requested in the ACB, an ESDS has been opened in CNV mode so the automatic verify during open will not be started. Run an AMS VERIFY.
		X'08'	Request Macros	A request other than sequential or skip sequential PUT to insert records was issued during initial loading of the file, or a request other than PUT insert was issued during initial loading of a relative-record file. Possibly an attempt was made to read an empty file.
117	X'75'	X'08'	OPEN	The logical unit specified in the EXTENT statement is not assigned to a valid device type, or invalid extents are specified.
118	X'76'	X'00'	OPEN	You opened a file that was not closed on a previous OPEN for output. OPEN verified the file's catalog records, but if this OPEN was for input now, the catalog RBA values have not been validated and this error code keeps coming until you give an OPEN for output or run an explicit VERIFY. Programmer Response: No action required. This information message indicates that the catalog statistics may be incorrect. These statistics cannot cause any processing errors, but be aware that LISTCAT output may contain erroneous information.
128	X'80'	X'08'	OPEN	The DLBL statement for the file or catalog is missing, or the file name specified in that statement does not match the name of the ACB. If the error occurs during VSAM Re-director action, the target file system is unreachable.
		X'08'	Request Macros	The VSAM catalog was accessed during processing of a request, and an error occurred during this catalog access. The reason can be one of the following: GETVIS failure. An attempt has been made to process a file which would result in the total size of the file exceeding X'FFFFFFFF' (4.3 billion bytes). The request has been rejected. Programmer Response: GETVIS failure: If a recoverable catalog was used, check whether all of the required EXTENT statements were provided; if a recoverable catalog was not used, provide a larger virtual partition. Enable SNAP1. For details see VSE/VSAM User's Guide and Application Programming. Rerun the job. If the rerun fails, contact your IBM Support Center. You may wish to use the following for problem determination. Program listing SYSLOG output Program dump, if available. If the file size exceeded X'FFFFFFFF' (4.3 billion bytes): Use option EXTRALARGEDATASET during DEFINE of a CLUSTER to go over this limitation with a KSDS. For ESDS the limitation of 4.3 billion bytes can not be circumvented. Reorganize the file to reduce the size.
132	X'84'	X'08'	OPEN	A permanent I/O error occurred while VSAM was reading label information from the label information area. Programmer Response: Retry. If the problem persists, instruct your operator to issue the ROD command and to run EREP; contact your IBM Support Center, and have EREP and SYSLOG output available for problem determination.
		X'08'	Request Macros	An attempt was made to retrieve a spanned record in locate mode.
136	X'88'	Not zero	CLOSE	VSAM could not obtain a contiguous area of virtual storage large enough for the work area needed by the CLOSE routine. Programmer Response: Have your program executed in a larger virtual partition.
		X'08'	OPEN	VSAM could not obtain a contiguous area of virtual storage large enough to accommodate work areas, control blocks, and buffers needed by VSAM. Programmer Response: Provide a larger GETVIS area for VSAM by one of the following actions: Specify the SIZE parameter in the EXEC statement (if missing), or Allocate more virtual storage to the partition.
		X'08'	Request Macros	An attempt was made to retrieve a spanned record of a key-sequenced file with addressed access.
140	X'8C'	X'08'	Request Macros	VSAM encountered an inconsistent spanned record (that is, one or more segments were incompletely updated or destroyed).
144	X'90'	Not zero	CLOSE	One of the following has occurred: VSAM could not obtain a sufficiently large area of contiguous storage needed by the catalog routines for CLOSE processing. An error occurred when the catalog was accessed during processing of a CLOSE request. For example, a permanent I/O error may have occurred when VSAM was reading or writing a catalog entry or catalog recovery area record. A GETVIS failure, or a failure to load a VSAM phase occurred. Programmer Response: Retry. If the problem persists, instruct your operator to issue the ROD command and to run EREP; contact your IBM Support Center.
		X'08'	OPEN	An error occurred when the catalog was accessed during the processing of an OPEN request. For example, a permanent I/O error may have occurred when VSAM was reading or writing a catalog entry or a catalog recovery area record. Programmer Response: Retry. If the problem persists instruct your operator to issue the ROD command and to run EREP; contact your IBM Support Center and have EREP and SYSLOG output available for problem determination.
		X'08'	Request Macros	VSAM encountered a pointer in an alternate index without an associated base record. There are two classes of error which may result in this return code: Temporary After CLOSE or ENDREQ, the base record is present. This condition is due to read integrity restrictions. See VSE/VSAM Commands the SHAREOPTIONS parameter under DEFINE CLUSTER. Permanent The base record is missing even after CLOSE or ENDREQ. When a record is inserted into a base cluster, for which an alternate index has been built and flagged as UPGRADE, the alternate index(es) are updated first, and then the base cluster. If an error occurs while updating the base cluster, VSAM attempts to backout the change to the alternate index(es). If this fails, leaving an inconsistent alternate index pointer, VSAM sets an appropriate error code in bytes 1 and 3 of RPLFDBK, and sets byte 2 of RPLFDBK to X'01', indicating an incorrect upgrade set. VSAM then returns control to the calling program. It is up to the user to rebuild the alternate index. Simply retrying the request will not rectify the problem. When a non-zero return is detected from upgrade reset processing, VSAM will issue an IDUMP. This will assist the user in identifying the reason why the alternate index reset failed.
148	X'94'	X'08'	OPEN	No valid entry was found in the catalog for the ACB to be opened or for the alternate index structure related to this ACB. Your program may have: specified an incorrect cluster, alternate index, or path name, or failed to specify the correct catalog name, or an Access Method Services DEFINE or DELETE may have failed. Programmer Response: Verify that your program is using the correct cluster, alternate index, or path name. Verify that your program is using the correct catalog. Verify that the cluster, alternate index, or path was defined with the correct name and in the desired catalog. Verify that a previous Access Method Services DEFINE or DELETE did not fail. Perform a LISTCAT to determine the contents of the catalog you are using.
		X'08'	Request Macros	The maximum number of pointers in the alternate index has been exceeded.
152	X'98'	X'08'	Request Macros	Not enough buffers are available to process the request (LSR = shared resources only). See return code x'2E' for a similar error with non-shared buffers. Programmer Response: Modify your VSAM definitions to allow more buffers for your application. If the problem persists, contact IBM support.
		X'08'	Request Macros	Not enough buffers are available to process the request (shared resources only). Programmer Response: Retry the request; additional buffers may have been freed.
153	X'99'	X'08'	Request Macros	A call to Record Management was made with a corrupted RPL or ACB. An SDUMP is issued, and the request is returned with return code X'08'.
156	X'9C'	X'08'	Request Macros	One or more records in this CI may contain duplicate data after an addressed GET-with-update. Any duplicates can be eliminated by processing the data set using keyed access.
160	X'A0'	X'08'	OPEN	One of the following has occurred: Keyed access was specified for the ACB (in the ACB or the GENCB macro), but the file is entry sequenced. An attempt was made to load a key-sequenced file with an access type other than keyed. An attempt was made to access a relative-record file with an access type other than keyed or control interval. MACRF = LSR (shared resources) has been specified together with UBF (user buffering). MACRF = DFR (defer writes) has been specified without LSR (shared resources). MACRF = DFR has been specified for a file that was defined with SHAREOPTIONS (4). Both KEY and ADR/CNV access were specified in an ACB being opened for a share option 4 output file. An attempt was made to access a file for input with conflicting or invalid disposition specified on the job control statements.
161	X'A1'	X'08'	OPEN	User buffers (ACB MACRF=UBF) has been specified with one of the following: Keyed or addressed access, in which case user buffers can be specified only with control interval access, or Data set name sharing (ACB MACRF=DSN), in which case user buffers can be specified only with ACB MACRF=DDN. Programmer Response: Specify ACB MACRF=NUB (no user buffers), ACB MACRF=CNV (control interval access), or ACB MACRF=DDN. Rerun the job.
162	X'A2'	X'04'	OPEN	An OPEN with data set name sharing (ACB MACRF=DSN) was successful, but the ACB was connected to an already existing DSN structure with opposite input or output mode. If the current OPEN was done with ACB MACRF=OUT, no output access will be possible. If the current OPEN was done with ACB MACRF=IN, no output access will be possible, even if the existing DSN structure is an output structure. Programmer Response: None.
163	X'A3'	X'08'	OPEN	A path OPEN with data set name sharing failed because there were not enough strings available for the path-related base cluster. The ACB BSTRNO value, defined during a previous OPEN of a single cluster under data set name sharing, is too small for this OPEN attempt. Programmer Response: Either increase the ACB BSTRNO value for the previously OPENed cluster, or decrease the ACB STRNO value for this path OPEN.
165	X'A5'	Not zero	CLOSE	A permanent I/O error was detected on the system lock file. Programmer Response: Consult your system programmer to correct the problem. Rerun the job after the system problem is corrected.
		X'08'	OPEN	A permanent I/O error was detected on the system lock file. Programmer Response: Consult your system programmer to correct the problem. Rerun the job after the system problem is corrected.
166	X'A6'	Not zero	CLOSE	The system lock table is not large enough to accommodate the concurrent requests. Programmer Response: Rerun your job when there is less concurrent activity in the system.
		X'08'	OPEN	The system lock table is not large enough to accommodate the concurrent requests. Programmer Response: Rerun the job when there is less concurrent activity in the system.
167	X'A7'	Not zero	CLOSE	The system lock file is not large enough to accommodate the concurrent requests. Programmer Response: Rerun the job when there is less concurrent activity in the system.
		X'08'	OPEN	The system lock file is not large enough to accommodate the concurrent requests. Programmer Response: Rerun the job when there is less concurrent activity in the system.
168	X'A8'	Not zero	CLOSE	The return code from the lock manager indicated that the requested resource is either not available or already owned by the same task. Programmer Response: Same as for OPEN, below.
		X'08'	OPEN	The file is not available for one of the following reasons: It is being updated by and under exclusive control of another ACB; for example, the SHAREOPTION specification of the file does not allow an additional open of the type requested. Another ACB has opened the file in initial load mode. Initial load mode will be used if MACRF=RST or DLBL..DISP=NEW.. is specified, or if you open an empty dataset for output. It is being reset by another ACB. OPEN with RESET was specified in the ACB and the file is being accessed by another ACB. It was exported with the TEMPORARY and INHIBITSOURCE options and updating is not permitted. A copy of the file was exported with the INHIBITTARGET options and imported into this system. Updating is not permitted. It was altered via the ALTER command with the INHIBIT options. A SAM ESDS is being loaded or extended by another SAM access user (DTF). A managed-SAM access user (DTF) has attempted to load or extend a SAM ESDS that is in use by another managed-SAM access user (DTF). The ACB for a SHAREOPTIONS(4) KSDS indicates MACRF = ADR, MACRF = CNV, or MACRF = KEY but there are currently other ACBs open for addressed output or control interval output access. You attempted to open an ACB for a SHR(4) KSDS using MACRF = (KEY,CNV) or MACRF=(ADR). You attempted to open a file for output with MACRF=ADR or MACRF=CNV but a SHAREOPTION(4) file is already opened for output with MACRF=KEY. You attempted to open a file for output with MACRF=KEY but a SHAREOPTION(4) file is already opened for output with MACRF=ADR or MACRF=CNV. You attempted to open a file for output with SHAREOPTION(4) but the file is already opened for output from another processor. Only one processor may open a file unless the file was defined with SHAREOPTION(4). If the system which opened the file has become inoperative, the lock can be released via Attention Routine UNLOCK command. Programmer Response: Determine if the file contention problem is caused within your program. If so, change your program to avoid the contention, or change the file definitions to allow your desired operations. Rerun your job. If you determine the contention is caused by other jobs (either in your system or another system) using the same files as your job, attempt to reschedule your job at a time when contending jobs will not be running.
169	X'A9'	X'08'	OPEN	MACRF=DSN was specified in the ACB, and the SHRPOOL value of the ACB to be opened is not the same as the SHRPOOL value of the first ACB which opened the file and built the Data Set Name (DSN) sharing structure. OPEN failed in order to avoid getting incorrect information from subsequent SHOWCB/TESTCB requests. Programmer Response: If you want DSN, then change the SHRPOOL value so that the failing ACB has the same value as the first ACB which opened the file and built the Data Set Name sharing structure. To open the ACB without DSN, remove 'DSN' from the MACRF statement in the ACB.
180	X'B4'	X'08'	OPEN	An error occurred in opening a catalog or CRA. Possible causes are: The catalog may not exist or the wrong catalog is searched. An attempt to get virtual storage failed. An I/O error occurred while VSAM was reading the VTOC. An extent block is not available in the system. Unable to assign a logical unit. The system lock table or system lock file is full or an I/O error was detected on the system lock file. More than one volume with the same volume identifier (volume serial number) is mounted on the system. Programmer Response: Specify SIZE on the EXEC statement to provide adequate GETVIS space. Ensure that the correct volume was mounted; check your job control statements defining the catalog or CRA for possible errors. Correct any errors and rerun the job. If the error occurred although the correct volume was mounted and there was no job control error, restore the catalog by using a backup copy or the catalog recovery function.
184	X'B8'	Not zero	CLOSE	An internal error occurred in a VSAM routine while VSAM was completing I/O requests. Programmer Response: Ensure that your program issues a DUMP macro when this type of error occurs. Save the dump you obtain for later problem determination.
188	X'BC'	Not zero	CLOSE	The ACB to be closed is being used; (for example, by a SHOWCB or TESTCB macro).
		X'08'	OPEN	The ACB to be opened is already being used.
		X'08'	Request Macros	The ACB is already active by another operation that uses exclusive control (like OPEN, CLOSE, or Control Block Manipulation).
192	X'C0'	X'08'	OPEN	Either the file to be opened for output or to be backed up was found to be unusable (catalog entry marked not usable) because (a) catalog recovery for this file failed, or (b) DELETE SPACE with FORCE has deleted a volume required by the file or an attempt was made to open a dataset for output and the corresponding catalog resides on an R/O disk, or (c) an unauthorized program has attempted an output OPEN of a VSAM compression control data set. Programmer Response: One of the following: Correct the problem that caused the preceding catalog recovery operation to fail. Use Access Method Services EXPORTRA command to export the file for subsequent re-importation. Redefine and reload the file. Specify ACB MACRF=IN if you want to read data from a R/O disk. Exclude the file from the backup. You must not manipulate a VSE/VSAM compression control data set.
		X'08'	Request Macros	VSAM encountered an invalid relative-record number.
194	X'C2'	X'08'	OPEN	It was attempted to open the data component of a compressed cluster for output, or to open the index component of a compressed cluster. VSE/VSAM does not provide these functions. Programmer Response: Use the compressed cluster via its cluster component name.
195	X'C3'	X'08'	OPEN	ACB MACRF=(CNV,NCM) was specified and the cluster was compressed. In control interval mode VSE/VSAM cannot provide access to records in non-compressed format. Programmer Response: Either of the following solutions might be applicable: Do not use control interval mode Specify MACRF=CMP (only if access to uncompressed records is not necessary) Do not define the cluster with the COMPRESSED attribute
196	X'C4'	X'08'	OPEN	Access to data was requested via an empty alternate index.
		X'08'	Request Macros	An addressed request is issued for a relative-record file. Programmer Response: Use Access Method Services BLDINDEX command to initialize the alternate index. Rerun the job.
200	X'C8'	X'08'	Request Macros	An addressed or control-interval access is attempted via a path.
204	X'CC'	X'08'	Request Macros	The program issued a PUT to insert a record while in backward mode.
208	X'D0'	X'08'	Request Macros	For SHAREOPTIONS (4), a lock required for update or insert processing is held in exclusive control by another ACB. The other ACB is not in communication with the ACB under which the current request has been processed; however, processing for the other ACB is being executed under the same VSE task. Programmer Response: One of the following techniques can be used to alleviate the problem: Allow the processing of the request under the other ACB to be completed and then retry the failed request. Merge the processing that was two ACBs so that only one ACB is required. (However, this can result in error code X'14' when the same situation occurs.) Run both ACBs under Local Shared Resources so that they will be in communication with each other. (However, this can result in error code X'14' when the same situation occurs.) Run each ACB under a separate VSE task.
210	X'D2'	X'08'	Request Macros	VSAM received a return code from the LOCK macro indicating that the request would have resulted in a deadlock condition within the system (deadlocks across the systems are not affected). Programmer Response: Allow the processing of the request under the other ACB to be completed and then retry the failed request.
212	X'D4'	X'08'	OPEN	MACRF = LSR (shared resources) is specified, but the file being opened is empty (which implies that the file will be loaded).
		X'08'	Request Macros	VSAM received a return code from the LOCK macro indicating that there is no space in the lock table to make a lock entry. Programmer Response: Use another program to load the file or specify ACB MACRF = NSR (no-shared resources) until the file is loaded.
216	X'D8'	X'08'	OPEN	MACRF = LSR (shared resources) is specified, but the key length of the file being opened is greater than the maximum key length specified in BLDVRP for the resource pool.
220	X'DC'	X'08'	OPEN	MACRF = LSR (shared resources) is specified, but the control interval size of the file being opened is greater than the largest buffer size specified in BLDVRP for the resource pool.
224	X'E0'	X'08'	Request Macros	The update of a record in a compressed cluster using addressed mode (OPTCD=ADR) is not allowed.
228	X'E4'	Not zero	CLOSE	The VSAM shared resource table (IKQVSRT) ID is invalid. Programmer Response: Take a system dump, contact your IBM Support Center and have the dump output, SYSLOG output, and a copy of the job stream available for problem determination.
		X'08'	OPEN	ACB MACRF = LSR (local shared resources) is specified, but there is no resource pool defined or the pool value is incorrect. There may have been problems in loading the resource table. Programmer Response: Change your program to build the resource pool before attempting to open any ACB that uses local shared resources. Rerun your job.
229	X'E5'	X'08'	Request Macros	The expansion of a compressed record resulted in a different length than recorded by VSE/VSAM when the record was compressed. Programmer Response: The data may be corrupted. Rerun the failing job and contact your IBM support center if the error persists.
232	X'E8'	X'08'	OPEN	ACB MACRF = RST (reset) was specified for a non-reusable file and that file is not empty. Reset specification can result from MACRF = RST in your ACB, open disposition of NEW, or close disposition of DELETE in your DLBL statement. Programmer Response: Change the reset specification and rerun your job.
		X'08'	Request Macros	A compression control services error was encountered. The problem is further qualified by message 4A91I written to SYSLOG. Programmer Response: Change the reset specification and rerun your job.
245	X'F5'	X'08'	Request Macros	A compression management services error was encountered during compression. The problem is further qualified by message 4A90I written to SYSLOG.
246	X'F6'	X'08'	Request Macros	During OPEN or CLOSE a compression management service error was encountered. The 4228I message includes the compression management services return and reason codes, which are explained under message 4A90I.
246	X'F6'	X'08'	Request Macros	A compression management services error was encountered during expansion. The problem is further qualified by message 4A90I written to SYSLOG.
247	X'F7'	X'08'	OPEN CLOSE	During open or close of a compressed cluster a compression control error was encountered. The error is further qualified by message 4A91I written to SYSLOG.
248	X'F8'	X'08'	OPEN	IKQLAB or IKQMVRJ (VSAM Space Management for SAM Feature) passed an invalid parameter list to the LABEL or EXTRACT macro. This is probably a system error. Programmer Response: Take a system dump, contact your IBM Support center and have the dump output, SYSLOG output, and a copy of the job stream available for problem determination.
252	X'FC'	Not zero	CLOSE	Automatic close of a DTF for a managed-SAM file failed.
254	X'FE'	Not zero	CLOSE	Close detected an unexpected return code from the lock manager. VSAM provides an IDUMP of the region containing the VSAM control blocks. Programmer Response: Rerun your job. If the problem persists, contact your IBM Support Center. You may wish to have the following available for problem determination. IDUMP output. Storage dump of the supervisor lock tables. A dump of the lock file if one was specified at IPL time. SYSLOG output. job stream.
		X'08'	OPEN	OPEN detected an unexpected return code from the lock manager. VSAM provides an IDUMP of the region containing the VSAM control blocks. Programmer Response: Rerun your job. If the problem persists, contact your IBM Support Center. The following may be helpful for problem determination. IDUMP output. Storage dump of the supervisor lock tables. A dump of the lock file if one was specified at IPL time. SYSLOG output. Job stream.
255	X'FF'	Not zero	CLOSE	An unexpected error occurred during catalog processing. The most common problems are: Not enough partition GETVIS space. Not enough programmer logical units for the partition. Not enough extent blocks. An error may have occurred during Lock Manager processing. VSAM provides an IDUMP of the region containing the VSAM control blocks. Programmer Response: If you are using a recoverable catalog, check that all required EXTENT statements are present and correct, and that sufficient storage is available. If you suspect the problem is one of those listed above, perform the corresponding action: Specify SIZE=AUTO on the EXEC statement to increase the size of the GETVIS area. If this does not work, rerun the job in a larger partition. If this is a multistep job, either divide it into separate jobs or provide ASSGN statements instead of simplified JCL. Use the GETVIS parameter in IPL SVA command to increase the amount of space allocated for extent blocks. Note: Extent blocks are only used if the parameter DASDFP was specified in IPL SYS command. Refer to return code 246, reason codes 8, 28 and 36, in IDCAMS Return and Reason Codes . If the problem persists, print the dump from the SYSDUMP library. Contact your IBM Support Center and make IDUMP output, the SYSLOG output and job stream available for problem determination.
		X'08'	OPEN	An unexpected error occurred during catalog processing. The most common problems are: Not enough partition GETVIS space. Not enough programmer logical units for the partition. Not enough extent blocks. An error may have occurred during Lock Manager processing. VSAM provides an IDUMP of the region containing the VSAM control blocks. Programmer Response: If you are using a recoverable catalog, check that all required EXTENT statements are present and correct, and that sufficient storage is available. If you are using a recoverable catalog, check that storage is available. If you suspect the problem is one of those listed above, perform the corresponding action: Specify SIZE=AUTO on the EXEC statement to increase the size of the GETVIS area. If this does not work, rerun the job in a larger partition. If this is a multi step job, either divide it into separate jobs or provide ASSGN statements instead of simplified JCL. Use the GETVIS parameter in IPL SVA command to increase the amount of space allocated for extent blocks. Note: Extent blocks are only used, if the parameter DASDFP was specified in IPL SYS command. Refer to return code 246, reason codes 8, 28 and 36, in IDCAMS Return and Reason Codes . If the problem persists, print the dump from the SYSDUMP library. Contact your IBM Support Center and make IDUMP output, the SYSLOG output, and job stream available for problem determination.