Return Code 13 - INTERNAL ERROR

CA Datacom/DB Return Codes › Return Codes › Return Code 13 - INTERNAL ERROR

Return Code 13 - INTERNAL ERROR

Reason:

An invalid block number, a wrong record length, or an error condition beyond the control of the application programmer occurred.

Action:

See the documentation for the internal error code. The internal return code is in the position immediately following the return code in the Request Area.

If you need help in recovering from the error, contact CA Support. When you call, have available one of the following dumps:

If the Multi-User Facility was involved, have available the dump produced on the Statistics and Diagnostics Area for return code 13. To generate this report, execute the DBUTLTY REPORT AREA=PXX function with the specification DUMPS=FULL and RTNCODE=13.
If the return code was generated during the execution of a function of DBUTLTY, print the DBUTLTY region dump from the SNAPER data set, if z/OS, or the SYSLST data set, if VSE.

Return Code 13 Internal Return Codes

Dec	Hex	M	B	Explanation	User Response
002	02	Y	Y	WRONG RECORD LENGTH There is probably an error in the JCL. The accompanying message, DB00802W, points to the disk location in error.	Verify that the JCL points to the correct area and revise if an error is found. For additional information, see the documentation for message DB00802W. If necessary, contact CA Support with the recommended dumps. For information about contacting CA Support, see Troubleshooting.
003	03	Y	Y	NO RECORD FOUND There is probably an error in the JCL. The accompanying message, DB00801W, points to the disk location in error.	Verify that the JCL points to the correct area and revise if an error is found. For additional information, see the documentation for message DB00801W. If necessary, contact CA Support with the recommended dumps. For information about contacting CA Support, see Troubleshooting.
004	04	Y	Y	INVALID BLOCK NUMBER	Contact CA Support with the recommended dumps. For information about contacting CA Support, see Troubleshooting.
005	05	Y	Y	BLOCK OUTSIDE OF EXTENTS There may be a JCL error specifying the physical location of the data area or the Index Area. The data set may not have access to all the extents or the data set does not have access or know about all the volumes this data set should be on.	If there is a JCL error, correct it. Check the Directory against the operating system catalog and VTOC information to ensure that total disk space, sequence of extents, and accessible volumes are correct. If the problem persists, obtain the recommended dumps and contact CA Support. For information about contacting CA Support, see Troubleshooting.
007	07	Y	N	INVALID INTERNAL CA DATACOM/DB REQUEST	Contact CA Support with the recommended dumps. For information about contacting CA Support, see Troubleshooting.
008	08	Y	Y	INVALID DATA BLOCK FORMAT	Contact CA Support with the recommended dumps. For information about contacting CA Support, see Troubleshooting.
011	0B	Y	Y	INVALID REQUEST TO DBBFRMG	Contact CA Support with the recommended dumps. For information about contacting CA Support, see Troubleshooting.
014	0E	Y	Y	DB attempted to add a duplicate master key to a table with DUPLICATE MASTER KEY = NO specified.	Collect the PXX dump of the condition and contact CA Support. For information about contacting CA Support, see Troubleshooting.
016	10	Y	Y	REQUIRED TABLE NOT IN OPEN USER REQUIREMENTS TABLE The required table is not in the internal control block representing an open User Requirements Table.	Contact CA Support with the recommended dumps. For information about contacting CA Support, see Troubleshooting.
017	11	Y	Y	INTERNAL INDEX ERROR	Contact CA Support with the recommended dumps. For information about contacting CA Support, see Troubleshooting.
018	12	Y	Y	INTERNAL INDEX ERROR	Contact CA Support with the recommended dumps. For information about contacting CA Support, see Troubleshooting.
019	13	N	N	INTERNAL INDEX ERROR	Contact CA Support with the recommended dumps. For information about contacting CA Support, see Troubleshooting.
023	17	Y	Y	COMMANDS ISSUED IN INVALID SEQUENCE	Contact CA Support with the recommended dumps. For information about contacting CA Support, see Troubleshooting.
024	18	Y	N	INTERNAL DIRECTORY (CXX) ERROR An internal error occurred trying to update the Directory (CXX).	Contact CA Support with the recommended dumps. For information about contacting CA Support, see Troubleshooting. You can also rerun the failing job since this condition could be self correcting.
025	19	N	N	An internal error occurred trying to initialize the Directory (CXX).	Contact CA Support with the recommended dumps. For information about contacting CA Support, see Troubleshooting.
026	1A	N	N	The CA Datacom/DB Open/Extend logic could not find the correct data set name (DSN) for the area being extended.	Contact CA Support. For information about contacting CA Support, see Troubleshooting.
031	1F	Y	Y	DATA SPACE MANAGER INTERNAL ERROR	Contact CA Support with the recommended dumps. For information about contacting CA Support, see Troubleshooting.
032	20	Y	N	Internal error in DBMPXPR processing MUFplex.	Collect documentation and contact CA Support. For information about contacting CA Support, see Troubleshooting.
056	38	Y	Y	LOGIC ERROR	Contact CA Support with the recommended dumps. For information about contacting CA Support, see Troubleshooting.
060	3C	Y	N	LOGIC ERROR	Contact CA Support with the recommended dumps. For information about contacting CA Support, see Troubleshooting.
062	3E	Y	N	SORT IN LOAD, RETIX, OR BACKWARD RECOVERY HAD ERROR Either the LOAD AREA=aaa function, the RETIX function, or the RECOVERY OPTION=BACKWARD function of DBUTLTY was executed with SORT= specified. An error occurred during the activation of the sort option.	Contact CA Support with the recommended dumps. For information about contacting CA Support, see Troubleshooting.
069	45	Y	Y	TRANSACTION BACKOUT ERROR Possibly caused by a LOGLB command that has not initialized the request area to zero on the first LOGLB request in a series or set. There are very many other error conditions that could occur during the backout of a transaction. They are documented separately in most cases and need to be handled based on their return code.	For the LOGLB or LOGDR commands, review the user application for errors. For all other conditions, see if a previous error was also provided and if so, handle that situation. If no previous error, get the documentation and contact CA Support.
070	46	N	N	INTERNAL CONDITION ONLY This condition is internal and is not seen outside the Multi-User Facility.	No user action is expected, but if it should occur externally, gather documentation and contact CA Support. For information about contacting CA Support, see Troubleshooting.
071	47	Y	Y	I/O TO A DATA SET THAT IS NOT OPEN An I/O is being attempted to a data set that is in a closed state. The condition of a closed state normally only occurs when an operating system open error occurs for a data set, or the COMM OPTION=CLOSE,DBID=nnnn,AREA=aaa has been processed.	Collect documentation and contact CA Support. For information about contacting CA Support, see Troubleshooting.
090	5A	Y	N	INTERNAL INDEX ERROR	Contact CA Support with the recommended dumps. For information about contacting CA Support, see Troubleshooting.
126	7E	Y	Y	DATABASE DEFINITION CHANGE ERROR An error occurred because of an unexpected change in the database definition. Such an unexpected change can result from executing the DBUTLTY RESET AREA=CXX function for a specific database immediately before updating the Directory with either the CA Datacom Datadictionary online CATALOG function or the DBUTLTY CXXMAINT OPTION=DDPROD function. Do not use RESET for this purpose.	If a RESET was done, stop the Multi-User Facility and reapply the maintenance. Otherwise, contact CA Support with the recommended dumps. For information about contacting CA Support, see Troubleshooting.
131	83	Y	Y	INDEX NEXT COMMAND KEY VALUE ERROR During a next-type read or locate request, the key value in the Request Area has been changed.	Correct the application to maintain the key value for all next-type commands.
138	8A	Y	N	SEQUENTIAL COMMAND AND NO EXTENSION	Contact CA Support with the recommended dumps. For information about contacting CA Support, see Troubleshooting.
176	B0	N	N	INTERNAL COMMAND WORK AREA LENGTH ERROR	Contact CA Support with the recommended dumps. For information about contacting CA Support, see Troubleshooting.
177	B1	Y	N	EIP VIRTUAL BLOCK OUT OF EXTENT	Contact CA Support with the recommended dumps. For information about contacting CA Support, see Troubleshooting.
178	B2	Y	Y	Internal Error Duplicate lock with the recommended dumps.	Contact CA Support.
179	B3	N	N	This error is probably the result of a load failure on a CA Datacom/DB SID module. Such a failure can occur for one of two reasons as follows: Either the load library containing the particular CA Datacom/DB SID module does not exist in the DFHRPL concatenation, or The DBCSID SIDNAME= parameter value in the DBCVTPR assembly and LINK is not correct.	If one of the given reasons is the problem, correct the problem and recycle CICS. If one of the two given reasons is not the problem, contact CA Support. For information about contacting CA Support, see Troubleshooting.