Filter
Top Products
DB2 Manager User Guide 25
StorageTek Proprietary
To avoid any unnecessary and unpredictable delays due to this situation, any
automated operator reply facility which is present on the host system should
be configured to reply 'CANCEL' to the above message for any DB2 Manager
retrieval request (ie) a request for retrieval from an Archive Manager tape
dataset.
DB2 Manager will handle a reply of 'CANCEL' in the following manner:
1. For row retrieval requests, a ‘resource unavailable’ response will be
raised by DB2 Manager. An SQL –652 error is then returned to the caller
and a reason code placed field SQLERRD(6) in the SQLCA (refer to
chapter 7 of this manual for a description of these codes), or optionally
the request will be held internally in DB2 Manager until a tape drive
becomes available or until a customer-specified time interval has elapsed
(at which time the request will be rejected as above). For rejected
requests, the calling application may be amended to handle this type of
error in a special manner (eg) to display a retry message to the end user.
2. For row migration requests, DB2 Manager will retry the allocation at one-
minute intervals, up to a retry limit of 30. If, after this limit has been
reached, allocation has still not been successful, an error is returned to
the DB2 Manager migration utility, and the program will terminate.
Perform DB2 system modifications
DB2 Manager requires its own DB2 database for execution. This database
must be defined in all DB2 systems which are to be used by DB2 Manager
and the appropriate authorities granted before the product can be used.
Each DB2 system must also be updated with details of the plan(s) required
by DB2 Manager. The following activities will need to be performed:
a. Create LCDDB2 system database and grant access authorities.
DB2 Manager uses its own database for retention of internal information.
This is a DB2 database containing the following tables:
• LCDDB2.REGISTRY. This table is used for registration of tables which
have been enabled for row migration, and identifies the Archive Manager
database used for storing migrated rows from each of the tables. It is
automatically maintained during DB2 Manager migration processing.
• LCDDB2.PLAN_TABLE. This table is used internally by DB2 Manager for
DB2 EXPLAIN processing when validating customer-specified row
selection criteria.
During normal operation, DB2 Manager will need to access and update
resources in its system database. The following table identifies these
database resources and the level of access required to each.