DSNP006I csect - REQUIRED STOGROUP DEFINED DATA SET NOT AVAILABLE- data-set-name RC=rrrrrrrr CONNECTION-ID=xxxxxxxx, CORRELATION-ID=yyyyyyyyyyyy, LUW-ID=logical-unit-of-work-id=token
Explanation
An attempt to alter the shareoptions of this data set failed. The data set could not be accessed for the reason indicated by RC. The connection ID, correlation ID, and logical-unit-of-work ID (LUWID) identify the user or application that encountered the problem. Correlation IDs beginning with '0nn', where 'nn' is a number, identify system agents.
The value of the LUWIDis 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 the logical-unit-of-work-id in any Db2 command that accepts the logical-unit-of-work-id as input.
Messages having the same connection ID, correlation ID, and LUWID 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
Db2 terminates its actions associated with the current SQL request. Db2 might terminate the current SQL request or the unit of recovery that issued the request.
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
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.
Problem determination
See Problem Determination for message DSNP001I for this information.
Severity
8 (error)