CA IDMS Minor Codes

CA IDMS Status Codes › CA IDMS Minor Codes

CA IDMS Minor Codes

Minor codes and their meanings are listed below in numerical order by minor code. For each minor code, the most commonly occurring major/minor combinations are also listed and explained.

Minor Code	Status Code	DML Function and Status Description
00		This minor code combined with a 00 major code indicates successful completion; combined with a nonzero major code, it indicates unsuccessful completion as a result of problems with the CA IDMS central version. Problems such as timeouts and program checks can cause the return of an nn00 status. Refer to the DC/UCF log to determine the specific cause.
	0000	Any DML function The DML function requested has executed successfully.
	1400	BIND RECORD BIND RUN-UNIT The BIND RUN-UNIT statement or BIND RECORD statement has not been issued or cannot be recognized. This code usually means that the IDMS communications block (SUBSCHEMA-CTRL) is not aligned on a full word boundary.
01		An area has not been readied, or an IF operation has determined that the set is not empty or that the current record of run unit is not a member of the set.
	0301	FIND/OBTAIN DBKEY FIND/OBTAIN CURRENT FIND/OBTAIN WITHIN SET/AREA FIND/OBTAIN OWNER FIND/OBTAIN CALC/DUPLICATE FIND/OBTAIN WITHIN SET USING SORT KEY The area in which the object record participates has not been readied. Probable causes for the return of this status code are: No READY statement has been issued since the most recently issued BIND RUN-UNIT statement. The READY statement is missing or has been bypassed by program logic.
	1601	IF The named set is not empty, or the record that is current of run unit is not a member of the named set. This status triggers or bypasses execution of the imperative statement included in the IF statement: IF set-name IS EMPTY imperative-statement-a—1601 means that the set is not empty (that is, IF evaluates as FALSE) and, consequently, that the imperative statement is not to be executed. IF set-name IS NOT EMPTY imperative-statement-a—1601 means that the set is not empty (that is, IF evaluates as TRUE) and, consequently, that the imperative statement is to be executed. IF set-name MEMBER imperative-statement-a—1601 means that the current record of run unit does not participate as a member in any occurrences of the named set (that is, IF evaluates as FALSE) and, consequently, that the imperative statement is not to be executed. IF NOT set-name MEMBER imperative-statement-a—1601 means that the current record of run unit does not participate as a member in any occurrences of the named set (that is, IF evaluates as TRUE) and, consequently, that the imperative statement is to be executed.
	2001	Logical Record Facility Requests The requested logical record is not found in the subschema. (The path DML statement, EVALUATE, returns 0000 if true, and 2001 if false.)
02		IDMS has attempted to access a record directly by its db-key, but the db-key is not within the page range of the area to which the record is assigned.
	0302	FIND/OBTAIN DBKEY FIND/OBTAIN WITHIN SET FIND/OBTAIN OWNER FIND/OBTAIN CALC/DUPLICATE FIND/OBTAIN WITHIN SET USING SORT KEY The db-key to be retrieved is inconsistent with the area in which the specified record is stored. Probable causes for the return of this status code are: The db-key has not been initialized properly. The record name is incorrect. The program has invoked the wrong subschema. A bad db-key was extracted from a record's prefix while walking a set relationship indicating a possible broken chain. If the FIND/OBTAIN DBKEY command does not specify a record name, the return of this status code means that the db-key specified is not within the range of the DMCL tables.
	1202	STORE The suggested db-key is not within the page range of the area to which the specified record is assigned. This status code occurs only for record types defined with a DIRECT location mode. The most probable cause of this error is failure to specify correctly the desired db-key.
03		Invalid currency for the named record, set, or area. This can only occur when a run unit is sharing a transaction with other database sessions. The 03 minor status is returned if the run unit tries to retrieve or update a record using a currency that has been invalidated because of changes made by another database session that is sharing the same transaction.
	0203	Invalid currency for the named record to ERASE. This can only occur when a run unit is sharing a transaction with other database sessions. The 03 minor status is returned if the run unit tries to erase a record using a currency that has been invalidated because of changes made by another database session that is sharing the same transaction.
	0303	Invalid currency for a record to be retrieved on a FIND. This can only occur when a run unit is sharing a transaction with other database sessions. The 03 minor status is returned if the run unit tries to find a record using a currency that has been invalidated because of changes made by another database session that is sharing the same transaction.
	0503	Invalid currency for a record to be retrieved on a GET. This can only occur when a run unit is sharing a transaction with other database sessions. The 03 minor status is returned if the run unit tries to get a record using a currency that has been invalidated because of changes made by another database session that is sharing the same transaction.
	0803	Invalid currency for a record to be altered by a MODIFY. This can only occur when a run unit is sharing a transaction with other database sessions. The 03 minor status is returned if the run unit tries to modify a record using currency that has been invalidated because of changes made by another database session that is sharing the same transaction.
	1203	Invalid currency for a record to be inserted by a STORE. This can only occur when a run unit is sharing a transaction with other database sessions. The 03 minor status is returned if the run unit tries to store a record and a currency in any set in which the record is an owner or member of and has been invalidated because of changes made by another database session that is sharing the same transaction.
	1503	The dbkey that is the object of an ACCEPT has been invalidated. This can only occur when a run unit is sharing a transaction with other database sessions. The 03 minor status is returned if the run unit tries to retrieve a dbkey and a currency has been invalidated because of changes made by another database session that is sharing the same transaction.
04		The occurrence count of a variably occurring element (that is, OCCURS DEPENDING ON) has been specified as less than zero or greater than the maximum number of occurrences of the control element, or, zero has been specified as the sequence number of the object record for a FIND/OBTAIN sequence-vn WITHIN SET/AREA. This is usually a program logic error. Check to determine if the control element has been updated correctly.
	0304	FIND/OBTAIN WITHIN SET/AREA An explicit value of zero or a variable field containing a value of zero has been specified for the sequence number of the object record.
	0804	MODIFY The OCCURS DEPENDING ON item is less than 0 or greater than the maximum number of occurrences of the control element.
	1204	STORE The OCCURS DEPENDING ON item is less than 0 or greater than the maximum number of occurrences of the control element.
05		Execution of the specified DML function will violate a DUPLICATES NOT ALLOWED restriction. The three possible restrictions are: The object record has been defined as CALC with DUPLICATES NOT ALLOWED. This restriction can only be violated by a MODIFY or STORE command. The object record has been defined as a member in a sorted set that has been restricted by DUPLICATES NOT ALLOWED. The object record has been defined as a member in an index that has been restricted by DUPS=NO (explicitly or by default).
	0705	CONNECT Connection of the named record will violate a DUPLICATES NOT ALLOWED restriction. The probable cause for the return of this status code is that the program did not check for the existence of a duplicate index key or sort key before issuing the CONNECT.
	0805	MODIFY Modification of a CALC-key, sort key, or index key would violate a DUPLICATES NOT ALLOWED restriction. The probable cause for the return of this status code is that the program did not check for the existence of duplicate keys before issuing the MODIFY. The error set (as indicated in the IDMS communications block) is the set in which the violation has occurred.
	1205	STORE Storage of the record will violate a DUPLICATES NOT ALLOWED restriction. The probable cause for the return of this status code is that the program did not check for the existence of duplicate keys for all sets affected by the STORE before issuing the STORE. The error set (as indicated in the IDMS communications block) is the set in which the violation has occurred.
