DSNP012I csect - ERROR IN ICF CATALOG LOCATE FUNCTION FOR data-set-name CTLGRC=cc CTLGRSN=zzzzrrss CONNECTION-ID=xxxxxxxx, CORRELATION-ID=yyyyyyyyyyyy, LUW-ID=luw-id

Explanation

csect-name

The name of the control section that issued the message.

data-set-name

The name of the data set

cc

The return code that Db2 received from an SVC 26 call (ICF catalog locate function).

zzzzrrss

The reason code that Db2 received from an SVC 26 call (ICF catalog locate function). The reason code is in the same format as that returned to Db2 by the SVC 26 call.

If cc is 4 or 8, the reason code is associated with access method services message IDC3009I. To determine the name of the CSECT that set the reason code, convert zzzz from hexadecimal to EBCDIC, and append the resulting 2 characters to 'IGG0CL'. For example, suppose that zzzz is C6C6. The EBCDIC equivalent of X'C6C6' is 'FF', so the CSECT that set the reason code is IGG0CLFF.

rr is the hexadecimal equivalent of the reason code value that is documented in access method services message IDC3009I. ss is the hexadecimal equivalent of the return code value that is documented in access method services message IDC3009I. (The return code follows the reason code.) Convert rr and ss to decimal. Then, see the description of IDC3009I for explanations of the reason code and return code. For example, suppose that rrss is 0532. The decimal equivalent of X'32' is 50, and the decimal equivalent of X'05' is 5. Therefore, in IDC3009I, you need to look up a return code of 50 and a reason code of 5.

If CTLGRC=AAAAAA08 and CTLGRSN=AAAAAA08, zzzzrrss is not associated with access method services message IDC3009I. AAAAAA08 indicates that the specified data set is not in the ICF catalog.

xxxxxxxx

The connection ID for the user or application that encountered the problem.

yyyyyyyyyyyy

The correlation ID for the user or application that encountered the problem.

Correlation IDs that begin with '0nn', where nn is a number, identify system agents.

luw-id

The logical unit of work (LUW) ID for the user or application that encountered the problem.

An LUW ID with an asterisk (*) indicates that the thread does not have an LUW ID. If the LUW ID is not an asterisk (*), the value is an LUW ID that is assigned to the thread followed by an equals sign (=) and a token value. (The token value can be used in place of the LUW ID in any Db2 command that accepts an LUW ID as input.)

Messages that have the same connection ID, correlation ID, and LUW ID relate to the same user. This situation makes it possible to scan a number of DSNP messages and group activities that involve a particular user.