DSNP002I csect - DEFINE FAILED FOR data-set-name RC=reason-code CONNECTION-ID=connection-id, CORRELATION-ID=correlation-id, LUW-ID=logical-unit-of-work-id =token
Explanation
Data set definition failed (in CSECT 'DSNPmmmm') for the reason identified by RC. The connection ID, correlation ID, and logical-unit-of-work ID (LUW-ID) identify the user or application that encountered the problem. The connection, correlation, and logical-unit-of-work IDs identify the user or application that encountered the problem. Correlation IDs beginning with '0nn', where 'nn' is a number, identify system agents.
A LUW-ID of '*' indicates that the thread does not have a LUW-ID. If the LUW-ID is not an '*', the value is a logical-unit-of-work-id that is assigned to the thread followed by an '=' 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.
Messages that have the same connection ID, correlation ID, and LUW-ID relate to the same user. This makes it possible to scan a number of DSNP-prefixed messages and group activities involving a given user.
System action
The data space manager (DSM) terminates its actions associated with the current SQL request. Higher level functions might terminate the current SQL request or the unit of recovery that issued the request.
Operator response
This message is directed to either the database administrator or the system administrator. Bring the message to their attention if it appears on the MVS operator's console. The installation should consider directing Db2 messages to a console other than the operator's console.
System programmer response
Investigate the problem indicated by the reason code and preceding access method services messages, if any, and correct it, if possible. If an out-of-space condition exists, see the description of message DSNP001I for actions to consider.
Problem determination
See Problem Determination of message DSNP001I for this information.