06		Currency has not been established for the object record, set, or area. An attempt has been made to access a record occurrence without first establishing the required currency.
	0306	FIND/OBTAIN CURRENT Currency has not been established for the named record, set, or area.
		FIND/OBTAIN WITHIN SET/AREA Currency has not been established for the named record, set, or area.
		FIND/OBTAIN OWNER Currency has not been established for the named set.
		FIND/OBTAIN DUPLICATE Currency has not been established for the named record.
		FIND/OBTAIN WITHIN SET USING SORT KEY Currency has not been established for the named set.
	0506	GET Currency has not been established. This status code is returned only for the unqualified form of the GET function.
	0606	KEEP Currency has not been established for the named record, set, or area.
	0706	CONNECT Currency has not been established for the object record or set.
	1106	DISCONNECT Currency has not been established for the named record. This status can result from issuing a DISCONNECT command for a record that was previously erased.
	1606	IF Run-unit currency has been nullified by a previous ERASE statement. A probable cause for the return of this status code is that the IF follows a previously executed ERASE that has nullified the run-unit currency.
07		The end of a set, area, or indexed set has been reached, or the set is empty.
	0307	FIND/OBTAIN WITHIN SET/AREA The end of a set, area, or indexed set has been reached, or the set is empty. Probable causes for the return of this status code are: The set, area, or indexed set is being walked in the NEXT direction, and the most recently retrieved record occurrence is the last occurrence in the set, area, or indexed set. The set, area, or indexed set is being walked in the PRIOR direction, and the most recently retrieved record occurrence is the first occurrence in the set, area, or indexed set. The set, area, or indexed set is empty.
	1707	RETURN A RETURN has reached the end of the indexed set, or the indexed set is empty. The present RETURN cannot be executed. Probable causes for the return of this status code are: The indexed set is being walked in the NEXT direction, and the most recently retrieved record occurrence is the last occurrence in the indexed set. The indexed set is being walked in the PRIOR direction, and the most recently retrieved record occurrence is the first occurrence in the indexed set. The indexed set is empty.
08		The object record, set, procedure, or LR verb is not in the specified subschema, or the object record is not a member of the object set. This minor code is usually issued for one of the following reasons: The program has invoked the wrong subschema. The record name or set name is misspelled or has been overlayed. The named record or set is not described in the specified subschema. The record name/set name combination is invalid.
	0208	ERASE The object record is not in the specified subschema.
	0308	FIND/OBTAIN DBKEY FIND/OBTAIN CURRENT FIND/OBTAIN CALC/DUPLICATE The object record is not in the specified subschema.
		FIND/OBTAIN OWNER The named set is not in the subschema.
		FIND/OBTAIN WITHIN SET/AREA FIND/OBTAIN WITHIN SET USING SORT KEY The named record or set is not in the specified subschema, or the named record is not defined as a member of the named set.
	0508	GET The object record is not in the specified subschema.
	0608	KEEP The named record or set is not in the subschema.
	0708	CONNECT The named record or set is not in the specified subschema, or the named record is not a member of the named set.
	1108	DISCONNECT The named record or set is not in the specified subschema, or the named record is not a member of the named set.
	1208	STORE The named record is not in the specified subschema.
	1408	BIND RECORD BIND PROCEDURE The named record or procedure is not in the specified subschema.
	1508	ACCEPT DBKEY FROM CURRENCY The object record or set is not in the specified subschema.
		ACCEPT DBKEY RELATIVE TO CURRENCY The object set is not in the specified subschema.
		ACCEPT BIND The object record is not in the specified subschema.
		ACCEPT PROCEDURE The named procedure is not in the specified subschema.
	1608	IF The object record or set is not in the specified subschema, or the record type of the current record of run unit is not defined in the subschema as a member of the named set.
	2008	Logical Record Facility Requests The named logical record is not defined in the subschema, or the specified DML verb is not permitted with the named logical record.
09		The area has been readied for retrieval, but the DML issued requires a usage mode of UPDATE.
	0209	ERASE The object record's area has not been readied in one of the three update usage modes.
	0709	CONNECT The object record's area has not been readied in one of the three update usage modes.
	0809	MODIFY The object record's area has not been readied in one of the three update usage modes.
	1109	DISCONNECT The object record's area has not been readied in one of the three update usage modes.
	1209	STORE The object record's area has not been readied in one of the three update usage modes.
10		An existing access restriction or a subschema usage restriction prevents execution of the requested DML function. This minor code often indicates that the subschema has been changed since the program was last compiled. For example, an access restriction such as DISCONNECT IS NOT ALLOWED may have been added to the subschema definition of a record or set. The program compiled successfully because the restriction was not present in the subschema at compilation time. Check the subschema for added access restrictions.
	0010	Any DML function The program has attempted to access a database record, but the subschema in use allows access to logical records only; that is, the clause USAGE IS LR is included in the subschema definition.
	0210	ERASE The subschema specifies an access restriction that prohibits execution of the ERASE function. The subschema definition of the object record specifies the option ERASE IS NOT ALLOWED.
	0310	FIND/OBTAIN DBKEY FIND/OBTAIN CURRENT FIND/OBTAIN WITHIN SET/AREA FIND/OBTAIN OWNER FIND/OBTAIN CALC/DUPLICATE FIND/OBTAIN WITHIN SET USING SORT KEY The subschema specifies an access restriction that prohibits execution of the FIND/OBTAIN function. The subschema definition of the object record or of the object set specifies the option FIND IS NOT ALLOWED.
	0510	GET The subschema specifies an access restriction that prohibits execution of the GET function. The subschema definition of the object record specifies the option GET IS NOT ALLOWED. Note that an 0510 status code can be returned on the GET portion of an OBTAIN function.
	0610	KEEP The subschema specifies an access restriction that prohibits execution of the KEEP function. The subschema definition of the object record or of the object set specifies the option KEEP IS NOT ALLOWED. Note that an 0610 status code can be returned on the KEEP portion of a FIND/OBTAIN KEEP function.
	0710	CONNECT The subschema specifies an access restriction that prohibits execution of the CONNECT function. The subschema definition of the object record or of the object set specifies the option CONNECT IS NOT ALLOWED.
	0810	MODIFY The subschema specifies an access restriction that prohibits execution of the MODIFY function. The subschema definition of the object record specifies the option MODIFY IS NOT ALLOWED.
	0910	READY The subschema specifies an access restriction on the object area that prohibits execution of the READY function in the usage mode specified. If this status code is returned while attempting to execute the CA IDMS restructure utility, ensure that all areas in the specified subschema are allowed to be readied in EXCLUSIVE UPDATE usage mode. If this status code is returned during an attempt to execute the CA IDMS database load utility, ensure that all areas in the specified subschema are allowed to be readied in EXCLUSIVE UPDATE usage mode.
	1110	DISCONNECT The subschema specifies an access restriction that prohibits execution of the DISCONNECT function. The subschema definition of the object record or of the object set specifies the option DISCONNECT IS NOT ALLOWED.
	1210	STORE The subschema specifies an access restriction that prohibits execution of the STORE function. The subschema definition of the object record specifies the option STORE IS NOT ALLOWED.
	2010	Logical Record Facility Requests The program has attempted to access a logical record, but the subschema in use allows access to database records only; that is, the clause USAGE IS DML is included in the subschema definition.
