Title: How to locate and determine the cause of DB00501E Errors.

Document ID : KB000020280
Last Modified Date : 14/02/2018
Show Technical Document Details


This knowledge document provides instructions on how to locate and determine the cause of DB00501E errors received by CA Workload Automation Restart Option for z/OS Schedulers (CA 11).


Refer to the CA-Datacom/DB Message Guide, and review the section titled CA-Datacom/DB Return Codes when a job fails with a DB00501Eerror while being processed by CA 11.

Each Return Code is documented with a chart that provides the reason and action which causes or generates the return code.

The DB00501E error will have the following format:

22.41..41 STC0331 CA11MUF:DB00501E -OPEN ERROR - RETURN CODE XX (###)

The most common DB00501E errors with their description and probable cause are listed below:

Return Code: 02 (52)Request was an OPEN and one of the tables is not defined to the Directory or the request was an OPENand all the tables in the area are being backed up or extracted and are in an a "NOT LOADED" status.
Return Code: 25 (20) Request was an OPEN, and the table being opened references a database which is not defined to the Directory.
Return Code: 57 (1) The address passed to CA-Datacom/AD in a multi-tasking environment is invalid.
Return Code: 69 (71) Data in a table cannot be accessed because no current index exists for that table.
Return Code: 85 (2) The job has requested XCF access to a remote Multi-User Facility and there are insufficient tasks defined in the MUF startup option TASKS xcfnumber parameter to satisfy this request.
Return Code: 87 (2) The sender was not included in the XCFFROM list in the DBSIDPR macro.