DSNP014I IRLM MANUAL LOCK REQUEST FAILED FOR data-set-name. RC=reason-code,SC=subcode, CONNECTION-ID=connection-id, CORRELATION-ID=correlation-id, LUW-ID=logical-unit-of-work-id=token
Explanation
Db2 requested a manual lock on a data set, but the lock could not be obtained for reasons specified in RC and SC. RC and SC are the return code and reason code from IRLM. The connection ID, correlation ID, and logical-unit-of-work ID (LUW-ID) identify the user or application that encountered the problem.
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. DSNP001I or DSNP007I follow this message. Correlation IDs beginning with '0nn', where 'nn' is a number, identify system agents.
If message DSNT376I was received before message DSNP014I, the lock request failed because of a timeout condition. Otherwise, refer to the IRLM return and reason codes for an explanation of the failure.
System action
The current SQL or the unit of recovery that issued the request might be terminated.
Operator response
This message is directed to the database administrator or the system administrator. Bring it to that person's 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 IRLM return and reason code.
Problem determination
Provide the console sheet and a dump. A GTF trace might also be required. If you suspect an error in Db2, you might need to report the problem. For information about identifying and reporting the problem, see Collecting diagnostic data. Refer to the explanation section of this message for additional problem determination information.