DSNB260I csect-name WARNING - A READER HAS BEEN RUNNING FOR duration MINUTES - CORRELATION NAME=correlation-name, CONNECTION ID=connection-id, LUWID=luwid ID=token, PLAN NAME=plan-name, AUTHID=authorization-id, END USER ID=user-id, TRANSACTION NAME=transaction-name, WORKSTATION NAME=system-name

Explanation

One of the following situations occurred:

  • A long-running reader reached the maximum permitted time without issuing either a COMMIT or ROLLBACK statement.
  • A reader that was claimed by cursors that were defined WITH HOLD was held longer than the number of minutes that an agent can hold a read claim.
csect-name
The name of the control section that issued the message.
duration
The time, in minutes, that has elapsed since the beginning of the unit of work.
correlation-name
The correlation name that is associated with the unit of work.
connection-id
The connection ID that is associated with the unit of work.
luwid
The logical unit of work ID, or an asterisk (*) to denote that the thread originated at the local site.
token
A unique token number that is associated with the logical unit of work ID.
plan-name
The plan that is associated with the unit of work.
authorization-id
The authorization ID that is associated with the unit of work.
user-id
The user ID that is associated with the unit of work, if known. Otherwise, an asterisk (*).
transaction-name
The transaction that is associated with the unit of work, if known. Otherwise, an asterisk (*).
system-name
The workstation hostname that is associated with the unit of work, if known. Otherwise, an asterisk (*).

The amount of time that is permitted for a reader is controlled by the LRDRTHLD subsystem parameter.

System action

Processing continues.

If IFCID 0313 trace is activated, an IFCID 0313 trace record is written. This message is issued every time that the threshold is reached.

System programmer response

Work with the application programmer to determine if there is a problem with the unit of work. If an application program caused the unit of work to reach its time limit threshold, you can use CANCEL THREAD to cancel the associated thread.

Administrator response

Increase the value of subsystem parameter LRDRTHLD so that this message is issued less frequently.

Programmer response

Make sure that the application commits at appropriate intervals, or work with the Db2 administrator to determine an appropriate frequency for the COMMIT check.