DSNU121I csect-name TIMEOUT INFORMATION: NUMBER OF HOLDERS/WAITERS = hw-count, TIMEOUT FACTOR = timeout-factor.

Explanation

Utility processing encountered a resource that is currently unavailable because of a timeout condition. The resource cannot be granted and the wait period has exceeded the maximum wait period specified by the RESOURCE TIMEOUT field on panel DSNTIPI (the IRLMRWT subsystem parameter).

csect-name
The name of the control section that issued the message.
hw-count
The number of holders or waiters involved in the timeout.
timeout-factor
An internally defined wait period.

The introductory message text is followed by set of column headings and one or more rows with information about the resource holders: 

LOCK NAME  TYPE  FUNC/STATE/DURATION  HOLDER/WAITER  PLAN-ID  CORR-ID  MEMBER NM
text       text  text                 text           text     hex      text
LOCK NAME text
The lock resource name.
TYPE text
The type of lock, such as PG or DBD.
FUNC/STATE/DURATION text
Information about the lock function, state, or duration. Expected values depend on the type of information.
Lock function
The requested lock function: LOCK, UNLOCK, or CHANGE.
Lock state
The lock resource state, such as SHARED or EXCLUSIVE.
Lock duration
The lock resource duration, such as MANUAL or PLAN.
HOLDER/WAITER text
Indicator if the resource is a holder or a waiter.
PLAN-ID text
The plan name of the holder or waiter.
CORR-ID hex
The correlation ID of the holder or waiter.
MEMBER NM text
The Db2 member name.

System action

The utility abnormally terminates with a X'04E' abend and a utility reason code. The dump is suppressed. Message DSNT500I is issued.

System programmer response

Use the information provided in messages DSNU121I (specifically information about holders and waiters) and DSNT500I to identify the lock resources and the utility jobs and applications that are involved in the timeout.

User response

Use the TERM UTIL command to restart or terminate the utility.

Problem determination

Collect the following diagnostic items:
  • Console output from the system on which the job was run, and a listing of the SYSLOG data set for the period of time that spans the failure.
  • SVC dump (or system dump), taken to SYS1.DUMPxx data set, as result of an operator-initiated dump command or SLIP trap exit.
  • Listing of SYS1.LOGREC data set, obtained by executing IFCEREP1.
  • IRLM trace output.
  • SYSPRINT output, including JCL, for the application program or batch job, and system messages that were issued. Make sure that MSGLEVEL=(1,1) on the JOB statement so that all diagnostic information is sent to SYSPRINT.
  • Listing of the IRLM procedure.
  • Results from SELECT * from SYSIBM.SYSDATABASE.