-923 CONNECTION NOT ESTABLISHED: DB2 condition REASON reason-code, TYPE resource-type, NAME resource-name
Explanation
- reason-code
- The DB2 reason code value that indicates the reason for the failure. For explanations of reason codes, see DB2 reason codes.
- condition
- DB2 not up
- DB2 not operational
- DB2shutdown in progress
- DB2 restricted access mode
- Allocation error
- DB2 - CICS® attachment not up
- DB2 - CICS ENTRY disabled
- The object is dependent on facilities of a release of DB2 that is newer than the release that you are currently running (fall back).
- DB2restarted in light mode
- reason-code
- The DB2 reason code value that indicates the reason for the failure. For explanations of reason codes, see DB2 reason codes.
- resource-type and resource-name
- The type and name of the resource that the message identifies. For an explanation of resource-type and resource-name values, see Resource types.
Possible causes of an allocation error are:
- The application plan does not exist.
- A required database, table space, table, or index is unavailable.
- Data set allocation failed for a required data set.
- There is insufficient virtual storage.
- The application is trying to execute the plan from a system (environment) that was restricted when the plan was bound or rebound. Check the SYSPLSYSTEM table to determine from which systems (for example, IMS™ or CICS) the plan can be executed.
If the condition is "CICS attachment not up", then NAME indicates the DB2 subsystem that is not available. The reason-code indicates the reason the attachment is not available.
If the condition is "CICS entry disabled", then NAME indicates the entry that is disabled.
System action
The statement cannot be processed. The connection to DB2 is not established.
Programmer response
If the connection failed because either DB2 or a required database, table space, table, or index was unavailable, wait until it is available before invoking the application again.
If allocation failed for an application plan, REBIND the plan to determine the problem. Error messages are produced explaining why the plan could not be allocated.
For other types of allocation errors, installation action might be required to correct the problem.
For CICS attachment failures, resolve the primary cause as noted by the reason code. Then restart the attachment.
Problem determination
The reason-code, resource-type, and resource-name might not be available. If they are not available, nothing appears.
Any attempts to issue SQL statements after receiving SQLCODE -923 will cause unpredictable results.
SQLSTATE
57015
