• For a key-sequenced data set
  • PUT sequential or skip-sequential processing
  • GET sequential, single string input only
  • GET skip-sequential processing and the previous request is not a POINT
• For a relative record data set
  • GET skip-sequential processing
  • PUT skip-sequential processing

Offset Length Description
 
0      4      Address of RPL in exclusive control
4      1      Flag Byte: - Not used For RLS
              X'00'--neither RPL doing a control
                     area split
              X'01'--current RPL doing a control
                     area split
              X'02'--other RPL doing a control
                     area split

If this request's RPL specifies a MSGAREA of length 4 bytes or greater, the address of an RPL whose lock on this record caused this request to be rejected is returned in the first 4 bytes of MSGAREA. The application may choose to issue an ENDREQ on that RPL and then reissue this POINT, GET NUP, or GET UPD request.

For VSAM RLS and DFSMStvs, another LUWID holds an exclusive lock on this record. The combination of one or more LUWIDs waiting for other record locks held by this LUWID and this LUWID waiting for this record lock produced a deadlock.

Offset Length Description
 
0      4      Address of problem determination area
              If you see this error, you are required 
              to free this area, for example, with:
              ?STORAGE (RELEASE) 
where LENGTH=VPDISIZE, SP=0,KEY=user's key.

For VSAM RLS and DFSMStvs, another LUWID holds an exclusive lock on this record. This request waited for the record lock until the timeout interval expired.

Offset Length Description
 
0      4      Address of problem determination area.
              If you see this error, you are required 
              to free this area, for example, with:
              ?STORAGE (RELEASE) 
where LENGTH=VPDISIZE, SP=0,KEY=user's key.

For VSAM RLS and DFSMStvs, another LUWID holds a retained lock on this record.

Offset Length Description
 
0      4      Address of problem determination area.
              If you see this error, you are required 
              to free this area, for example, with:
              ?STORAGE (RELEASE) 
where LENGTH=VPDISIZE, SP=0,KEY=user's key.

For VSAM RLS and DFSMStvs, the error can occur for a GET request when the same error has been issued for a preceding PUT request on the same ACB.

• CNV processing
• The specified RPL is asynchronous
• Chained RPLs
• Path processing
• Shared resources (LSR/GSR) indeterminate buffer status
• Load mode
• Fixed-length relative record data set
• Data set contains spanned records
• User not in key 0 and supervisor state
• End-of-volume in process (secondary allocation)

For VSAM RLS and DFSMStvs, this error indicates an invalid reuse of an RLS RPL.

This RPL has position established for VSAM RLS and DFSMStvs access to a data set. The application has changed the ACB or the LUWID, or both. VSAM RLS and DFSMStvs do not permit this form of RPL reuse. This error does not change or lose the string's position. Before changing the ACB or LUWID, the application must issue an ENDREQ on the RPL to release the string's position.

RPL reuse violation. The RPL request had positioning information from a previous request and the ACB or LUWID specified in the RPL, or both, did not match that of the prior request.

For VSAM RLS and DFSMStvs, the limit of 1024 outstanding requests for this ACB has been exceeded.

For VSAM RLS and DFSMStvs, the application issued a GETIX or PUTIX. GETIX and PUTIX are not supported by VSAM RLS and DFSMStvs

• For access to an entry-sequenced data set
• For access to an entry-sequenced data set via a path
• With control interval access

• For a PUT request
• In the previous request parameter list in a chain of request parameter lists
• For UBF processing

• SKP was specified and either KEY was not specified or BWD was specified.
• XRBA was not specified in the RPL OPTCD when a GET DIR or a POINT request was issued in ADR or CNV mode with LRD=OFF, and RPLARG points to a nonzero argument (RBA), while processing an extended-addressing data set.
• BWD was specified for CNV processing.
• FWD and LRD were specified.
• Neither ADR, CNV, nor KEY was specified in the RPL.
• BFRNO is invalid (less than 1 or greater than the number of buffers in the pool).
• WRTBFR, MRKBFR, or SCHBFR was issued, but either TRANSID was greater than 31 or the shared resource option was not specified.
• ICI processing was specified, but a request other than a GET or a PUT was issued.
• MRKBFR MARK=OUT or MARK=RLS was issued but the RPL did not have a data buffer associated with it.
• The RPL specified WAITX, but the ACB did not specify LSR or GSR.
• CNV processing is not allowed for compressed data sets. Only VERIFY and VERIFY REFRESH are allowed.
• VERIFY was specified for a z/OS UNIX file.
• BWD or UPD was specified for a z/OS UNIX file.
• DIR was specified for a z/OS UNIX file, that is an FIFO or character special file.
• Non-key access issued against extended-format, extended-addressing data set when RBA/XRBA is required for positioning.

1. RECLEN specified was larger than the maximum allowed, equal to 0, or smaller than the sum of the length and the displacement of the key field.
2. RECLEN was not equal to record (slot) size specified for a fixed-length RRDS.
3. RECLEN was not sufficient to contain the new alternate index key pointer. With non-unique UPGRADE AIX®‘s, the record is automatically increased in size each time a record is added to the base cluster and this can cause an incorrect RECLEN. Make sure the maximum RECORDSIZE on the alternate index is large enough for all base pointers it must contain.

Close the data set, restore it, and re-open to re-access if necessary.

If multiple RPL requests are issued for alternate indexes, getting return code 144(X'90') might mean a temporary situation where processing has not been completed on either the base cluster or the associated alternate indexes.

For example, you have issued multiple RPL requests including erase requests to the path or base cluster, and got a return code of X'90'. This might be a temporary situation where the base cluster has been erased, but the associated alternate index has not been erased. If you provide a message area using the MSGAREA parameter of the RPL macro, VSAM returns the address of an RPL doing the erase when the return code X'90' was set.

This IDAQUIES request is rejected because the requestor does not have update authority to the sphere. Issued for the following: * This is a type QUICLOSE request. Successful completion of the request results in a catalog update to mark the sphere quiesced. Because the requestor does not have update authority, the request is rejected.

The catalog shows this sphere is quiesced. Successful completion of the QUIOPEN request would result in an update to the catalog to reset the quiesced state of the sphere. because the requestor does not have update authority, the request is rejected.

For rls, the IDAQUIES request is rejected because an IDAQUIES is already in progress for this sphere.

Offset  Length Description
------  ------ -----------
0         1    Type of quiesce event already in progress for this sphere.
               Quiesce type constants are defined in IFGQUIES mac.

For MACRF=RLS, the application issued an ABEND condition while VSAM was processing this request. The VSAM RLS FRR (Functional Recovery Routine) intercepted the failure and failed the VSAM request with this reason code.

For MACRF=RLS, the user task was cancelled while the request was being processed.

For base VSAM, an EOV initialize failure occurred. For example, with data set name sharing, if dynamic allocation (DYNALLOC) is issued before the first OPEN of the data set and that first ACB is later closed, EOVs against the data set will fail because EOV is unable to find the TIOT offset indicated in the shared control block structure. In that case, either close all DDNAMEs for the data set and then do an OPEN, or ensure that the first DDNAME opened remains open.

For MACRF=RLS, the sphere is in lost locks state. A record management request was issued by this SUBSYSNM, but these requests are not allowed until the sphere is out of lost locks state.

For MACRF=RLS, a lock for the VSAM request required space in the record table, but the table was full. Installation action is needed to modify the CFRM policy and rebuild the lock structure.

For LSR, the cache request is purged.