DML status codes

Status code giving information

001	FIND/FETCH format 1 or 7 with OR PRIOR/OR NEXT specification: No record has been found which matches the values given. The next record following in the sort sequence has been made available.

Status codes with progress information of the online utility

010	RELOCATE DML: Source and target levels are identical. Relocation has been completed. REORGPPP DML: End of realms reached. Reorganization has been completed.
011	RELOCATE DML: Source and target levels are 0 when INITIALIZE=*NO. REORGPPP DML: Current page number is 0 when INITIALIZE=*NO. When an attempt is made to continue the relocations with INITIALIZE=*NO, it is determined that no further information is available, e.g. because the database has been detached in the meantime or a new session section has been started.
012	RELOCATE DML: A locking conflict occurred with a parallel transaction when a source page was read. REORGPPP DML: A locking conflict occurred with a parallel transaction when a page was read.
013	A locking conflict occurred with a parallel transaction when a target page was read.

Status codes relating to data consistency:

018

Deadlock status (mutual locking of several transactions involving UDS/SQL resources); FINISH WITH CANCEL is executed. It is advisable to repeat the transaction (a limited number of times). For UDS-D: In UDS/SQL applications without openUTM, global deadlock recognition is carried out by means of timeout monitoring (PP DEADTIME) of wait situations. Once the time limit has been exceeded, the status code 018 is indicated, even if there is no actual deadlock.

020

FIND/FETCH (only CALL DML) A page to be accessed is locked by another transaction.

Status codes relating to retrieval of records

021	The end of a record type, set or realm has been reached. FIND/FETCH formats 2 (DUPLICATE) and 3 (USING): No record with the same values as the corresponding CRR or DRS can be found. FIND/FETCH format 3 (without USING): The end of the hits has been reached. FIND/FETCH format 4: No next or prior record can be found or integer or name contains a value that addresses no record within the realm/record type/set occurrence.
022	The transaction attempts to open a database or realm which is locked for UPDATE and RETRIEVAL. Possible reasons for the lock are: Database level: The database administrator has locked the database with the DAL command ACCESS. The DBDIR of the database is locked (see realm level). Realm level: The realm has been excluded from the database during restructuring. The realm has been disconnected by the database administrator or by UDS/SQL error handling. The realm has been locked by the database administrator, using the DAL command ACCESS.
023	In SET OCCURRENCE SELECTION IS THRU LOCATION MODE OF OWNER only: no set occurrence which satisfies the set selection criteria can be found.
024	No record satisfying the record selection expression can be found. FIND/FETCH format 1: The database key does not deliver any records for one of the following reasons: Its record reference number does not match the record type specified. Its value lies within the limits of its DBTT, but no associated record exists in the database. FIND/FETCH formats 2 (ANY) and 7: No record matching the initialized data elements or search expression can be found. FIND/FETCH format 4: No record can be found within the specified record type, realm or set occurrence.
027	The subscript of the specified item name does not lie within the range defined by the OCCURS clause in the subschema.
028	The specified database key contains an invalid record reference number or a record sequence number that lies outside the range of its DBTT.
029	FIND/FETCH formats 4 and 5: The Current of Realm or the Current of Set does not have the record type specified in the statement.

Status codes relating to currency indicators:

031	The Current of Realm, the Current of Set or the Current of Record type is not known. FIND/FETCH format 3: The Current of Set is owner and not a member of the specified set or the specified set name differs from the set name specified in the preceding FIND7. FIND/FETCH format 6 and format 7: The owner has been erased. IF format 2: The CRS has been erased or disconnected from the specified set.
032	The Current of Run Unit is not known or has been erased.
033	The Current of Run Unit does not have the record type specified in the statement.

Status codes relating to naming conventions:

042	Record type, set or realm is not defined in the called subschema, or an item which is part of an ASC, DESC or CALC key is not defined in the subschema, or following schema modification, the application program was not recompiled (COBOL DML) or the BCALLSI run was omitted (CALL DML), or an error occurred at the BIB interface (see status code 103) or in the case of an online utility a realm was specified in which no activities are permitted.
043	STORE and FIND/FETCH format 2: The AREA-ID data element contains the name of a realm which is not specified in the DDL WITHIN clause or does not belong to the called subschema, or in SET OCCURRENCE SELECTION IS THRU LOCATION MODE OF OWNER and owner record type = LOCATION MODE IS CALC: the AREA-ID item of the owner record contains the name of a realm which is not specified in the DDL WITHIN clause or does not belong to the called subschema.
044	IF: Specification of a dynamic set is not permitted.