11		The record cannot be stored in the specified area due to insufficient space.
	0711	CONNECT An attempt to allocate space within a database failed while executing a CONNECT verb. This can occur when connecting a record occurrence to an index and an attempt to allocate space for a new SR7/SR8 record within the area containing the index components fails.
	0811	MODIFY No database page in the area and page range assigned to the specified variable-length record contains sufficient space to hold the modified record occurrence. This status code can mean that the minimum fragment specified in the schema is too large. If so, no single page has enough space to store the minimum fragment.
	1211	STORE No database page in the area and page range assigned to the specified record contains sufficient space to store the record occurrence. Note that pages containing 255 records are considered full and are not available for storing additional records. Note: If the DMCL specifies a PAGE RESERVE clause for the area in question, space may be available but not accessible for the STORE function. This space can be accessed by changing the DMCL.
13		Run-unit currency has not been established or has been nullified by a previous ERASE statement.
	0813	MODIFY Run-unit currency has been nullified by a previous ERASE statement. A probable cause for the return of this status code is that the record to be modified has not been established as current of run unit.
	1613	IF Run-unit currency has not been established.
15		The DISCONNECT statement cannot be executed because the object record has been defined as a mandatory automatic member of the set.
	1115	DISCONNECT The named record is defined as a mandatory member of the named set and, therefore, cannot be disconnected from the set.
16		The record is already a member of the set and, therefore, cannot be connected to the set.
	0716	CONNECT The object record is already a member of the named set; the CONNECT cannot be executed.
17		The transaction manager encountered an error. This status code is usually accompanied by an error message written to the operator console describing the nature of the error.
	1417	BIND RUN UNIT The transaction manager was unable to successfully establish a database session or associate it with a database session or associate it with a database transaction, due to an environmental condition such as short-on-storage.
18		The record has not been bound. A BIND statement must be issued before GET, OBTAIN, STORE, MODIFY, or FIND CALC functions can be executed. A probable cause of this error is that the record-name or record-location-variable being bound has a nonexistent or incorrect address. Consequently, the object record of the BIND statement has been bound to location 0. This problem can also occur with the BIND PROCEDURE and ACCEPT PROCEDURE statements. Note: A location address of 0 usually occurs when the location is included in the LINKAGE SECTION, but the required addressability has not been established.
	0318	FIND CALC The record was not bound before the FIND CALC was attempted.
	0518	GET The record was not bound before the GET was attempted. Note that this code is issued during the execution of the GET portion of the OBTAIN function.
	1218	STORE The record was not bound before the STORE was attempted.
	1418	BIND RECORD BIND PROCEDURE The BIND statement is attempting to bind incorrectly the record location or the procedure location to location 0.
	1518	ACCEPT IDMS STATISTICS ACCEPT PROCEDURE A BIND PROCEDURE has not been issued, or the database statistics location (for ACCEPT IDMS STATISTICS) or the procedure control location (for ACCEPT PROCEDURE) is 0.
	2018	Logical Record Facility Requests A path command has issued a FIND CALC for a database record that is not part of the logical record. Include the database record in the logical record.
19		The database transaction associated with the run unit was forced to back out. This error status generally occurs only when the run unit is sharing its transaction with another database session. Some action by another sharing database session caused the transaction to be backed out. After this condition is detected, the run unit is terminated and the program receives a 19 minor status code. This status code may be returned on any DML request other than a ROLLBACK
20		The current record of run unit is not the same type as the record named in the DML command.
	0220	ERASE The current record of run unit is not the same type as the named record. Probable causes for the return of this status code are: The object record has not been established as current of run unit. The record name specified is invalid or misspelled. A DML has altered run-unit currency just before the ERASE was issued.
	0520	GET The current record of run unit is not the same type as the named record. Probable causes for the return of this status code are: The object record has not been established as current of run unit. The record name specified is invalid or misspelled. A DML has altered run-unit currency just before the GET was issued.
	0820	MODIFY The current record of run unit is not the same type as the named record. Probable causes for the return of this status code are: The object record has not been established as current of run unit. The record name specified is invalid or misspelled. A DML has altered the current of run unit just before the MODIFY was issued.
21		Not all areas being updated have been readied in an UPDATE usage mode, or not all records, sets, and areas affected have been included in the subschema. The most probable cause is that the wrong subschema has been invoked, or that the subschema has been compiled incorrectly. If the object record is a member of a multi-member set, there are two additional probable causes for the return of this minor code: An area in which one of the other members resides has not been readied in one of the three update usage modes. One or more of the other members of a multi-member set have not been included in the subschema. When making updates to a member of a multi-member set, the subschema must contain all records and areas (readied for update) that are involved in the update of the set.
	0221	ERASE Not all areas being updated have been readied in an update usage mode, or not all records, sets, and areas affected have been included in the subschema.
	0721	CONNECT Not all areas being updated have been readied in an update usage mode, or not all records, sets, and areas affected have been included in the subschema.
	0821	MODIFY Not all areas being updated have been readied in an update usage mode, or not all records, sets, and areas affected have been included in the subschema. This status is returned only when the key from a sorted set is modified.
	1121	DISCONNECT Not all areas being updated have been readied in an update usage mode, or not all records, sets, and areas affected have been included in the subschema.
	1221	STORE Not all areas being updated have been readied in an update usage mode, or not all records, sets, and areas affected have been included in the subschema.
22		The named record is not currently a member of the named set.
	1122	DISCONNECT The named record is not currently a member of the named set. A probable cause for the return of this status code is that the program did not verify membership of the named record in the named set before issuing the DISCONNECT.
