StorageTek Lifecycle Director DB2 Manager 312564001 User Manual
104
DB2 Manager User Guide
StorageTek
Proprietary
o Primary key and archive date of the object containing the row to be
pre-fetched
o Return and supplementary codes received from Archive Manager
after processing the request
o The concatenated key of the DB2 row to be pre-fetched
Note that there may be multiple entries in this report for the same Archive
Manager object, if multiple rows within that object have been selected for
pre-fetch processing. Repeated requests for pre-fetching of the same
object will be ignored by Archive Manager.
Manager object, if multiple rows within that object have been selected for
pre-fetch processing. Repeated requests for pre-fetching of the same
object will be ignored by Archive Manager.
• Summary processing report. At end of processing, the utility will write
the summary processing report. This will contain the following
information:
information:
o Number of rows selected for pre-fetching
o Number of DB2 error conditions received
o Total number of pre-fetch requests issued
o Number of pre-fetch requests accepted by Archive Manager
o Number of rows which were already pre-fetched
o Number of pre-fetch requests rejected by Archive Manager
o Number of batches successfully processed
o Number of batches processed with errors
o Number of DB2 error conditions received
o Total number of pre-fetch requests issued
o Number of pre-fetch requests accepted by Archive Manager
o Number of rows which were already pre-fetched
o Number of pre-fetch requests rejected by Archive Manager
o Number of batches successfully processed
o Number of batches processed with errors
Condition codes
The pre-fetch utility will set a condition code on completion. This code may
take the following values:
take the following values:
0 -
the utility has been executed successfully.
4 -
a warning condition has been encountered during processing
of the utility. A warning message will have been written to the
SYSPRINT dataset. The utility has been executed
successfully.
of the utility. A warning message will have been written to the
SYSPRINT dataset. The utility has been executed
successfully.
8 -
an error condition has been encountered during processing of
the utility. An error message will have been written to the
SYSPRINT dataset. Execution of the utility has continued.
the utility. An error message will have been written to the
SYSPRINT dataset. Execution of the utility has continued.
12 -
a serious error has been encountered during processing of the
utility. An error message will have been written to the
SYSPRINT dataset. Execution of the utility has been
terminated.
utility. An error message will have been written to the
SYSPRINT dataset. Execution of the utility has been
terminated.
Utility failure and restart considerations
If the pre-fetch utility fails to complete successfully (return code greater than
8), consult the error report in the SYSPRINT dataset to identify the cause of
the problem. Refer to chapter 7 for a description of the message(s)
appearing in the error report. Rows in all batches successfully processed
prior to the point of failure will have been successfully pre-fetched to disk
storage by Archive Manager.
8), consult the error report in the SYSPRINT dataset to identify the cause of
the problem. Refer to chapter 7 for a description of the message(s)
appearing in the error report. Rows in all batches successfully processed
prior to the point of failure will have been successfully pre-fetched to disk
storage by Archive Manager.