Start of change

DSNT501I   csect-name RESOURCE UNAVAILABLE

Explanation

The requested function requires a resource that is unavailable. This message is issued with other messages that identify the system action and the action that the installer or operator should take.

In some cases, DB2® can recover from this situation where a resource is not available and can complete successfully. One example is during the setup of a performance enhancement during bind time for execution time. If DB2 recovers successfully, no action is necessary.

correlation-id
The correlation identifier of the thread that is associated with the requester of the resource.
connection-id
The connection identifier of the requester.
luw-id
The logical-unit-of-work identifier (LUW-ID) of the thread that is associated with the requester of the resource. An asterisk (*) indicates that the thread does not have a LUW-ID. If the LUW-ID is not an asterisk, the value is a logical-unit-of-work-id that is assigned to the thread. This value is followed by an equal sign (=) and a token value, which can be used in place of logical-unit-of-work-id in any DB2 command that accepts logical-unit-of-work-id as input.
reason-code
The reason code that tells why the resource is unavailable.
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.

For some situations, message DSNT501I is issued once and then suppressed until the resource is available. For example, this situation occurs when this message is issued for reason code 00C90081. As another example, for TYPE=905, REASON=00C90092, and NAME=IRLM, message DSNT501I is usually issued once. It is suppressed at the DB2 subsystem level until the IRLM out-of-storage condition is relieved.

Operator response

Note the values for reason-code, resource-type, and resource-name.

System programmer response

Look up the reason code for more information about why the resource was unavailable and possible actions to correct the problem. For example, if the reason code is 00C900A6, you must migrate the catalog to the current release. To do so, run DSNTIJTC.

Problem determination

Collect the following diagnostic items:
  • Console output from the system on which the job was run, and a listing of the SYSLOG data set for the period of time that spans the failure.
End of change