23		The named area is not in the subschema.
	0323	FIND/OBTAIN CURRENT FIND/OBTAIN WITHIN AREA The named area is not in the subschema.
	0623	KEEP The named area is not in the subschema.
	0923	READY The named area is not in the subschema.
	1523	ACCEPT DBKEY FROM AREA The named area is not in the subschema.
25		Currency has not been established for the object set.
	1225	STORE A set occurrence has not been established for each set in which the object record is defined as an automatic member, or a set occurrence has not been established for each set in which the object record is defined as a manual member and is stored VIA the set.
26		The record cannot be found, or no more duplicates exist for the object record.
	1726	RETURN The indexed entry requested cannot be found. The prior of set and next of set are maintained, and the current of set is set to null. A subsequent format 3 FIND/OBTAIN command specifying next of set or prior of set will be executed properly.
	0226	ERASE In the process of executing an ERASE ALL, PERMANENT, or SELECTIVE command, a broken chain was encountered. A broken chain is usually caused by improper recovery.
	0326	FIND/OBTAIN DBKEY FIND/OBTAIN CALC/DUPLICATE FIND/OBTAIN WITHIN SET USING SORT KEY The record requested cannot be found. This status code is returned only with formats 1, 5, and 6 of the FIND/OBTAIN statement. These formats use direct retrieval based on a key value. Note that this status code does not necessarily indicate an error condition; it is commonly used to check for CALC and sorted set duplicates. Probable causes for the return of this status code are: No record exists with the specified key. For a FIND/OBTAIN DUPLICATE command, no more duplicates exist for the object record. For a FIND/OBTAIN CALC command, the page range to which the record type is assigned has been changed since the record was stored. The object record has been removed by a previous ERASE command. For a FIND/OBTAIN DBKEY command, the record type to which the object record occurrence belongs is not included in the subschema. If format 6 has been specified and this status code is returned, the prior of set and next of set are maintained, and the current of set is set to null. A subsequent format 3 FIND/OBTAIN command specifying next of set or prior of set will be executed properly.
	0526	GET The object record has been erased. The probable cause for the return of this status code is that a GET command has been issued, but the record that was last made current of run unit has been erased.
	0626	KEEP The record to be kept has been erased. The probable cause for the return of this status code is that a KEEP CURRENT WITHIN SET command has been issued, but the record that was last made current of that set has been erased.
28		The run unit has attempted to ready an area that has already been readied.
	0928	READY READY has already been executed.
29		The run unit has attempted to place a lock on a record that was already locked by another run unit, and a wait would cause a deadlock. This run unit aborts. Subsequent requests by this run unit will result in: DLOK abort Nn69— The run unit must be bound by issuing another BIND RUN-UNIT statement.
30		An attempt has been made to erase the owner record of a nonempty set.
	0230	ERASE The unqualified form of the ERASE statement has been issued, but the record occurrence specified is the owner of a nonempty set occurrence. The probable cause for the return of this status code is that the program did not verify that all set occurrences owned by the record were empty before issuing the ERASE command.
31		The format of the retrieval statement conflicts with the record's location mode.
	0331	FIND/OBTAIN CALC FIND/OBTAIN CALC has been used to retrieve a record that does not have a CALC location mode.
		FIND/OBTAIN WITHIN SET USING SORT KEY FIND/OBTAIN WITHIN SET USING SORT KEY has been used to retrieve a record within a set that is not sorted.
32		An attempt to retrieve a duplicate of a CALC record was unsuccessful; the value of the CALC field in program variable storage does not equal the value of the CALC control element in the current record of record type.
	0332	FIND/OBTAIN DUPLICATE CALC-key values in program variable storage and in the current record of record type are not equal. The probable cause for the return of this status code is improper use of FIND/OBTAIN DUPLICATE. FIND/OBTAIN DUPLICATE can only be issued when the current record of record type has a CALC-key that matches the CALC-key contained in program variable storage.
33		One or more sets in which the record participates have not been included in the subschema, which caused the subschema compiler to establish access restrictions when the subschema was compiled.
	0233	ERASE All required sets have not been defined. The cause for the return of this status code is that one or more sets in which the object record participates, either as owner or member, have not been included in the subschema. Consequently, when the subschema was compiled, it established an access restriction that prohibits the use of ERASE with the object record.
	0833	MODIFY All required sets have not been defined. The cause for the return of this status code is that one or more sorted sets in which the record is defined as a member have not been included in the subschema. Consequently, when the subschema was compiled, it established an access restriction that prohibits the use of MODIFY with the object record.
	1233	STORE All required sets have not been defined. The cause for the return of this status code is that one or more sets in which the record is defined as an automatic member have not been included in the subschema. Consequently, when the subschema was compiled, it established an access restriction that prohibits the use of STORE with the object record.
37		The ERASE/PERMANENT/SELECTIVE/ALL could not be performed because there is a cyclical relationship between two or more of the records that would be erased.
	0237	ERASE PERMANENT/SELECTIVE/ALL MEMBERS The ERASE could not be executed because there is a cyclical relationship between two or more of the records that would be erased. This is an example of a cyclical set relationship: REC-A owns REC-B in the A-B set REC-B owns REC-C in the B-C set REC-C owns REC-A in the C-A set
39		SVC SEND/RECEIVE communications lost The current front-end has lost contact with the back-end. See the description of minor code 69 for potential causes of the loss of the communications. The DC log may contain more information about the reason for this loss.
40		The WHERE clause in an OBTAIN NEXT logical record request is inconsistent with a previous OBTAIN FIRST or OBTAIN NEXT command for the same logical record.
	2040	Logical Record Facility Requests The WHERE clause included in an OBTAIN NEXT statement has directed LRF to a different path than did the WHERE clause in the preceding request for the logical record. Either the WHERE clause is incorrect, or an OBTAIN FIRST statement should have been issued instead of an OBTAIN NEXT statement.
41		The subschema contains no path that matches the WHERE clause in a logical record request.
	2041	Logical Record Facility Requests LRF cannot match the request's WHERE clause to a path. This status code can also be returned if the program did not contain a WHERE clause and if the subschema does not specify an unqualified SELECT within the path group.
42		An error has occurred in processing a logical record path.
	2042	Logical Record Facility Requests An ON clause included in the path by the database administrator specifies the return of the LR-ERROR path status to the program.
