Reason code Explanation (hex)

Action: Refer to IBM documentation on the LOCASCB macro for a description of the error. Take the appropriate corrective action before continuing with DB2 Manager processing.

0A00

A request has been unable to obtain exclusive access to the DB2

 

Manager control region scheduler lock within the time interval set in

 

the READTIMEOUT or WRITETIMEOUT initialization parameter

 

(depending on type of request).

 

Action:

This condition normally indicates a problem with the

 

 

 

control region. Issue a series of operator summary

 

 

 

display commands (see page 51) to display the current

 

 

 

condition of the scheduler lock. If this indicates that it is

 

 

 

unlocked, re-try the request. If it is consistently locked,

 

 

 

review the control region joblog for other error messages.

 

 

 

If no reason for the error can be identified, report the

 

 

 

problem to your local DB2 Manager support

 

 

 

representative. To relieve the condition, perform an

 

 

 

immediate stop on the control region and restart the

 

 

 

region.

0B00

A migrated row has been accessed by the row migration utility

 

OTDBP100.

 

Action:

This is a normal condition when running an DB2 Manager

 

 

 

utility program, and will be handled by the program. This

 

 

 

error should not occur when executing any other type of

 

 

 

program.

0C00

Field TCBUSER was not correctly initialized during DB2 Manager

 

utility processing. The utility job will terminate with an error.

 

Action:

This indicates an internal DB2 Manager error. Report the

 

 

 

problem to your local DB2 Manager support

 

 

 

representative.

0Dxx

A problem has occurred attempting to communicate with the DB2

 

Manager control region. The second byte of the reason code (‘xx’)

 

will contain a two-digit explanation code, as follows:

 

01 -

An invalid DB2 Manager communications table was found by the

 

 

row edit procedure OTDBP300.

 

 

Action: This indicates an internal error in DB2 Manager

 

 

 

processing. Stop and restart the control region to try to

 

 

 

clear the error condition. If this does not work, report the

 

 

 

problem to your local DB2 Manager support

 

 

 

representative.

 

02 -

The name of the DB2 Manager control region held in the ASCB

 

 

addressed by the row edit procedure OTDBP300 does not

 

 

match that of the control region at start-up time.

 

 

Action: This indicates an internal error in DB2 Manager

168

 

 

DB2 Manager User Guide

 

 

 

StorageTek Proprietary

Page 171
Image 171
StorageTek 312564001 manual Action