DB2 SQL-Error: -923
SQLState: 57015
Short Description: CONNECTION NOT ESTABLISHED DB REASON TYPE NAME SQLCODE
The connection to DB2 failed for the reason indicated by condition, which can be any of the following: v DB2 not up v DB2 not operational v DB2 shutdown in progress v DB2 restricted access mode v Allocation error v DB2 - CICS attachment not up v DB2 - CICS ENTRY disabled v The object is dependent on facilities of a release of DB2 that is newer than the release that you are currently running (fall back). v DB2 restarted in LIGHT(YES) mode Possible causes of an allocation error are: v The application plan does not exist. v The application plan is inoperative. An explicit REBIND or BIND is required. v The application plan is invalid. Underlying resources have changed. v A required database, table space, table, or index is unavailable. v Data set allocation failed for a required data set. v There is insufficient virtual storage. v 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 executed. 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. If they are available, refer to Part 3, “DB2 codes” for an explanation of the reason-code, resource-type, and resource-name. Refer to message DSNT500I under DB2 Messages for an explanation of resource type and resource name. Refer to Table 3 in Appendix C, “Problem determination,” on page 757 for an explanation of resource type codes. Any attempts to issue SQL statements after receiving