43		Bad or inconsistent data is present in the logical record's variable-storage location, in the request's WHERE clause, or in the path's WHERE clause.
	0343	FIND/OBTAIN DBKEY FIND/OBTAIN CURRENT FIND/OBTAIN WITHIN SET/AREA FIND/OBTAIN OWNER FIND/OBTAIN CALC/DUPLICATE FIND/OBTAIN WITHIN SET USING SORT KEY A program check occurs during evaluation of a path's WHERE clause for one of two reasons: A WHERE clause has specified that a packed decimal field be compared to a field that is not packed, and that cannot be converted to packed because of the presence of nonnumeric data. In this case, specify a quoted literal for the field. Data in variable storage or in a database record does not conform to its description. A path status of LR-ERROR is returned to the program unless the database administrator has included an ON clause in the path to override this action.
	2043	Logical Record Facility Requests A program check occurs during evaluation of a request's WHERE clause for one of two reasons: A WHERE clause has specified that a packed decimal field be compared to a field that is not packed, and that cannot be converted to packed because of the presence of nonnumeric data. In this case, specify a quoted literal for the field. Data in variable storage or in a database record does not conform to its description. A path status of LR-ERROR is returned to the program unless the database administrator has included an ON clause in the path to override this action.
44		The WHERE clause in a logical record request does not supply a key element expected by the path.
	2044	Logical Record Facility Requests A CALC KEY, DBKEY, or SORT KEY specified in a FIND/OBTAIN path command and qualified by OF REQUEST is not specified correctly in the request's WHERE clause. To avoid this error condition, the database administrator should ensure that each OF REQUEST in the path has a corresponding FIELDNAME-EQ selector.
45		The value of a subscript in a WHERE clause in a logical record request is invalid.
	2045	Logical Record Facility Requests A program check occurs during the evaluation of a request's WHERE clause because a subscript value is less than 0 or greater than its maximum allowed value. A path status of LR-ERROR is returned to the program unless the database administrator has included an ON clause in the path to override this action.
46		An arithmetic program check occurs during the evaluation of a WHERE clause in a logical record request.
	2046	Logical Record Facility Requests A program check would occur during the evaluation of a request's WHERE clause for one of the following reasons: An arithmetic overflow has occurred (fixed point, decimal, or exponent). An arithmetic underflow has occurred (exponent). A divide exception has occurred (fixed point, decimal, or floating point). A significance exception has occurred. A path status of LR-ERROR is returned to the program unless the database administrator has included an ON clause in the path to override this action.
52		IDMS attempted to read an incomplete variable-length record.
	0352	In a system generated with RETRIEVAL NOLOCK, IDMS attempted to read an incomplete variable-length record; that is, it attempted to retrieve a variable-length record for which a STORE operation was still in progress.
53		The subschema definition of an indexed set does not match the indexed set's physical structure in the database. The most probable cause for the return of this minor code is that the subschema definition of an indexed set has been changed to conflict with the indexed set's physical structure in the database. Specifically, any of the following definitional changes result in the return of this minor code: Changing the set order of an indexed set from unsorted to sorted, or changing the set order from sorted to unsorted. Changing the indexed set's symbolic key COMPRESSION option. Changing the sorted set order of an indexed set from sorted by symbolic key to sorted by db-key, or from sorted by db-key to sorted by symbolic key. Changing the sorted set order of an indexed set from ascending to descending sequence, or from descending to ascending sequence. The minor code can be returned if a record on the database has been found to have a different length than defined within the subschema. When processing an SQL-defined database, the date-timestamp does not match the stamp in the access module.
54		Invalid record description (SR51) in subschema tables.
	1254	STORE The prefix length of an SR51 record is less than zero or the data length is less than or equal to zero.
55		An invalid length has been defined for a variable-length record.
	0555	GET An invalid length has been defined for a variable-length record. Note that this status code can be returned for the GET portion of the OBTAIN (that is, FIND/GET) command. Probable causes for the return of this status code are: The database has been restructured and the subschema invoked has not been recompiled to reflect the new database. The data length portion of the variable-length record has been defined as less than the control length portion. The sort key for a sorted record has been defined incorrectly either in the variable portion of the record or in the entire record.
	0855	MODIFY An invalid length has been defined for a variable-length record. Probable causes for the return of this status code are: The database has been restructured and the subschema invoked has not been recompiled to reflect the new database. The data length portion of the variable-length record has been defined as less than the control length portion. The sort key for a sorted record has been defined incorrectly either in the variable portion of the record or in the entire record.
	1255	STORE An invalid length has been defined for a variable-length record. Probable causes for the return of this status code are: The database has been restructured, and the subschema invoked has not been recompiled to reflect the new database. The data length portion of the variable-length record has been defined as less than the control length portion. The sort key for a sorted record has been defined incorrectly either in the variable portion of the record or in the entire record.
56		Insufficient memory is available to provide for the work areas needed by the IDMS compression/decompression routines.
	0356	Insufficient memory is available to provide for the work areas needed by the IDMSCOMP/IDMSDCOM routines; sufficient storage must be available to contain the decompressed record. Usually, this status code occurs only when running under the central version. If this error recurs, increase the size of the storage pool. In the case of CA IDMS Presspack, the error may be caused by a lack of compression, an incorrect control length, or an incorrect DCT.
57		A retrieval-only run-unit has detected an inconsistency in an index that should cause an 1143, 1144, or 1153 abend, but optional apar bits 216 and/or 242 have been turned on.
	0357	An OBTAIN or FIND command encountered an inconsistency within an index that would have normally generated an 1143, 1144, or 1153 abend, but optional apar bits 216 and/or 242 have been turned on. If the retrieval-only run-unit is being run within a CV and the CV has SYSGEN parameter RETRIEVAL NOLOCK specified a concurrent update run-unit may have made a change to the index that makes the retrieval run-unit believe the index has been corrupted. If the retrieval-only run-unit is being run in local mode a concurrent copy of IDMS may have updated the index making it appear as if the index has been corrupted. In either case, simply rerun the failing transaction. If the error persists or a CV is running with RETRIEVAL LOCK the error status should be treated as an 1143 abend and rerun with optional apar bit 216 turned off so a dump can be produced.
	1757	A RETURN verb encountered an inconsistency in an index that would have generated a 1143, 1144, or 1153 abend, but optional apar bits 216 and/or 242 have been turned on. If the retrieval-only run-unit is being run within a CV and the CV has SYSGEN parameter RETRIEVAL NOLOCK specified, a concurrent update run-unit may have made a change to the index that makes the retrieval run-unit believe the index has been corrupted. If the retrieval-only run-unit is being run in local mode, a concurrent copy of IDMS may have updated the index making it appear as if the index has been corrupted. In either case, simply rerun the failing transaction. If the error persists or a CV is running with RETRIEVAL LOCK the error status should be treated as an 1143 abend and rerun with optional apar bit 216 turned off so a dump can be produced.
58		An attempt was made to rollback updates in a local mode program. Updates made to an area during a local mode program's execution cannot be automatically rolled out. The area must be manually recovered.
	1958	A ROLLBACK CONTINUE was issued by a program running in local mode and records had been updated since the last checkpoint was encountered. The run-unit has been terminated and the related areas must be manually recovered.
