DSNU377I csect-name - IN utility WITH SHRLEVEL CHANGE, THE LOG IS BECOMING LONG, MEMBER=member-name, UTILID=utilid
Explanation
During log processing for REORG with SHRLEVEL CHANGE, the number of log records that the next iteration will process is not sufficiently lower than the number that the previous iterations processed. This situation means that during reorganization, the log is not being read quickly enough to catch up to the application writing the log. This is a WTO message; it is sent to the console, but it is not an action message. It is also sent to SYSPRINT.
During log processing for utility with SHRLEVEL CHANGE, the number of log records that the next iteration is to process is not sufficiently lower than the number that the previous iterations processed. When you executed the utility, the log was not read quickly enough to catch up to the application that is writing the log. This is a WTO message; it is sent to the console, but it is does not require any user action. The message is also sent to SYSPRINT.
- You issue an -ALTER UTILITY command.
- You issue a -TERM UTILITY command.
- Db2 estimates that the time to perform the next iteration is less than or equal to the time specified in the MAXRO phrase.
- The utility terminates for any reason (including the deadline).
- member-name
- Identifies the Db2 member in a data sharing environment. It is blank in a non-data-sharing environment.
- utilid
- Identifies the utility job step.
System action
After a delay (specified by the DELAY phrase of the utility or the -ALTER UTILITY command), the REORG utility performs the action specified by the LONGLOG phrase of the REORG utility or the -ALTER UTILITY command.
Operator response
No action is required. However, if the action that is specified by the LONGLOG phrase is not what you wanted, the operator (or a user-written program that is triggered by the message) can take an action.
Severity
4 (warning)