Filter
Top Products
152 DB2 Manager User Guide
StorageTek Proprietary
OTD20071 Invalid Purge operand(s) – request ignored
Explanation: An invalid operand has been entered with the PURGE operator
command.
Action: Ensure that the PURGE command is specified correctly and re-enter
the command. Refer to page 55 for details of the operator PURGE
command.
OTD20072 Task tnnn is already being purged – request ignored
Explanation: A second PURGE request has been entered for a busy sub-task
before the first PURGE request has been processed, where ‘t’
identifies the sub-task type (‘D’ – disk reader; ‘H’ – housekeeping; ‘S’
– scheduler; ‘T’ – tape reader; ‘W’ – writer) and ‘nnn’ gives the sub-
task number.. The request is ignored.
Action: Wait for the queued PURGE command to be processed after all
outstanding retrieval requests have been completed. To immediately
terminate the sub-task, enter the FORCE command.
OTD20073 Task tnnn purge request is being processed
Explanation: A PURGE request has been queued for a sub-task, where ‘t’ identifies
the sub-task type (‘D’ – disk reader; ‘H’ – housekeeping; ‘S’ –
scheduler; ‘T’ – tape reader; ‘W’ – writer) and ‘nnn’ gives the sub-task
number. Waiting tasks will terminate immediately; busy tasks will
terminate when all currently queued requests have been processed.
Action: None this is an informational message.
OTD20081 Invalid Force operand(s) – request ignored
Explanation: An invalid operand has been entered with the FORCE operator
command.
Action: Ensure that the FORCE command is specified correctly and re-enter
the command. Refer to section 0 on page 4.55 for details of the
FORCE operator command format.
OTD20082 Controller received error posting requestor ECB
Explanation: An error occurred posting an outstanding request during force purge
processing. The DB2 Manager control region will attempt to recover
from this error condition and continue processing.
Action: Consult other available system messages for additional information
regarding the error. If no apparent cause for the failure can be
determined, report the problem to your DB2 Manager product support
representative. Preserve all diagnostic information and system dumps
for further analysis.