60		A record occurrence has been encountered whose type is inconsistent with the set named in the ERROR SET field of the IDMS communications block. The return of this minor status code is triggered most often by a broken chain caused by improper recovery.
	0260	ERASE A record occurrence has been encountered whose type is inconsistent with the set named in the error set field of the IDMS communications block. An affected record occurrence has been found in the database, but its record type has not been defined in the subschema as a member or owner of the set. Probable causes for the return of this status code are: A broken chain exists in the database due to improper recovery. A new schema and associated subschemas describe an existing database improperly.
	0360	FIND/OBTAIN CURRENT FIND/OBTAIN WITHIN SET FIND/OBTAIN OWNER FIND/OBTAIN WITHIN SET USING SORT KEY A record occurrence has been encountered whose record type is not a member or owner of the set as it is defined in the subschema. Probable causes for the return of this status code are: A broken chain exists in the database due to improper recovery. A new schema and associated subschemas describe an existing database improperly.
	0860	MODIFY A record occurrence has been encountered whose type is inconsistent with the set named in the ERROR SET field of the IDMS communications block. The record being modified is a member of a sorted set, and the sort key has been changed as part of the modification. In the process of disconnecting and then reconnecting a record occurrence to replace it in the proper position in the set, the inconsistent record occurrence was encountered. Probable causes for the return of this status code are: A broken chain exists in the database due to improper recovery. A new schema and associated subschemas describe an existing database improperly.
	1260	STORE A record occurrence encountered in the process of connecting automatic sets is inconsistent with the set named in the ERROR SET field of the IDMS communications block. The record type of the occurrence is not defined as either owner or member in the set. Probable causes for the return of this status code are: A broken chain exists in the database due to improper recovery. A new schema and associated subschemas describe an existing database improperly.
