After completion of the @MODIFY function, the ERRSTAT field in the IDMS communications block indicates the outcome of the operation. The following is a list of the acceptable status codes for this function and their corresponding meaning:
The request has been serviced successfully.
The OCCURS DEPENDING ON item is less than 0 or greater than the maximum number of occurrences of the control element.
Modification of the record would violate a duplicates-not-allowed option for a CALC record, a sorted set, or an index set.
Currency has not been established for the specified record.
The specified record cannot be found. The record name has probably been misspelled.
The specified record's area has not been readied in one of the three update usage modes.
The subschema specifies an access restriction that prohibits modification of the named record.
There is insufficient space to hold the modified variable-length record occurrence.
A current record of run unit has not been established or has been nullified by a previous @ERASE statement.
The record has not been bound.
The current record of run unit is not the same type as the specified record.
An area other than the area of the named record has been readied with an incorrect usage mode.
No current record of set type has been established.
All sorted sets in which the specified record participates have not been included in the subschema.
An invalid length has been defined for a variable-length record.
A record occurrence has been encountered whose type is inconsistent with the set named in the ERROR-SET field of the IDMS communications block. Probable causes are either a broken chain and improper database description.
No record can be found for an internal db-key. This code usually indicates a broken chain.
Either the length of a record in a native VSAM ESDS has been changed, or a prime key in native VSAM KSDS has been modified.
|
Copyright © 2014 CA.
All rights reserved.
|
|