Filter
Top Products
DB2 Manager User Guide 155
StorageTek Proprietary
OTD22002 Scheduler initialization error: insufficient storage available for
workareas
Explanation: A request for virtual storage in the DB2 Manager control region has
been rejected by the operating system. Control region initialization
processing is aborted.
Action: Allocate more virtual storage to the control region, by increasing the
value of the SIZE parameter in the DB2 Manager procedure. Restart
the control region.
OTD22003 Storage Release Error: Return Code=X'xx' T=Snnn
Explanation: An error has been received trying to free a virtual storage area during
scheduler task shutdown processing. ‘xx’ gives the hexadecimal
return code from the STORAGE macro, and ‘nnn’ identifies the
scheduler task number. Shutdown processing will continue normally.
Action: Consult IBM documentation on the STORAGE macro for an
explanation of the return code displayed in the message. If
necessary, take appropriate action to ensure the problem does not re-
occur. If the error persists, and no apparent cause can be identifier,
report the problem to your local DB2 Manager support representative.
OTD22004 Invalid request on Scheduler Queue
Explanation: A request in the scheduler queue is not a valid DB2 Manager request
element. Processing of the request cannot continue. The scheduler
task will continue by waiting for the next request to arrive.
Action: This message indicates an internal error in DB2 Manager processing.
Retain as much information about the error as possible and report the
problem to your local DB2 Manager support representative.
OTD22005 ENQueue Error: Major: mmmmmmmm Minor: nnnnnnnnnnnnnnnn
Return code=X'xx' T=Snnn
Explanation: An error has been received attempting to enqueue on the resource
whose major and minor names are identified in the message. ‘xx’ is
the return code received from the ENQ macro, and ‘nnn’ identifies the
scheduler task receiving the error.
Action: Refer to IBM documentation on ENQ macro processing for a
description of the return code. Take the appropriate corrective action
and re-start the control region. If no apparent cause for the error can
be detected, contact your DB2 Manager product support
representative.