61		No record can be found for a pointer db-key. A record pointer has a non-null db-key value, but no record having that db-key value can be found in the database. The probable cause for the return of this status code is that a broken chain exists in the database due to improper recovery.
63		The DBMS cannot interpret the DML function to be performed. Probable causes for the return of this status code are: A direct use of the CALL statement to perform a database operation, rather than one of the DML statements, has been made incorrectly. A PL/I program has not declared the IDMS interface as an Assembler module. The program must include the following statement: DECLARE IDMS ENTRY OPTIONS(INTER,ASM). An attempt has been made to run a utility through central version that must be run in local mode. An attempt has been made to perform an CA IDMS/DC function from a DC-BATCH program. The requested DC function is not supported in DC-BATCH. The only DC functions supported in DC-BATCH are: Accessing DC/UCF queues (GET/PUT/DELETE QUEUE) Creating DC/UCF reports (WRITE PRINTER/#PRINT)
	2063	Logical Record Facility Requests A logical record request's WHERE clause includes a keyword that is not 1 to 32 characters long. Another possible cause of the error is that selection expressions (PXEs) are missing from the Logical Record Communications Block (LRC). Module IDMSMOVE must be copied into the application program for PXE fields to be initialized correctly.
64		The CALC control element has not been described properly.
	0364	FIND/OBTAIN CALC The named record has been included in the subschema with a CALC location mode, but the CALC control element has not been included in the subschema view of the record.
	2064	Logical Record Facility Requests A path command has attempted to access a database record with CALC location mode, but the CALC control element has not been described properly in the subschema.
65		The database page read was not the page requested. The return of this minor code is associated most often with the following situation: a page read into the system buffers from disk contains first and last 4-byte positions that do not equal the page number requested. Probable causes for the return of this minor status code are: The page size specified in the DMCL does not agree with the actual page size specified for the file, for one of the following reasons: The page size has been specified incorrectly. The load or core-image library assignment has been specified incorrectly. An CA IDMS utility has been run to increase the page size of the area, but the DMCL has not been recompiled. The JCL has been specified incorrectly, with DD or DLBL statements pointing to the wrong file. The data on the requested page has been destroyed. Check for an I/O error or an update by a non-IDMS program or utility.
66		The area specified is not available in the requested usage mode. Probable causes for the return of this status code are: The area is being used by another program in a usage mode that conflicts with the usage mode requested by this program. The area update indicator lock has been left on after an abend.
	0966	READY The area specified is not available in the requested usage mode. If the 0966 status code is ignored, subsequent attempts to access the area will return an 01 or 09 minor code. Probable causes for the return of this status code are: If running in local mode, the area is locked against update. If running under the central version, either the area is offline to the central version, or an update usage mode was requested and the area is in retrieval mode to the central version.
67		The subschema invoked does not match the subschema object tables.
	1467	BIND RUN-UNIT The subschema specified on a BIND RUN UNIT is an invalid subschema load module, or the internal name in the subschema load module does not match the specified subschema name. Probable causes for the return of this status code are: The tables loaded are not subschema object tables. Libraries have been concatenated incorrectly. The name of the subschema load module does not match the name contained in the subschema tables, for one of the following reasons: The subschema was linked using an incorrect name. An attempt has been made to use an ALIAS through the z/OS linkage editor. This is not allowed for subschema tables. The subschema was added to the load area using an incorrect name.
68		The CICS interface (IDMSINTC) was not started. Probable causes for the return of this minor code are: IDMSINTC was not executed before the execution of a CICS task that issued IDMS requests. The CWA location containing the address of IDMSINTC has been overwritten by another CICS application.
69		The run unit has not been bound to the DBMS. Probable causes for the return of this minor code are: The proper BIND statement has not been issued. The DC/UCF system is not active or is not accepting new run units. The connection between the run unit and the DC/UCF system has been broken by exceeding the maximum wait time or by other factors, as noted on the DC/UCF log. An attempt has been made to sign on a run unit for a program that has not been registered with the DC/UCF system. The DC/UCF system under which the program is running requires program registration (as defined at system generation). The subschema control block has been reinitialized since the BIND RUN-UNIT was last issued. An nn29 or nn79 status has been encountered, but the program failed to check for these status values and to reissue the BIND RUN-UNIT. The DC/UCF system runtime messages that appear most commonly in conjunction with the nn69 status code are listed below. DC001002— The requested wait would have caused a deadlock on resources other than db-keys. DC001003— The waiting task exceeded the stall-time threshold. DC015001— Waiting for the storage requested would cause a deadlock.
	1469	BIND RUN-UNIT This status code indicates one of the following conditions: the central version is not active or is not accepting new run units; the program is not registered; or the run unit's connection to the central version has been broken because of a timeout or other factors, as noted on the DC/UCF log.
70		The file will not open properly. This minor code is returned when a file has not opened properly. For native VSAM files, check that the cluster was properly defined using IDCAMS and that the CONTROL INTERVAL CONTAINS clause was correctly specified in the DMCL. This error may also indicate insufficient storage for the VSAM control blocks to be loaded. This minor code is also returned when the page size assigned in the DMCL does not match the blocksize of the database file on disk.
	0370	FIND/OBTAIN DBKEY FIND/OBTAIN CURRENT FIND/OBTAIN WITHIN SET/AREA FIND/OBTAIN OWNER FIND/OBTAIN CALC/DUPLICATE FIND/OBTAIN WITHIN SET USING SORT KEY A database file will not open properly. The associated area has been readied, but the first attempt to access the file has triggered this status code.
	0970	READY A database file will not open properly. This status code is often returned as a result of an error in the JCL or the page size defined in the DMCL does not match the blocksize of the database file on disk.
	1470	BIND RUN-UNIT A journal file will not open. This status code occurs only when operating in local mode. If operating under z/OS, the most probable cause is that a DD statement for the journal file is missing in the JCL. Check the operating system message listing for the missing DD statement.
71		The page range/page group for the area being readied, or the page range/page group requested cannot be found in the DMCL. Probable causes for the return of this minor code are: The page range/page group requested, either implicitly or explicitly, will not map properly with the DMCL table provided. Check that all areas referenced by the run unit are defined in the specified DMCL tables. If the db-key specified does not map to any area known to the DMCL, the subschema and the DMCL are probably mismatched (or the db-key is bad). A new page range/page group for the data dictionary has been specified. In the process of reassembling and relinking the subschema macros, the starting and ending page specifications were changed. However, no corresponding changes have been made in the data dictionary DMCL macro (IDMSBASE) or in the DC/UCF system's global DMCL. The DMCL tables for the DC/UCF system have been recompiled; however, the system has not been shut down and restarted. Consequently, the DC/UCF system continues to operate with the obsolete DMCL tables.
	0971	READY The page range/page group for the area being readied could not be found in the DMCL. A probable cause for the return of this status code is that the area does not map to a page range/page group specified in the DMCL.
72		Insufficient memory is available for load or storage allocation. If operating under the central version, the return of this minor code usually indicates that the program pool, reentrant pool, or storage pool is too small. If running in local mode, this code indicates that the region/partition size for the application program is too small.
	nn72	Any DML function Insufficient memory is available for loading a database procedure. A minor code of 72 can be received for any verb if a database procedure is described in the schema. Database procedures that are not linked with the subschema are loaded when needed. The probable causes for the return of a minor code of 72 vary, depending on whether the run unit is running under the central version or in local mode, and depending on the operating system on which the run unit is executing. When running under the central version, probable causes for this status code are: The program pool or reentrant pool is too small to allow for loading a database procedure for the run unit. If using z/VSE, the DC/UCF system has attempted to load a database procedure that has been deleted from a core-image library, without condensing the library. The entry in the library's directory for the deleted module contains invalid size information. When running in local mode, probable causes for this status code are: The program's region/partition is too small to allow for loading a database procedure for the run unit. If using z/VSE, the DC/UCF system has attempted to load a database procedure that has been deleted from a core-image library, without condensing the library. The entry in the library's directory for the deleted module contains invalid size information.
	1472	BIND There is not enough storage available to load the subschema load module. The probable causes for the return of this status code vary, depending on whether the run unit is running under the central version or in local mode, and depending on the operating system on which the run unit is executing. When running under the central version, probable causes for this status code are: Insufficient storage to load necessary modules The program pool or reentrant pool is too small to allow for loading of the run unit's subschema. The storage pool is too small to allow for the allocation of the variable subschema tables (VB50). If using z/VSE, the DC/UCF system has attempted to load a subschema that has been deleted from a core-image library, without condensing the library. The entry in the library's directory for the deleted module contains invalid size information.
		When running in local mode, probable causes for this code are: Insufficient storage to load necessary modules The program's region/partition is too small to allow for allocation of the runtime storage areas. Runtime storage must accommodate the variable subschema tables (VB50), that database buffers and the journal buffer as defined in the DMCL, and VSAM control blocks (if IDMS VSAM or native VSAM databases are used). z/VSE— IDMS has attempted to load a module (either system runtime or user runtime) that has been deleted from a core-image library, without condensing the library. The entry in the library's directory for the deleted module contains invalid size information.
	2072	Logical Record Facility Requests Storage is not available for the work areas required to evaluate the logical record request's WHERE clause.
73		A new central version run unit would exceed the MAXERUS value, as specified at system generation.
	1473	BIND RUN-UNIT A run unit has attempted to sign on; if it had signed on, the MAXERUS value would have been exceeded, resulting in a run-unit failure. The DC/UCF system is unable to accept a new run unit until an existing run unit terminates.
74		The dynamic load of a module has failed. An attempt to load a module from the load/core-image library or from the DDLDCLOD area has failed. Probable causes for this code are: The module is not in the library. A program definition element (PDE) that the DC/UCF system can assign to the module does not exist. An I/O error has occurred during the load of the module from the library.
	nn74	Any DML verb An attempt to load a database procedure from the load/core-image library has failed. A minor code of 74 can be received for any verb from the application program if a database procedure is associated with that verb, as described in the schema. Database procedures that are not linked with the subschema are loaded when needed. The probable causes for the return of a minor code of 74 vary depending on whether the run unit is running under the central version or in local mode, and depending on the operating system under which the run unit is executing.
		When running under the central version, probable causes for this status code are: A database procedure cannot be found in the CDMSLIB load library or in CDMSLnnn if DCUF TEST is in use (z/OS systems), or in the core-image library assigned to the IDMS-DC/UCF partition (z/VSE systems). The database procedure is not defined as a program in the SYSGEN for the system, and no null program definition elements (null PDEs) are available to the DC/UCF system for use by the procedure. This has occurred either because the Undefined Program Count in the SYSGEN defaulted to zero, or because the null PDEs specified for ALL have been allocated previously to other modules. A database procedure that has been loaded by the DC/UCF system at least once has been deleted from the library where it was previously found, and a VARY SUBSCHEMA NEW COPY command (or DCMT VARY PROGRAM NEW COPY command) has not been issued. This command instructs the DC/UCF system to perform its library search for the database procedure again. An I/O error occurred while the database procedure was being read into memory from the load/core-image library. This is a result of either a physical I/O error on disk or from an incomplete load module/core-image phase due to an unsuccessful link edit of the module.
		When running in local mode and under z/OS, this status code is not returned to the application program. The operating system will abend the program with a system abend code of 806, indicating that the operating system cannot locate the database procedure requested by the CA IDMS runtime system. If a CDMSLIB DD statement was present, then CA IDMS requested that the database procedure be loaded from that library. Otherwise, the load was attempted from the STEPLIB/JOBLIB specified in the job's JCL. When running in local mode, probable causes for this status code are: If using z/VSE, the database procedure could not be found in the core-image library assigned to the partition. An I/O error occurred while the database procedure was being read into memory from the load/core-image library. This is a result of either a physical I/O error on disk or from an incomplete load module/core-image phase due to an unsuccessful link edit of the module.
	1474	BIND An attempt to load a module from the load/core-image library or DDLDCLOD has failed. The probable causes for the return of this status code vary, depending on whether the run unit is running under the central version or in local mode, and depending on the operating system on which the run unit is executing. When running under the central version, probable causes for this status are: The subschema cannot be found in the DDLDCLOD area (for all operating systems) or in the CDMSLIB load library or CDMSLnnn if DCUF TEST is in use (z/OS systems), or in the core-image library assigned to the DC/UCF partition (z/VSE systems). The subschema is not defined as a program in the SYSGEN for the system, and no null program definition elements (null PDEs) are available to the DC/UCF system for use by the module. This has occurred either because the Undefined Program Count in the SYSGEN defaulted to zero for ALL or for SUBSCHEMAS, or because the null PDEs specified for ALL or for SUBSCHEMAS have been allocated previously to other modules. A subschema that has been loaded by the DC/UCF system at least once has been deleted from the DDLDCLOD area or from the library where it was previously found, and a VARY SUBSCHEMA NEW COPY command (or DCMT VARY PROGRAM NEW COPY command) has not been issued. This command instructs the DC/UCF system to perform its library search for the module again.
		The subschema name provided is binary zeros. If the SUBSCHEMA-SSNAME field is copied into an application program such that the field has no initial value (for example, COBOL LINKAGE SECTION), the program must move the name of the subschema to this field before issuing the BIND RUN-UNIT verb or copying SUBSCHEMA-NAMES into WORKING-STORAGE. An I/O error has occurred while the module was being read into memory from the load/core-image library. This is a result of either a physical I/O error on disk or an incomplete load module/core-image phase due to an unsuccessful link edit of the module. Note: If running the program in a multi-database/multi-dictionary environment and/or in a DDS environment, the name of the subschema specified by the application program may have been changed by the subschema mapping specifications found in the database name table. Using an incorrect database name table can result in this error status. When running in local mode and under z/OS, this status code is not returned to the application program. The operating system will abend the program with a system abend code of 806, indicating that the operating system cannot locate the module requested by the IDMS runtime system. If a CDMSLIB DD statement was present, then CA IDMS requested that the module be loaded from that library. Otherwise, the load was attempted from the STEPLIB/JOBLIB specified in the job's JCL. Note that loading Note that in local mode, loading modules from the DDLDCLOD area is not supported.
		When running in local mode, probable causes for the return of this status code are: If using z/VSE, CA IDMS runtime modules or user runtime modules could not be found in the core-image library assigned to the local program's partition. An I/O error occurred while the module was being read into memory from the load/core-image library. This is a result of either a physical I/O error on disk or an incomplete load module/core-image phase due to an unsuccessful link edit of the module. Note: If running the program in a multi-database/multi-dictionary environment, the name of the subschema specified by the application program may have been changed by the subschema mapping specifications found in the database name table associated with the DMCL.
75		A read error has occurred. Probable causes for the return of this status code are: A file assignment has been specified incorrectly in the JCL. A physical I/O error has occurred. This is a hardware error. The disk journal files or database files have not been initialized. An insufficient buffer size has been specified in the DMCL. If operating under z/VSE, SD rather than DA has been specified for the DLBL file type. An unexpected return code from VSAM has been received.
76		A write error has occurred. Probable causes for the return of this status code are: A file assignment has been specified incorrectly in the JCL. A physical I/O error has occurred. This is a hardware error. An unexpected return code from VSAM has been received. The READ ONLY switch has been set on the disk drive after a file was opened.
77		The run unit has not been bound or has been bound twice. This minor code is returned only to IDMS-DC programs. Probable causes for the return of this status code are: Another DML statement has been issued before the required initial BIND RUN-UNIT statement. BIND RUN-UNIT must be the first functional call issued to CA IDMS. More than one BIND RUN-UNIT statement has been issued. The second and subsequent BIND RUN-UNIT statements will fail. No BIND RUN-UNIT statement was issued after a FINISH or a ROLLBACK.
	1477	BIND RUN-UNIT The run unit has been bound previously.
78		An area wait deadlock has occurred.
	0978	READY AREA To wait for an area would cause a deadlock. It is recommended that all areas be readied either before issuing the first functional call or that all programs ready areas in the same order.
80		The target node is not active or has been disconnected.
	1480	BIND RUN-UNIT Probable causes for the return of this status code are: The node specified through the BIND RUN-UNIT statement is not active or has been disconnected. Note that the node may have been specified explicitly in the BIND RUN-UNIT statement, or may have been derived from IDMSOPTI, SYSCTL, or from the database name table. The node name specified in the BIND RUN-UNIT statement was misspelled.
81		The database name specified is not known.
	1481	BIND RUN-UNIT The specified subschema must be an entry in the database name table. The dbname specified matches an entry in the database name table that was defined with subschema mapping mandatory.
82		The subschema is not allowed under the specified database.
	1482	BIND RUN-UNIT The subschema name specified in the BIND RUN-UNIT statement cannot be located in the database name table, and the specified database has been defined with the ALWAYS option.
83		An error has been made in the use of native VSAM data sets. A native VSAM error has occurred during an attempt to access a native VSAM data set. This minor code usually results from a VSAM I/O error and is issued in conjunction with system runtime error message 205006.
84		READY or any DML command immediately issued after a READY. The threshold for the number of tries to lock an area has been exceeded. Either increase the RETRY count of the SYSGEN AREA ACQUISITION parameter or set it to FOREVER. Attempting to execute the run-unit when there are fewer conflicting run-units may also avoid the problem.
	0184 0284 0384 0584 0684 0784 0884 0984 1184 1284 1584 1684 1784	The threshold for number of tries to lock an area has been exceeded.
86		Any DML command. An attempt to lock a dbkey would have required a wait but NOWAIT was requested.
87		An update violation has occurred. The update operation was not performed. The owner and member records for an updated set are not in the same page group or do not have the same dbkey radix.
91		BIND RUN-UNIT
	1491	There must be a DBNAME established before issuing a BIND RUN UNIT to the specified subschema.
92		BIND RUN-UNIT
	1492	The subschema specified does not contain at least one logical area that maps to a physical area when using the dbname specified.
93		BIND RUN-UNIT
	1493	The subschema specified contains a symbolic value for the area name specified. The symbolic value does not match a corresponding symbolic value in the DMCL.
94		BIND RUN-UNIT
	1494	The dbname specified does not match any dbname defined in the database name table or any segment defined in the DMCL. This status also results if a dbname defined in the database name table is invalid.
95		BIND RUN-UNIT
	1495	The specified subschema must be defined in the default section of the database name table when a bind is issued with the specified dbname.