Status codes relating to data elements:

051

Duplicate occurrences of key values in the database. This means that the execution of a DML statement would contradict a DUPLICATES ARE NOT ALLOWED specification in an ORDER IS SORTED BY DEFINED KEYS clause or SEARCH KEY clause of a set in which the record involved is a member, or the LOCATION MODE IS CALC or SEARCH KEY clause of the record involved.

Status codes relating to records:

071	FIND/FETCH format 2 (DUPLICATE), 3, 4 and 5: The entry point of the DML statement (CRR, CRA or CRS) has been deleted or removed from the current set occurrence. If the records found are processed (FIND3 without USING), update operations of the user’s own transaction do not result in the entry point being lost, only updates performed by foreign transactions cause this to happen.
072	ERASE: The record involved is owner of a non-empty set occurrence and therefore cannot be erased by the selected ERASE variant.

Status codes relating to set membership:

081	CONNECT (set-name): The CRU is already a member in one of the specified sets or one of the specified sets is not a member of the CRU. CONNECT (ALL): The CRU is already a member of all its member sets. MODIFY (set-name): One of the specified sets is not a member set of the CRU. MODIFY (ALL): The CRU is a member of none of its member sets.
082	DISCONNECT (set-name): The CRU is a MANDATORY member of one of the specified sets or one of the specified sets is not a member of the CRU DISCONNECT (FROM ALL): No member set of the CRU is OPTIONAL.
083	DISCONNECT (set-name) and MODIFY (set-name): The CRU is not a member in one of the specified sets DISCONNECT (FROM ALL): At least one member set of the CRU is OPTIONAL but the CRU is not a member of any of these OPTIONAL sets

Status codes relating to a READY status:

091	A realm is not in the READY status (i.e. a realm was not explicitly specified at READY or is not part of the current subschema), or realm names were explicitly specified at READY in an ERASE PERMANENT/ SELECTIVE/ALL statement, or the DBTT of a record type to be relocated by the online utility is in an unopened realm.
092	No DML statement containing an update function is permitted in a RETRIEVAL processing chain, or the processing chain specified with an ERASE PERMANENT/SELECTIVE/ALL was not opened with EXCLUSIVE UPDATE, or in conjunction with the P parameter PP TA-ACCESS=SHARED an attempt has been made to open a processing chain in usage mode PROTECTED or EXCLUSIVE.
093	The Database Handler (DBH) does not allow the processing chain since the database involved is already open within the transaction (second READY within a processing chain).
099	(only CALL DML or Online Utility) While opening a transaction, a realm is locked by a different transaction.

Status codes relating to erroneous DML statements

101	FIND/FETCH Format 4: The value zero has been specified for integer or item-name or a negative value was used for a search in a CHAIN that is not chained backward FIND/FETCH format 6: setname must not identify a singular set. FIND/FETCH format 7: OR PRIOR or OR NEXT could not be executed, since no sorted and indexed key was found “WITHIN setname-1 USING itemname-1,...” was specified. Specification of a dynamic set in setname-1 is not permitted. LIMITED BY dynamic-set ... SORTED BY ... was specified. It is not possible to sort the intersection of a hit list and a dynamic set. LIMITED BY sorted-dynamic-set ... was specified. It is not possible to obtain the intersection of a hit list and a sorted dynamic set. FINISH: Type of FINISH (with or without CANCEL) cannot be identified.
102	SET, ACCEPT (Format 1): A large database key value (database key value with REC-REF > 254 and/or an RSQ > 224-1) cannot be accommodated in an item of type USAGE IS DATABASE-KEY. A subschema must be used in which SUBSCHEMA FORM IS OLD is not specified and which was created in UDS/SQL V2.0 or higher. The field specified must also be of the type USAGE IS DATABASE-KEY-LONG. FIND/FETCH-1, ACCEPT (Format 2): A large database key value that is passed to UDS/SQL by an application program in an item of type USAGE IS DATABASE-KEY-LONG cannot be processed with a subschema of UDS/SQL V1.2 or with a subschema that was compiled with “SUBSCHEMA FORM IS OLD”.
103	Error in the BIB interface. Possible cause: incorrect COBOL compiler or incorrect COBOL runtime system, error in the CALL-DML converter, in IQS, in the online utility, or in a utility routine which generates BIBs, or error in the Database Handler.

Status codes relating to system errors:

113	When accessing a database page a serious error was discovered in the Database Handler or in the database.

Status codes relating to UDS/SQL resources:

