Return Code 94 - GENERAL ERROR INDICATOR

CA Datacom/DB Return Codes › Return Codes › Return Code 94 - GENERAL ERROR INDICATOR

Return Code 94 - GENERAL ERROR INDICATOR

Reason:

This is a general error number.

Action:

See the specific message based upon the internal return code. See the following internal return codes for details.

Return Code 94 Internal Return Codes

Dec	Hex	M	B	Reason	Action
001	01	Y	N	WORK AREA LENGTH ERROR	Your work area length does not match the length of the elements in your element list. Correct your work area length and rerun.
002	02	S	N	INTERNAL COMMAND MODIFIER FIELD ERROR	Collect the PXX dump of the condition and contact CA Support. For information about contacting CA Support, see Troubleshooting.
003	03	N	N	DL1T INTEGRITY LOAD FAILURE	Ensure the Multi-User Facility library concatenation contains DLCV1PR, DLSERV, DLSERVH, and DLSERVZ.
004	04	N	N	SPARSE INDEX ROUTINE NOT FOUND	Ensure the Multi-User Facility library concatenation contains the sparse index routine.
005	05	N	N	NO TABLE MATCH IN FAT FOR DBID The FAT-TAT database does not contain a FAT for the requested table in the requested DBID.	Verify the accuracy of the table name and DBID in the Request Qualification Area (RQA). If both are correct, run the Preprocessor with the corresponding DBD to create the missing FAT for the requested table and DBID.
006	06	N	N	FAT DIRECTORY IS FULL	Enlarge the FAT directory area by increasing FATDIR= value in the DLCVTPR macro and reassembling.
007	07	N	N	NO FAT FOUND WITH DBID MATCH The FAT-TAT database does not contain a FAT with the requested DBID.	Verify the accuracy of the DBID in the Request Qualification Area (RQA). If correct, run the Preprocessor with the corresponding DBD to create the missing FAT.
008	08	N	N	SPARSE INDX RTN DIRECTORY FULL	Increase the EXTNO= value in DLCV1PR macro and reassemble.
009	09	N	N	SECONDARY INDX ADD NOT ALLOWED You are attempting to insert a segment in a secondary index database, but this is not allowed in native DL/I.	Correct the program.
010	0A	N	N	SECONDARY INDEX PROT VIOLATED You attempted to update data that is not updatable.	Correct the program.
011	0B	N	N	TARGET KEY CHANGE NOT ALLOWED You attempted a target key change, but this is not allowed.	Correct the program.
012	0C	N	N	CONTROL DATA UPDAT NOT ALLOWED You attempted to update CA Datacom DL1 Transparency control data, but this is not allowed.	Correct the program.
013	0D	N	N	PREFIX ON ADDIT IS NOT LOW VALUES	Correct the program so that the adds are done with a prefix of low values.
014	0E	N	N	VARIABLE LENGTH FIELD INVALID The length of the LL field of a variable length segment is either greater than the maximum length specified in the DBD or less than the minimum length specified in the DBD.	Correct the program to insert the variable length segment with a length field.
015	0F	N	N	LCHLD LPCK CHANGE NOT ALLOWED	Correct the replace request.
016	10	N	N	DELETE RULE VIOLATION A violation of the DL/I delete rule was detected.	Correct the program as you would in the native environment.
017	11	N	N	INSERT RULE VIOLATION A violation of the DL/I insert rule was detected.	Correct the program as you would in the native environment.
018	12	N	N	CANNOT OPEN DUE TO CHECK PENDING You attempted to open a table in check status.	Run the DBUTLTY CONFIRM function against the table you are trying to open. See SQL code -166 - TBL authid.tblname CHECK PENDING.
019	13	N	N	TRYING TO RUN SU WITH CONSTRAINTS	Run with Multi-User Facility, not Single User.
020	14	N	N	CONFIRMING AND ALREADY CONFIRMED You specified a table that does not exist or has no constraints.	No action required. The table does not need to be confirmed. See SQL code -251 on 251 - TABLE HAS NO CONSTRAINTS and 252 - TABLE NOT IN A CHECK STATE.
021	15	N	N	CONFIRMING AND EXCEPTION TBL PROBLEM You specified an exception table that does not exist.	Either change the exception table name or first use the CREATE TABLE statement to create the exception table. The exception table definition must match the table being confirmed. See SQL code -250 on 250 - EXCEPTION TABLE authid.tblname NOT FOUND.
22	16	N	N	You attempted to update a row in a partitioned table. This update caused the partition value to change, so that the row now belongs in a different partition, and the table is defined with Move to New Partition as NO.	Updates which move a row to a different partition are not allowed if Move to New Partition is NO. If you want to be able to move rows with an update from one partition to another, set Move to New Partition as YES in the CA Datacom Datadictionary table definition. Note the documented cautions, if you choose to define a table with Move to New Partition as YES.
023	17	N	N	TABLE CONFIRMED BUT WITH EXCEPTIONS You attempted to ADD a foreign key reference or a domain constraint, but the rows of the table violated the constraint.	Delete the data in violation or drop the constraint(s) violated. Rows which are in error may be found in the exception table. See SQL code 170 - NO ROW FOUND.
024	18	N	N	TABLE NOT CONFIRMED DUE TO DEPEND An attempt to access a table in check-related state with a foreign key reference to a table has been rejected because the table is in a check state. Access is denied to the referencing table because foreign key values may have been deleted from the referenced tables in a check state.	Confirm the parent table(s) first. Take the table being opened out of check-related state. If the table being confirmed references a table in a check state, the confirm process is aborted because subsequent confirmation of the referenced tables may delete foreign key references. Therefore, you must confirm a chain of related tables in "top down"sequence. See SQL code -249 on 249 - REFERENCED TABLE aaa.ttt PLUS n OTHERS IN CHECK STATUS.
025	19	S	N	RDMXX COMMAND MODIFIER FIELD ERROR	Contact CA Support. For information about contacting CA Support, see Troubleshooting.
026	1A	S	N	LOCKT WORK AREA INVALID VALUE	Contact CA Support. For information about contacting CA Support, see Troubleshooting.
027	1B	Y	Y	DB SQL ACTIVE DD ML-CXX NO MATCH	With the SQL option selected, the CA Datacom Datadictionary database ID in the MUF startup option DICTIONARY does not match the Directory (CXX).
028	1C	Y	Y	DB SQL ACTIVE DDD ML-CXX NO MATCH	With the SQL option selected, the CA Datacom Datadictionary Data Definition Directory database ID in the MUF startup option DICTIONARY does not match the Directory (CXX).
029	1D	S	N	MAXIMUM ELEMENTS PER REQ. EXCEEDED	More elements were specified than allowed with the value specified for the MUF startup option MAXELRQ.
030	1E	Y	N	NULL VALUE INDICATOR IS NOT VALID Note: To assist in user application debugging, the specific field found to be invalid is identified in the Request Area for the ADDIT or UPDAT being done. From the start of the Request Area, an offset of 26 (x'1a') contains a 2-byte field length and a 2-byte displacement of the field within the record. The Request Area also has returned at offset 30 (x'1e') a 2-byte displacement of the offending data within the Work Area. This points to the null indicator.	An ADDIT or UPDAT is providing a column that can contain null values within the Element List, but the value provided for the null indicator is not N or a blank.
031	1F	N	N	You attempted to delete or update a referenced primary key value, or you attempted to add an invalid foreign key value.	The 18-character name of the violated constraint starts at the RQA feedback field of the Request Area. Add primary keys before adding foreign keys that reference them. Delete all foreign keys before deleting the primary key they reference. See SQL codes -175 on -175 - FOREIGN KEY <authid.constraintname> REFERENCE VIOLATION and -176 on -176 - FOREIGN KEY <authid.constraintname> VALUE VIOLATION.
032	20	N	N	You attempted to load CA Datacom DL1 Transparency for constraint processing, but the module could not be found.	Correct the Multi-User Facility library concatenation.
034	22	N	N	Your attempt to delete or update a referenced primary or unique key value was rejected because the referencing table is in check state.	Run the CONFIRM function of DBUTLTY to take the referencing table out of check state. See SQL code -262 on -262 - REFERENCING TABLE xxx.xxx IN CHECK-RELATED STATE.
035	23	N	N	You attempted to add or update a row which would violate a domain constraint.	The 18-character name of the violated constraint starts at the RQA feedback field of the Request Area. You may query the SYSADM.SYSCONSTRSRC table to see the WHERE clause of the domain constraint. You must modify your row so that it satisfies that WHERE clause. See SQL code -167 on -167 - DOMAIN CONSTRAINT nnnnnnnn.mmmmmmmm VIOLATION.
036	24	N	N	You are trying to catalog a table used by a plan executing or precompiling.	Take appropriate action relative to your particular situation.
037	25	N	N	INTERNAL ERROR	Collect the dump and contact CA Support. For information about contacting CA Support, see Troubleshooting.
038	26	N	N	The relative record number you specified is 0 or greater than 268,000,000.	Specify a valid relative record number.
039	27	N	N	If the UPDAT request were honored, the relative record number key would be updated.	Make sure the relative record number key is not changed by an UPDAT.
040	28	Y	N	The relative record number you provided is not within the area's extents.	Either extend the area or specify a smaller relative record number.
041	29	Y	Y	You attempted to add a record whose relative record number key already exists in this table.	Insure that the application is structured in such a way that when a row is added to a table with relative record number keys the key is unique.
042	2A	N	N	NOTWIN occurrence already exists.	Correct the program to not insert duplicates.
043	2B	N	N	Unable to load compression routine, probable user error.	Run CXX report to get the name of the comparison routine for the table. Make the routine available to the DB System causing this return code.
044	2C	N	N	The command coded is invalid with the relative record key.	Specify a different key name.
045	2D	N	N	A field with the no change option would be changed by this UPDAT. Note: To assist in user application debugging, the specific field found to be invalid is identified in the Request Area for the ADDIT or UPDAT being done. From the start of the Request Area, an offset of 26 (x'1a') contains a 2-byte field length and a 2-byte displacement of the field within the record.	Assure that the field is not changed.
048	30	N	N	Invalid data provided for data type. Note: To assist in user application debugging, the specific field found to be invalid is identified in the Request Area for the ADDIT or UPDAT being done. From the start of the Request Area, an offset of 26 (x'1a') contains a 2-byte field length and a 2-byte displacement of the field within the record.	Change input data to match data type.
049	31	N	N	Field not included in the elements during an ADDIT and no default was specified. To assist in user application debugging, the specific field found to be invalid is identified in the Request Area for the ADDIT or UPDAT being done. From the start of the Request Area, an offset of 26 (x'1a') contains a 2-byte field length and a 2-byte displacement of the field within the record.	Include the field in the elements while doing an ADDIT.
050	32	N	N	Bad return code from GETFLD.	Contact CA Support. For information about contacting CA Support, see Troubleshooting.
051	33	N	N	Bad return code from GETFLD.	Contact CA Support. For information about contacting CA Support, see Troubleshooting.
052	34	N	N	Bad return code from GETFLD.	Contact CA Support. For information about contacting CA Support, see Troubleshooting.
053	35	N	N	Bad return code from GETFLD.	Contact CA Support. For information about contacting CA Support, see Troubleshooting.
054	36	Y	Y	DL1T SEG. W/EQUAL LOGICAL TWIN IN PARENT The call is not completed because a segment with an equal logical twin sequence field exists for the parent.	Correct the program to not insert duplicates on the logical twin chain.
055	37	N	N	SEQUENTIAL COMMAND (Gaaaa) WITH MULTIPLE TASKS In CA Datacom CICS Services or any use of the extended options entry with multiple tasks, the Gaaaa commands (such as GETIT and GETPS) are not allowed.	Remove these commands from the application.
056	38	Y	Y	INDEX ERROR DURING SEQUENTIAL PROCESSING If a next-type command (such as LOCNX or REDNX) caused this error, it could be because you did not provide the Request Area's reserved fields intact from the previous command.	If you did not provide the Request Area's reserved fields intact from the previous command and a NEXT-TYPE command caused this error, correct the condition by providing those fields intact. Otherwise, contact CA Support. For information about contacting CA Support, see Troubleshooting.
058	3A	S	N	DYNAMIC TABLES INVALID COMMAND Dynamic system tables have many restrictions on supported commands. An invalid command is being presented.	Collect all documentation and contact CA Support. For information about contacting CA Support, see Troubleshooting.
059	3B	N	N	MUFPLEX OPEN WITH 'ACCESS NOOPT' An open for a base is being attempted where the Multi-User Facility is running as part of a MUFplex, but ACCESS NOOPT was specified for this base.	This condition is not supported. This base cannot be opened until the Multi-User Facility is recycled either with ACCESS OPTIMIZE specified or defaulted or with MUFplex turned off.
060	3C	N	N	An attempt was made to add a row that contains a value outside the range of values in a table partition or to update the value in a row so that the row can no longer reside in the partition.	Perform one of the following: Change the program so that it accesses the Full Parent table. If adding a record, add it to the correct table partition. If updating a record, delete the record from the current table partition and add it to the new correct table partition.
062	3E	N	N	Either an attempt was made to execute an ADDIT command using the Any Parent table, and it belongs in an area which is ACCESS OFF, UTLTY, or READ, or an attempt was made to execute an UPDAT command through the Any Parent table (which changes the partitioning criteria), and the new partition area has ACCESS OFF, UTLTY, or READ.	This is an error that the program needs to handle in its use of the Any Parent.
063	3F	N	N	An open of a partitioned table or any of the partitions was attempted against a database defined with the MUF startup option ACCESS NOOPT.	Change the MUF startup option ACCESS setting to OPTIMIZE.
064	40	N	N	SYSTEM AREA NOT URI A Multi-User Facility open is being attempted for an area that is considered part of the system that is either not loaded in the URI format, or is not virtual and has not been initialized. All system areas must be loaded in the URI format, and we therefore highly recommended that all areas be loaded in this format.	Back up and load the failing area with the defaulted URI=YES option of the DBUTLTY LOAD function. A non-virtual area must be initialized and loaded before it can be successfully opened.
065	41	N	N	An OPEN of a table is being attempted using a User Requirements Table with RRS=YES, but the table is in an area loaded with URI=NO. All areas accessed using a User Requirements Table with RRS=YES must be loaded in the URI format (we highly recommended that all areas be loaded in the URI format).	After ensuring that all applications using the area are URI-compliant, back up and load the failing area with the defaulted URI=YES option of the DBUTLTY LOAD function.
066	42	Y	Y	DATA CONTROL BLOCK ENDING INVALID The last block of data area contains invalid information. This can only occur when using the DBUTLTY CXXMAINT ALTER OPTION2=areaev function to enable a control block at the end of loaded data areas.	There is a probable JCL error with missing extents from what was initialized or extended. The edit in the Multi-User Facility can be removed during an open by specifying the startup option DIAGOPTION 8,64,OFF that turns off all extent read validation. Or you can use the DBUTLTY CXXMAINT ALTER OPTION2=areaev function to control the use of data area data set extent validation (see the CA Datacom/DB DBUTLTY Reference Guide).
067	43	N	N	You attempted to run a job using XCF to communicate with the Multi-User Facility using a User Requirements Table with RRS=YES, but the Remote Resource Manager (RRM) specified in the RRMNAME= parameter in the DBSIDPR module (assembled by the DBSYSID macro) is not currently enabled.	Submit RRM and rerun the job.
068	44	N	N	You attempted to run a job using XCF to communicate with the Multi-User Facility using a User Requirements Table with RRS=YES, but your SID does not have a RRMNAME= parameter coded.	The Remote Resource Manager (RRM) is required when using XCF and RRS. Either code RRS=NO in the User Requirements Table, or code the RRMNAME= parameter in the SID.
069	45	N	N	The data space of the Remote Resource Manager (RRM) is full.	Check the WXX (RRM log) size for a reasonable value, since the data space size is allocated based on the WXX size. If the size of the WXX is reasonable, contact CA Support.
070	46	N	N	You are executing the DBULTY DEFRAG function against a DBID which already has DEFRAG running against it.	Wait until the currently executing DEFRAG function completes against this DBID.
071	47	N	N	The DXX for this DBID is unusable due to a write I/O error encountered while running the DBUTLTY DEFRAG function.	Close the DBID, ensure that the cause of the I/O error has been corrected, and open the DBID for update.
072	48	N	N	You are trying to run the DBUTLTY DEFRAG function against a DBID which currently has or recently had old entry point users, that is, entry points other than DBNTRY. DEFRAG and old entry point programs are incompatible.	If you want to run DEFRAG against a DBID that is used by old entry point programs, you must do the following: Wait for all old entry point programs to complete. When all old entry point programs have completed, close the DBID in the MUF. When the DBID in the MUF is closed you can run DEFRAG provided no new program accesses the DBID using an old entry point.
073	49	N	N	You are trying to run the DBUTLTY DEFRAG function against a Multi-User Facility that is in a MUFplex environment in which more than one Multi-User Facility is enabled.	Running DEFRAG with more than one MUF enabled in a MUFplex environment is not permitted. Therefore, correct this error and then run DEFRAG again, or do not attempt to run DEFRAG in that environmental configuration.
074	4A	N	N	This return code was generated because logging is set to NO for a table specified in the DBUTLTY OLREORG function.	ddb>Ensure that logging is set to YES (specified with the LOGOPTION MUF startup option) for tables specified in the OLREORG function. For more information about the LOGOPTION MUF startup option, see the CA Datacom/DB Database and System Administration Guide.
075	4B	N	N	You received this message because you attempted to run either the OLREORG function of DBUTLTY or the REFGROUP report against a relative record table.	Do not run OLREORG or a REFGROUP report against a relative record table.
076	4C	N	N	Internal processing that moves rows uses this return code, but it should never be seen in a user application or request, nor should it be reflected in external return code counts.	If a user application or requests receives this return code, contact CA Support. For information about contacting CA Support, see Troubleshooting.
077	4D	N	N	You received this message because you attempted to run either the OLREORG function of DBUTLTY or the REFGROUP report against an area that uses clustering for its space management option.	Do not run the OLREORG function or run a REFGROUP report against an area that uses clustering (space management option 3). For more information on clustering and space management options, see the CA Datacom/DB Database and System Administration Guide.
078	4E	N	N	You received this message because you attempted to execute either the OLREORG function of DBUTLTY or a REFGROUP report using a partition parent as a table name. This is not allowed because partitions cross multiple areas.	Do not attempt to execute the OLREORG function or the REFGROUP report using a partition parent as a table name.
080	50	N	N	Physical pair cannot be found.	During a replace or delete, the physical pair of a logical child was not found. Contact CA Support for CA Datacom DL1 Transparency. For information about contacting CA Support, see Troubleshooting.
081	51	Y	N	DL1T NOT IN STARTUP An attempt is being made to open a table which requires CA Datacom DL1 Transparency for integrity checking, but DL1T was not specified in the MUF startup option DATACOM.	Add DL1T to the MUF startup option DATACOM, restart the Multi-User Facility, and retry your request.
082	52	Y	N	PRESSPACK NOT IN STARTUP An attempt is being made to open a table which requires CA Datacom Presspack as a compression routine, but PRESSPACK was not specified in the MUF startup option DATACOM.	Add PRESSPACK to the MUF startup option DATACOM, restart the MUF, and retry your request.
085	55	N	N	INCOMPLETE ROLL BACK The logical unit of work cannot be completely rolled back due to a forced spill point.	Specify the MUF startup option RXXROLLBACK YES, use more frequent checkpoints in your program, or make the Log Area larger to avoid this condition in the future.
086	56	Y	Y	INVALID DATACOM RECORD ID An invalid record ID was passed in the Request Area during the REDLE or the REDID command.	Assure that the program did not modify the record ID which was previously passed from CA Datacom/DB.
087	57	N	N	NOMAINT OPTION IS IN FORCE The NOMAINT parameter was set with the ACCESS DBUTLTY command, console command, or MUF startup option and maintenance commands, including RAAT ADDIT, UPDAT, or DELET, as well as an SQL INSERT, UPDATE, or DELETE statement, are not permitted. No distinction is made whether the caller has issued no prior maintenance commands, or millions. The feature is a simple way to stop maintenance without closing URTs. The ACCESS option does not prevent URT opens or closes and does not prevent proper execution of transaction backout (ROLLBACK) or backward recovery.	Determine why maintenance commands for the subject database are not permitted and if your request is an exception. If appropriate, issue the ACCESS DBUTLTY command, console command, or MUF startup option with a MAINT parameter.
088	58	N	N	DYNAMIC SYSTEM TABLE DATA ERROR There was invalid data associated with a request for maintenance to a Dynamic System Table. The error should be obvious but could be any of the following: Either the value specified for MUF_NAME does not match the mufname specified in the MUF Multi-User startup option, or if the MUF Multi-User startup option is not present, MUF_NAME does not match the Job Entry Subsystems (JES) job name. An attempt was made to add a generic entry to COVERED or VIRTUAL when one already existed. An attempt was made to make virtual a database that is currently open. An attempt was made to delete a virtual database that has open users. An update of a field tried to place an invalid value in that field, for example a zero in a field that must be larger than zero or test in a field which must contain yes or no.	Review the data being inserted or updated against the special rules in the CA Datacom/DB System Tables Reference Guide, then retry the request with the correct data when appropriate. Alternately, accomplish your goal in some other fashion than by doing maintenance to the Dynamic System Tables.
089	59	S	N	DYNAMIC SYSTEM TABLE FACILITY N-GEN Required facility was not generated for maintenance through the Dynamic System Tables. One of the following occurred. See the corresponding action. An insert of an area is being attempted to be covered or virtual, but the Multi-User Facility was not enabled with Memory Resident Data Facility (MRDF) support. An insert of an Accounting table is being attempted but the Multi-User Facility was not enabled with Accounting Facility support.	See the CA Datacom/DB Database and System Administration Guide for information about the MUF startup options, and before you next enable the Multi-User Facility note the following requirements related to the corresponding reason above. At least one COVERED or VIRTUAL startup option is required to generate MRDF and allow later changes to the MRDF areas. The ACCT and ACCTPRM startup options are required to allow you to add an Accounting Facility table later.
090	5A	N	N	DYNAMIC SYSTEM TABLE CO/VI CONFLICT There was an attempt to add a covered or virtual definition for a database which already has the other. That is, an insert of an area to be virtual or covered is being attempted into a database which is not of the same type.	Review your desired result. The action you are attempting is not possible. A database must be either completely virtual or not. That is, a database cannot be both covered and virtual.
091	5B	N	N	CCI COMMUNICATION ERROR The application attempted to use CA Common Services for z/OS CAICCI to access a MUF. The feedback from CAICCI indicated a failure.	Perform the following: Ensure that the MUF startup options correctly request CAICCI support and that the SID parameters for the application match the MUF startup option CAICCI parameters. See the chapter on using the Multi-User dacility in the CA Datacom/DB Database and System Administration Guide. Ensure that CAICCI is active. Review the CAICCI feedback codes displayed on message DB00501E. See Processing, DBUTLTY, and SQL Messages.
093	5D	Y	Y	OPENING URI DATA AREA WITH RECOVER=NO TABLE An area is being opened for one (or more) tables in that area. The area control block from DASD indicates a URI area, but at least one table in the Directory (CXX) has RECOVER=NO. Because this is not a valid or supportable condition, CA Datacom/DB should not have allowed this condition to exist. Therefore, a non-CA Datacom/DB data set restore probably occurred that does not match the Directory (CXX).	Determine how the invalid area came to exist and correct the problem.
094	5E	N	N	Data base if FORMAT 1, action requested is not allowed. This applies to some Version 12.0 features such as MultiDataset index and dynamic extend using cylinders.	Either change the base format to 2 or do not use the option.
095	5F	N	N	CBS ACCESS AGAINST DIRECT TABLE Compound Boolean Selection may select a direct key only in limited conditions. If all conditions are not met, the direct key must be ignored. In this case, the direct key is excluded and no other keys exist, or all other keys are set to CBS IGNORE.	Provide other keys for this request to use, or use simpler requests that generate a Compound Boolean Selection Facility Request Qualification Area with all the restrictions met. The list of restrictions are provided in the direct key information in the CA Datacom/DB Database and System Administration Guide.
096	60	N	N	Another record cannot be added to this area because the highest Unique Row Identifier (URI) is at the maximum.	To reassign URI numbers to any current records and lower the highest URI, the area must be loaded with the LOAD function of DBUTLTY, without providing input in the form of a physical backup taken with the RECID=YES parameter. All other types of backups or extracts are valid, including the NONE option, if no data exists to be loaded.
097	61	N	N	An application attempted to connect to a MUF using a SID. The application SID does not agree with the MUF SID. One of them is using the DBSYSID macro parameter MUFNAME= as the identifier and one is using the DBSYSID macro parameter SUBID= as the identifier. The MUF is identified to the Supervisor call (SVC) by SUBID= or MUFNAME=. A SID is built by assembling the DBSYSID macro.	Change the application SID to match the MUF SID with regard to the MUFNAME= parameter.
098	62	N	N	Release of the DBSIDPR module (or special named DBSYSID Macro assembly output) is not the same as the MUF or interface module.	Ensure the MUF uses a DBSIDPR module at the same release as it is. The same is true forDBUTLTY. For a user application, the DBSIDPR module must match the MUF release to which it is being connected.
099	63	N	N	INTERNAL ERROR An SQL error occurred during a RAAT (record-at-a-time). Certain RAAT commands require processing inside SQL and if a problem is encountered at this point, a RAAT return code is produced. The Master List dump for this error is only produced if you turn on dumps for the return code using either the MUF startup option RCERROR or a DBUTLTY COMM command.	Run a DBUTLTY REPORT AREA=PXX and search for the DATA BASE SQL ERROR SUMMARY section for which there is a 94(99) in the RETURN CODE FROM DB field. Search backwards for the SQL ERROR CODE. Follow the instructions documented in the SQL Return Code section of this guide for the particular error. You can also obtain the SQL error code from the Request Area of the specific RAAT command being executed. From the start of the Request Area, offset 26 (x'1a) contains a 4-byte binary field which when converted to decimal gives you the SQL error code. Contact CA Support if you need further assistance. For information about contacting CA Support, see Troubleshooting.
100	64	N	N	If a navigational application command (that is, a record-at-a-time command, not an SQL statement) triggers an SQL trigger, and that trigger generates an error, a return code 94(100) is received. This return code is generated to make it clear that a trigger failure caused the current record-at-a-time request to fail. For example, a 94(100) could prevent confusion in a situation where, if the triggered procedure performs an INSERT, a DELET command could cause a return code 07 DATA AREA FULL error. The actual return codes produced by the trigger itself may be found in the Request Area, starting at DBRQDIAG (located 26 bytes (decimal) into the user request area), as follows: the 4-byte SQLCODE is followed by the external 2-byte return code, followed by the internal 1-byte return code, followed by the 5-byte SQLSTATE. Note: The Statistics and Diagnostics Area (PXX) contains more detailed information about the SQL error (search for the SQLCODE or SQLSTATE). The Master List dump for this error is only produced if you turn on dumps for the return code using either the MUF startup option RCERROR or a DBUTLTY COMM command.	Correct the error.
101	65	N	N	A maintenance command was performed against DBID 1008, which triggers a CA Datacom/DB TR exit. Either this is a non-TR Multi-User Facility or the trigger exit returned a non-zero return code.	If this is a non-TR Multi-User Facility, maintenance is not allowed against the reserved DBID of 1008. If this is a TR Multi-User Facility, look for indications of the TR problem and, if necessary, contact CA Support. For information about contacting CA Support, see Troubleshooting.
102	66	N	N	ATTEMPTING TO UPDATE DYNAMIC SYSTEM TABLE WITH MORE THAN ONE COLUMN IN SET CLAUSE An update to a dynamic system table using SQL is being done with multiple columns. This is not allowed.	Change the update to have a single column.
103	67	Y	N	FORCE AREA (FXX) INVALID CONTROL BLOCK The Force Area (FXX) has been opened but cannot be validated as a Force Area because of the control block.	Either the Force Area was not initialized, or the JCL is not pointing to the correct data set.
104	68	Y	*	ERROR OCCURRED ON ANOTHER MUF WITHIN THE MUFPLEX	Find task area DBRW---Y and, using the hex offset, find the following: x'14A'— job name (8-byte character) x'152'— run unit number (4-byte binary x'15A'— master list dump reason (1-byte character), values are: s - snap e - error dump d - dump (called from support zap) x'15B'— internal error code (1-byte binary) x'15C'— external return code (2-byte character) x'160'— logical MUFplex number (1-byte binary) Next, go to the logical Multi-User Facility that had the error, and look at the original master list dump. Note: * With 104, buffers are optional based upon original error.
105	69	Y	Y	Another Multi-User in the MUFplex abended.	Pursue the problem on the abending Multi-User. This error and corresponding PXX dump are taken to assist in debugging, if necessary.
106	6A	Y	N	There was an internal MUFplex error involving an invalid version.	Collect the documentation from all executing MUFs and contact CA Support. For information about contacting CA Support, see Troubleshooting.
109	6D	N	N	You attempted an OPEN of a User Requirements Table with RRS=YES specified in the DBURINF macro, but the RRS MUF startup option was not coded. The RRS MUF startup option is required in order to open an RRS=YES User Requirements Table.	Either cycle the Multi-User Facility, specifying the RRS MUF startup option, or specify RRS=NO in the User Requirements Table DBURINF macro.
110	6E	N	N	A call, made in DBINFPR on behalf of the application, to express an unprotected interest in a unit of recovery to RRS, was unsuccessful. Message DB02603E was generated in response.	See message DB02603E in CA Datacom/DB Processing Messages (DB0xxxxc) for details.
111	6F	N	N	An unacceptable return code and internal return code was specified in the RCERROR= parameter of the DBUTLTY COMM ALTER function. See the section on COMM ALTER in the CA Datacom/DB DBUTLTY Reference Guide and the section on the RCERROR MUF startup option in the CA Datacom/DB Database and System Administration Guide. Message DB13001E was generated in response. See DBUTLTY Messages (DB1xxxxc).	Do not specify the identified return code. Some return codes are not valid to produce buffer and master list dumps.
112	70	N	N	You attempted an open of a User Requirements Table with RRS=YES specified in the DBURINF macro, but the RRS exits in the Multi-User Facility are unset.	Either specify RRS=NO in DBURINF, or investigate why the exits are unset. For details about unset exits, see message DB02602E in CA Datacom/DB Processing Messages (DB0xxxxc).
113	71	N	N	A call was made in DBINFPR, on behalf of the application, to RRS to change a UR interest from unprotected to protected, a request that is part of the first CA Datacom maintenance request in a transaction. The maintenance request was successful, but it is not subjected to the Application_Comit_UR (where UR refers to a unit of recovery) command for a commit. You should therefore issue an Application_ Backout_UR command for a rollback after receiving this error. Message DB02603E is generated in response. It shows the RRS return code. See CA Datacom/DB Processing Messages (DB0xxxxc) for details about message DB02603E.	Issue an Application_Backout_UR command for a rollback through RRS.
114	72	Y	N	RRS LOG MISMATCH The CA Datacom/DBLog Area (LXX) was found open during the restart process of a Multi-User Facility enable. The RRS MUF startup option was specified, but the RRS log is either old or wrong.	Check for old or incorrect RRS logs that are being used, and correct the condition. For more information, see the appropriate IBM documentation dealing with resource recovery in MVS Programming .
115	73	Y	N	OPEN BASE URT, NOT ENOUGH ENTRIES The database level open option was selected in the assembly of the User Requirements Table. It did not provide enough entries for all tables currently in the database.	Reassemble the User Requirements Table with a larger number of table entries.
116	74	N	N	An attempt was made to execute area level DBUTLTY control against a Multi-User Facility running as part of a MUFplex, when more than one Multi-User Facility is enabled. Running in this configuration is not allowed.	When running as part of a MUFplex, when more than one Multi-User Facility is enabled, do not attempt to use area level DBUTLTY control. For more information on area level DBUTLTY control, see the CA Datacom/DB DBUTLTY Reference Guide.
118	76	N	N	MUF UTILITY FOUND USERS One of the DBUTLTY functions with the MULTUSE=YES option has found that one or more User Requirements Tables are open in an incompatible manner.	Using the ACCESS function of DBUTLTY, to wait for current users, is one way to ensure the utility does not find a conflict.
119	77	N	N	MUF UTILITY FOUND NOOPT BASE The use of the MULTUSE=YES function in many utility functions requires that the database be specified as OPTIMIZE (the default) in the MUF startup options.	Review the requirements for running the database as optimized and, if acceptable, change the MUF startup option for the next enable of the Multi-User Facility.
120	78	N	N	MUF UTILITY -- VIRT. BASE (OR DST) The utility function being executed is not supported with the MULTUSE=YES option against a database defined as VIRTUAL or specified as the SYSTEMDBID in the MUF startup options.	Review the requirements and the action necessary.
121	79	N	N	RRS ERROR IN MULTIPLE MUF INTERFACE The application is using the multiple Multi-User Facilities interface to make requests to one or more Multi-User Facilities. It has also requested RRS support for complete two-phase commit processing. An error of some type has been received during the RRS commit or rollback process.	Review the information returned and pursue the problem in the one or more Multi-User Facilities involved and also other resource managers.
122	7A	N	N	XCF was unable to respond to a remote RRS change interest request.	Contact CA Support. For information about contacting CA Support, see Troubleshooting.
123	7B	N	N	TRYING TO USE A FUNCTION THAT REQUIRES URI FORMAT You are attempting to use a DBUTLTY function that requires a table or area to be in the URI format.	Review the reasons for the table or area not being URI and, convert to URI. After conversion, the utility functions that require the URI format are available. Note: If you are attempting to LOAD an AREA with MULTUSE=YES and URI=YES but the area is currently marked non-URI, you must first INIT the area.
124	7C	N	N	NO MULTUSE=YES UTILITY IN 2+MUFPLEX The MULTUSE=YES option of BACKUP, EXTEND, EXTRACT, INIT, LOAD, RECOVERY,REORG, and RETIX are not available when executing against a MUFplex and more than one Multi-User Facility is enabled.	These utility functions are not available in this environment.
125	7D	N	N	An application is trying to access a Child table directly within a partition, and that table has been restricted.	Access the Child table through the Parent table or Any Parent table, or change the CA Datacom Datadictionary PARTITION attribute to allow the table to be accessed directly.
126	7E	N	N	INVALID DYNAMIC SYSTEM TABLES DEFINITION The current table definitions cataloged to the Directory (CXX) do not match those required for the code version being executed.	Either the wrong version of the code is being executed, or the definitions need to be updated to match the version of the code.
127	7F	N	N	INVALID COMMAND The console command is not one of those that are listed in the console command table.	Review the spelling or format of the command entered. The command is required to start in the first position of the console input.
128	80	N	N	INVALID VALUE For commands that have a value, the value (or a value) is invalid. There could have been an error of one of the following kinds: A specification error where a number required to be specified, for example, between 1—99 was entered as 0 or 100. A character field that, for example, needed to be specified as 1—8 bytes but was entered as 10 bytes. An error in specific values, for example an option that needed to be entered as YES/NO/ON/OFF but was entered as ABC. A value that was missing, for example an option that required two values but only had one value provided. One or more blanks must follow the command to the first value. If multiple values are allowed or required, they must be separated by one comma and no blanks. Exceptions to that rule include the commands ACCT, COMM, and SECURITY that, for compatibility reasons, treat the second word as its own command, and therefore have a blank following, before any other options.	Compare documentation of the required and optional values to what was actually entered. Correct errors that are found and submit the command again.
129	81	N	N	INVALID CONTEXT (other) The command and optional value (or values) entered are one of the following: Though the command and value specified are valid, they were issued in a context that is not appropriate and cannot be honored. The command and value, though valid, are invalid in some other way. For example, a command could have been issued during MUF startup, but the command could not be done until after the MUF had been enabled, or a command that could only be done during MUF startup was issued after the MUF had been enabled. Some conditions are ignored, instead of being treated as an error, for example if a COMM NEWRXX was issued in a MUF without LOGRCV YES specified, it is accepted but ignored.	Compare documentation of the required and optional values to what was actually entered. Correct errors that are found and submit the command again.
130	82	N	N	In a table defined as SQL read-only, an attempt was made to insert new rows, update existing rows, or delete existing rows. SQL statements cannot be used to perform these functions when the table is defined as SQL read-only.	Either perform the functions using record-at-a-time commands or remove the SQL read-only restriction from the table.
134	86	N	N	The PRESSPAK module is not the same release as CA Datacom/DB as is required.	Review the library modules to see why the releases are not in sync.
135	87	N	N	An open is being attempted to a table defined with both user compression and DB compression which is not allowed.	The table must be backed up with COMPRESS=NO, redefined and reloaded to remove the condition.
136	88	Y	N	UNABLE TO LOAD DYN SYS TABLES MODULE The Dynamic System Table module. could not be loaded.	Check for problems with the MUF library names or with the library data sets.
137	89	Y	N	ENCRYPT NO BASIC 1 SET An area is being subjected to DBUTLTY LOAD or REORG or REPLACE with a table that has encryption but there is currently no ENCRYPT basic key 1 set.	You must either remove basic encryption from the table definition or define a basic key 1 using DBUTLTY function ENCRYPT with OPTION=SET_BASIC_KEY_1 and both OPTION2 and OPTION4 specified as per the DBUTLTY Reference Guide.
138	8A	N	N	OPEN BASIC ENCRYPT NOT CXX Attempting to open a table that is encrypted with the basic option but the encryption key is not the same as either key 1 or key 2 in the Directory CXX.	Basic encryption supports a single encryption key for normal use and as a transition a second key. One choice is to restore the key from the data area to the Directory CXX but doing so can prevent other tables from being opened. The area is allowed to be opened by the DBUTLTY functions BACKUP and EXTRACT if SEQ=PHYSICAL is specified.
139	8B	Y	Y	OPEN TABLE DEFINITION CHANGE The table definition in the Directory CXX does not match the definition in place when the area was loaded. For example, a table was loaded with a table having a 100-byte data size but the current Directory CXX indicates the table is 110 bytes. Not sure how the condition occurred, possible if the user mismatches data sets between the CXX and data area.	Research how the condition was allowed to occur. Datacom needs accurate directory information to understand how to process the data area.
140	8C	N	N	ENCRYPT NOT AUTHORIZED An unauthorized address space is attempting to open an encrypted table.	Authorization is required to open a table that has been loaded as encrypted.
141	8D	N	N	REORG, MUF NOT NONSWAP OR NOT AUTH The DBUTLTY REORG function, when executing with a keyword of MULTUSE=YES, is not executing with a Multi-User Facility that is running with the ability to be swapped out of memory, or is not running authorized.	Review the requirements, and either run the REORG function without the MULTUSE=YES option or recycle the Multi-User Facility after causing it to be authorized and not swappable.
142	8E	Y	N	ENCRYPT HARDWARE An open is attempted on an encrypted table on hardware that does not support decryption.	The area cannot be opened on the current hardware.
143	8F	Y	N	ENCRYPT CA EKM NOT AVAILABLE An encrypted table is being opened using the CA Encryption Key Manager for processing but Datacom is unable to connect to the manager.	The CA EKM must be available to support the open of this table.
144	90	Y	N	OPEN DATA CONTROL NOT OK An area is being subject to DBUTLTY LOAD or REORG with an encrypted table but the block size is too small to contain the needed information.	The data area block size must be made larger and the database cataloged.
145	91	Y	N	DATA BLOCK TOO SMALL An area is being subject to DBUTLTY LOAD or REORG or REPLACE with an encrypted table but the block size is too small to contain the needed information.	The data area block size must be made larger and the database cataloged.
146	92	Y	N	CALLER INVALID OR UNKNOWN The caller application is from an invalid or unknown application. It may be a product that is not supported by the current release of CA Datacom/DB.	If the calling application is known to not be supported, then it should not be executed. If the application is not known, then collect the documentation including the Master List dump and contact CA Support. One example is CA Datacom CICS Services releases prior to r11.0 are not supported.
147	93	N	N	LOG LRSN MAX The Log Record Sequence Number is either at the maximum value or, the number is at the near maximum value and this is the first log record of a transaction.	The Log Record Sequence Number can be reset to a 1 by a clean EOJ of the MUF (all active MUFs, if part of a MUFPLEX). It can also be reset using QUIESCE RST if the MUF is not part of a MUFPLEX having more than one enabled at this time). No dump is taken.
148	94			LOG LBSN MAX The Log Block Sequence Number is at the maximum value.	The number can only be reset by causing the MUF to go through normal EOJ processing (and all other MUFPLEX executing MUFs). No dump is taken.
149	95			LBSN NEAR MAX The Log Block Sequence Number is at the near maximum value and this is the first log record of a transaction.	Running active transactions may continue to execute; new transactions get the error. The number can only be reset by causing the MUF to go through normal EOJ processing (and all other MUFPLEX executing MUFs).
150	96	N	N	XCF was not successful in processing a Remote Resource Manager (RRM) request.	This return code is internal and is not normally seen by a user. If, however, you receive this return code, and there is a problem that cannot be determined by the other messages, contact CA Support.
151	97	N	N	XCF was not successful in processing a Remote Resource Manager (RRM) request.	This return code is internal and is not normally seen by a user. If, however, you receive this return code, and there is a problem that cannot be determined by the other messages, contact CA Support.
152	98	N	N	XCF was not successful in processing a Remote Resource Manager (RRM) request.	This return code is internal and is not normally seen by a user. If, however, you receive this return code, and there is a problem that cannot be determined by the other messages, contact CA Support.
153	99	N	N	XCF was not successful in processing a Remote Resource Manager (RRM) request.	This return code is internal and is not normally seen by a user. If, however, you receive this return code, and there is a problem that cannot be determined by the other messages, contact CA Support.
154	9A	N	N	XCF was not successful in processing a Remote Resource Manager (RRM) request.	This return code is internal and is not normally seen by a user. If, however, you receive this return code, and there is a problem that cannot be determined by the other messages, contact CA Support.
155	9B	N	N	XCF was not successful in processing a Remote Resource Manager (RRM) request.	This return code is internal and is not normally seen by a user. If, however, you receive this return code, and there is a problem that cannot be determined by the other messages, contact CA Support.
156	9C	N	N	XCF was not successful in processing a Remote Resource Manager (RRM) request.	This return code is internal and is not normally seen by a user. If, however, you receive this return code, and there is a problem that cannot be determined by the other messages, contact CA Support.
157	9D	N	N	You have coded an invalid AREA name in either a DBUTLTY function keyword or in a User Requirements Table entry with the AREANAM= keyword.	Make sure the area name being provided exists in the database being referenced.
158	9E	N	N	You have issued a request using the DATACOM interface that requires the DBID to be remapped, and the remapped DBID for the Multi-User Facility (MUF) is greater than 240.	When using the DATACOM interface for requests using a User Requirements Table (URT) with DBID remapping, be certain that the remapped DBID is between 1 and 240.
167	A7	N	N	An open of a URT is being attempted to a MUF that is configured as a LIMITED_INSTALL_MUF in its startup. A MUF so configured allows only action needed to get it to a functional status. For normal user application execution, the MUF must be recycled without the option.	Wait until the MUF is recycled without the option.
168	A8	N	N	A DBUTLTY function is executing and the keyword IXXAREA is in conflict with the database definition. The keyword must be set with a valid name when required and may never be set with an invalid name. For example, if the database has no index area I11, the DBUTLTY function INIT AREA=IXX,IXXAREA=I22 is an error. Another example is a database with index area I33 but the DBUTLTY function INIT AREA=-IXX is being executed without IXXAREA specified.	Correct the use of IXXAREA= and submit the DBUTLTY again. If you need to run a CXX report to see the existing index areas, that can be done with REPORT AREA=CXX,TYPE=B,DBID=n where n is the database in question.
170	AA	N	N	A database is attempting an open but it is in conflict because it is a MultiDataset index and the database was set as ACCESS NOOPT in the MUF startup in conflict of requirements.	Either the MUF needs to be recycled without the ACCESS NOOPT for the database or the database needs to be redefined and reloaded with the single index area IXX.
171	AB	N	N	The process being done is not allowed to a MUF that is currently part of a MUFplex with more than one MUF executing.	Do not run this action until or unless all MUFs are ended except one.
172	AC	N	N	A user application is attempting to open a URT in single user mode which has been disabled in this Directory (CXX) by the CXXMAINT option ALTER with Y_SU (the default) and the recommended method of execution which is having a DBURSTR Macro keyword set to MULTUSE=YES.	Preferred option is to change the URT to execute using the MUFplex User Facility. Otherwise, execute the CXXMAINT option to allow single user execution.
176	B0	N	N	A single-user function (DBUTLTY) is trying to open an index or data area that is currently being processed by a Multi-User Online Area Move process.	The Online Area Move process must complete before any single-user jobs can be executed against the area.
193	C1	N	N	DUPLICATE UNIQUE KEY An ADDIT or UPDAT command, if honored, would cause a duplicate unique key. The key name of the key in error is returned at Request Area +26.	Do one of the following: Correct the record being added or updated to not contain a duplicate key value. Delete or change the existing record which has this key value. Modify the table definition to make this key not unique.
194	C2	Y	Y	CAN'T DO ALL OF UNMARK	Contact CA Support. For information about contacting CA Support, see Troubleshooting.
195	C3	N	N	CONFIRMING AND CONSTRAINT REBIND FAILED SQL initiated an automatic rebind process for an invalid constraint during a CONFIRM. The automatic rebind process failed, making execution of the CONFIRM process impossible.	Run DBUTLTY REPORT AREA=PXX and search for an error summary for the SQLCODE -40 or -37 which terminated the constraint rebind. Follow the instructions listed in the appropriate SQL code. After the cause of the problem is corrected, the CONFIRM can be rerun. If neither of these SQL codes appear in the PXX, save the PXX report for possible use by CA Support and rerun the CONFIRM after clearing the PXX (DBUTLTY COMM OPTION=CLRPXX), then repeat this process. Alternative action: Drop CHECK constraints and re-add. If a +170 SQL code is produced, retry the CONFIRM. If no negative SQL code has been produced, all is well. Your CONFIRM was accomplished during the ALTER TABLE ADD CHECK. If a negative SQL code was produced then please remember to re-add all CHECK constraints after performing the following steps:

Return Code 94 Internal Return Codes

Dec	Hex	M	B	Explanation	User Response
195	C3	N	N	CONFIRMING AND CONSTRAINT REBIND FAILED	(Continued from previous page.) Drop FOREIGN KEY constraints and re-add. If the foreign keys do not re-add because our automatic rebind fails, use an SQL query against the foreign key table and its target to determine which rows are in violation of the constraint, and delete those rows. To find out which rows caused ALTER TABLE CHILD ADD FOREIGN KEY (COL1, COL2) REFERENCES PARENT (COL1, COL2) CONSTRAINT CHILDTOPARENT to receive a foreign key violation, issue the following query: SELECT COL1, COL2, any-other-columns-desired FROM CHILD WHERE NOT EXISTS (SELECT COL1, COL2 FROM PARENT WHERE PARENT.COL1 = CHILD.COL1 AND PARENT.COL2 = CHILD.COL2). All rows in violation of the would-be foreign key are returned. Re-add the foreign keys. A CONFIRM should no longer be required since the automatic rebind process is triggered by ALTER TABLE ADD FOREIGN KEY.
200	C8	N	N	This indicates that one execution of DBUTLTY is incorrectly connected. A single execution may only execute against a single Directory (CXX). In the two modes of operation, Single User and Multi-User Facility, the first connection establishes the CXX name being used. If a function utilizes the other mode and finds a different name, the error is recognized.	Take appropriate action, based on the explanation.
201	C9	N	N	A rollback scheduled by the restart process has ended processing all log records for bases except those set to NORESTART. The user action is unknown but dependent on why the database(s) were set to NORESTART.	This return code is for information only.
202	CA			The data set other than the CXX is being executed on a System in a different Sysplex than the CXX is defined to execute.	If executing the Job on the wrong System, submit it again on a System in the expected Sysplex. If the Sysplex name is not currently accurate, see the provided message DB00912E for information and action for how to proceed.