DSNT800I csect-name DB2 CANNOT IDENTIFY TO IRLM. IRLM CANNOT CONNECT TO ITS DATA SHARING GROUP. THE LOCK STRUCTURE THAT IRLM ATTEMPTED TO ACCESS WAS strname.
Explanation
IRLM failed to connect to the IRLM data sharing group. This message accompanies abend reason code 00E30806.
System action
DB2® terminates abnormally with reason code 00E30806.
System programmer response
Some possible reasons why IRLM could
not connect to its data sharing group are:
- The lock structure is not properly defined in the active MVS™ CFRM administrative policy. The
lock structure name is a concatenation of the DB2 data sharing group name and the string 'LOCK1'
separated by an underscore (_). For example, if the DB2 data sharing group name is DSNCAT, DSNCAT_LOCK1
is the lock structure name.
Ensure that the lock structure is properly defined in the active CFRM policy. The name of the lock structure that IRLM attempted to access is given in this message. IRLM issues message DXR138E to indicate that the lock structure definition could not be accessed in the active CFRM policy.
- IRLM could not connect the lock structure. The reason for the connect failure is given in IRLM message DXR135E.
- IRLM could not join its data sharing group. The reason for the join failure is given in IRLM message DXR134E.
- IRLM joined the wrong group. The set of IRLMs that are connected to a given lock structure must all be members of the same group. Ensure that the GROUP parameter is correctly specified in the IRLM startup procedure. If you give an incorrect group name, IRLM connects the lock structure, and then times out waiting for responses from other connectors. IRLM issues message DXR133I for the timeout.