122	The transaction was prematurely terminated with CANCEL by the DBH; possible causes for this are: RLOG file too small or split too often UDS/SQL buffer too small, increase PP BUFFERSIZE=n. Transaction rolled back in a deadlock which has been resolved in the meantime. Intervention by the database administrator with DAL (commands ABORT, PERFORM, CLOSE). New update transactions during writing of a checkpoint. Occurrence of a file or programming error which can be bypassed (temporarily) by executing CANCEL for the transaction. An error in a DML statement which cannot be rolled back on its own, and thus requires a CANCEL of the complete transaction. The database administrator was notified (by means of a UDS/SQL message). For UDS-D: Transaction rollback can also be due to errors or administrator intervention in a remote configuration (e.g. ABORT, CLOSE CALLS, CLOSE RUN-UNITS, %TERM) or due to errors in the link to a remote configuration.
123	The transaction attempts to open a realm, which is locked against updates, with READY USAGE-MODE UPDATE. The lock is due to one of the following reasons: Configuration level: The current session of the independent DBH was started without RLOG logging (PP LOG=NO). Opening of the RLOG file was unsuccessful, which means that RLOG logging is currently impossible. Database level: The database is being activated as a SHARED RETRIEVAL database. The database is not an original database, but a shadow database. Opening of a new ALOG file was unsuccessful, which means that AFIM logging is currently impossible. The database administrator has locked the database against updates by means of the DAL command ACCESS. The DBDIR of the database is locked for updates (see realm level). Realm level: The database administrator has locked the realm against updates by means of the DAL command ACCESS. The transaction attempts to open a realm of a remote database although the current session runs without RLOG logging (due to PP LOG=NO or unsuccessful open of RLOG file); there is thus no basis for the two-phase commit protocol of distributed transactions.
124	The transaction was prematurely terminated with CANCEL by the DBH. Cause: New update transaction or update processing chain when writing a checkpoint or switching the RLOG file. This status code is set if the load parameter PP ORDER-DBSTATUS=SPECIAL was specified for the current session. Otherwise, status code 122 is set under the conditions indicated above.
131	The Database Handler does not allow the transaction since the maximum permitted number of parallel transactions or user tasks, which was specified by the load parameter TRANSACTION when the Database Handler was loaded, has been reached.
132	The Database Handler does not allow the transaction since the maximum permitted number of subschemas, which was specified by the load parameter SUBSCHEMA when the Database Handler was loaded, has been reached.

Status codes relating to the sequence of DML statements

134	The Database Handler does not allow the DML statement since no transaction is open.
136	A DML statement, though belonging to an existing transaction, is rejected because it refers to a database (supplies a DB reference) for which no processing chain of the transaction currently exists.
137	It is not possible to mix SQL and non-SQL statements in a transaction (exception: accessing different UDS/SQL configurations via openUTM). A mixture of COBOL DML and CALL DML statements in a processing chain is not permitted.

Status codes relating to subschemas:

141	The transaction has specified an invalid or unknown subschema name, or the first 6 characters of the subschema name are not unique in the current DB configuration, or the database involved is not active. For UDS-D: The specified subschema is not in the local configuration and not in the distribution table. in the distribution table, but not in the corresponding UDS/SQL configuration. in the distribution table, but the corresponding UDS/SQL configuration is not accessible, because the computer is not accessible, the configuration is not running or is running without distribution active. in the distribution table but locked, or the related database or configuration is locked. in the distribution table and has a version >= 2.0, but the remote UDS/SQL configuration is working with UDS/SQL Version V1.2. not in the local configuration and UDS-D has not been started in the local configuration. The number of remote databases addressed by this transaction exceeds the value PP DISDB.
142	The subschema description in DBDIR (SSIA) has been destroyed. Repeat BGSSIA run.
144	The DML statement specifies a different subschema from the one specified in the current READY statement (subschema reference).
145	The subschema specified in the READY statement cannot be processed because it does not match the current status of the schema (subschema DDL compilation and/or BGSSIA run missing after database restructuring) or the READY statement is rejected because the UDS/SQL version does not match the database: Either the database was set so as to ensure the correct century is used in conjunction with two-digit year fields or this setting has not been properly removed. This means it may only be processed using a UDS/SQL version as of V2.0B30. A subschema contains national data (UNICODE). Therefore it may only be processed using a UDS/SQL version as of V2.5. A subschema contains BINARY 63 data. Therefore it may only be processed using a UDS/SQL version as of V2.9.
146	COBOL DML: The subschema with which the module of the current DML statement was compiled does not correspond with the current status of the database. CALL DML: the SSITAB module used does not correspond with the current status of the database.

Status codes relating to DBH availability:

151	The Database Handler is not yet available or is being terminated normally (termination in progress).
152	The Database Handler has been terminated abnormally.
154	An irrecoverable error has been detected in UDS/SQL; the program should be terminated (STOP RUN for COBOL programs). The transaction was not completed.
155	While UDS/SQL was processing a DML statement, a further DML statement for the same transaction was received (deserialization). Possible cause of error: Asynchronous activities performed by the user program (e.g. DML statement in STXIT routine) or UDS/SQL system error.

Further status codes of the UDS online utility

161	A transaction of an online utility is already active in the same realm.
162	A user transaction which is running in parallel has activated an online realm extension and thus temporarily hindered the online utility.
163	The online utility is not permitted in a temporary realm.
164	USAGE-MODE EXCLUSIVE UPDATE is required for this RELOCATE type.
165	The SET specified is not a distributable list.
166	The realm specified is not permitted for the record type.
167	Conflicting change of a parallel user TA. The utility TA is reset.

Status codes relating to FIND/FETCH:

183	The search expression exceeds the maximum length.
184	The temporary realm is not available.
191	Both the object set and the LIMITED set are dynamic sets.
192	The LIMITED set is empty.
193	FIND/FETCH format 7: The LIMITED set contains a different record type from the object set FIND/FETCH formats 4 and 7: The object set is dynamic and contains a record type different from the on specified. FIND/FETCH format 3: The specified record name differs from the record name specified in the preceding FIND/FETCH format 7.
194	The comparison value or sort item has the length 0 or a length that is not permitted for the item type.
195	The comparison value or sort item has an unknown item type or the comparison value contains incompatible data.
197	No preceding FIND/FETCH format 7.
198	The CRS of the result set has been disconnected from the object set or connected to another occurrence by a different transaction.

Status codes relating to interoperation with open UTM:

200	FINISH: The FINISH statement has been accepted, but the execution of FINISH will be delayed until the openUTM end-of-transaction call to the DC controller (PEND). No further DML statements are accepted.
201	A further DML statement was issued after the pended FINISH. The DML statement is ignored.
218	Deadlock involving more than one system that can only be resolved by releasing the openUTM application task (e.g. with PEND RS). Examples: local UDS/SQL openUTM operation: Deadlock between UDS/SQL resources (data) and openUTM resources (tasks). Distributed processing via UDS-D or openUTM-D: Deadlock between UDS/SQL resources (data) and/or openUTM resources (tasks). This type of deadlock is recognized by means of timeout monitoring of wait situations (PP DEADTIME). When this time limit is exceeded, status code 218 is indicated, even if no actual deadlock has occurred.

Status codes relating to LOOK:

781	Element not found or realm name unknown to the online utility.
782	No next element available.
783	One element in the list not found.
784	The item reference entered does not exist. The description with the next smallest item reference was output.
785	The result vector of a compound LOOKC function must be retrieved by a contiguous sequence of corresponding LOOKC statements.
786	The record type cannot be processed with this subschema as it contains data of a type which is not known to the application program.
789	The specified subschema does not exist.

Status codes relating to allocation of memory space or database key:

802	The memory space in the realm is exhausted or an activated online realm extension has failed. The record involved cannot be stored or inserted in a set occurrence.
804	No further database key is available for storage of a new record or an activated online realm extension has failed.
805	The system address space of the DBH is exhausted. The DBH tables can no longer be extended dynamically. The database administrator has been notified.

Status codes relating to variable-length items and compression:

888	The length of the variable item is greater than that defined in the subschema or is negative.
898	STORE/MODIFY format 2 is not allowed for variable-length items.
899	STORE: The number of items to be stored is so great that the size of the compressed record is greater than one page. GET: One of the desired items is not present in the compressed record in the database. MODIFY format 1: This format is not allowed if the record accessed is present in compressed form. MODIFY format 2: One of the items to be modified is not present in the compressed record.

Status codes relating to access privileges

901	Access to a realm, record or set is not permitted within the user group or the utility routine ONLINE-PRIVACY or ONLINE-UTILITY is trying to access a database which is not contained in the utility routine’s execution USER-ID. It is not possible to bypass this behavior of the utility routines by setting the P parameter PRIVACY-CHECK to OFF.
950	The specified user group is not known (see the manual “Creation and Restructuring”, BPRIVACY).
954	No access authorization has been defined for the specified user group.