StorageTek 312564001 User Manual

Page of 189
 
100 
DB2 Manager User Guide 
 StorageTek 
Proprietary 
expiration of this time interval.   Refer to the Lifecycle Director Archive 
Manager User Guide for information about setting pre-fetch retention periods 
in a database, and about executing the object management utility. 
Functions 
The DB2 Manager pre-fetch utility performs the following functions: 
•  It will process and validate a series of execution parameters from a 
SYSIN file, and an SQLIN row selection parameter which will govern 
execution of the utility.  The utility will then obtain information from DB2 
about the table from which the rows to be pre-fetched were migrated. 
•  It will scan the DB2 table, and select migrated rows for pre-fetching in the 
Archive Manager database which satisfy the selection criteria specified in 
the SYSIN dataset.   
•  For each selected row, a pre-fetch request will be passed to Archive 
Manager requesting that the object containing the selected row be copied 
from tape to disk, using the standard pre-fetch application program 
interface supplied by that component.  If detailed print reporting has been 
requested an entry will be written to the report file giving details of the 
request passed to Archive Manager and the result of that request.   
•  When the number of requests accepted by Archive Manager has reached 
the batch size specified in the execution parameters, the program will 
issue a request to Archive Manager to process the batch.  This will cause 
Archive Manager to sort all requests in the batch into the most efficient 
sequence for retrieval from tape, and to create disk copies of each object 
in the batch.   Note that the same object may appear multiple times in 
each batch, if multiple rows within that object have been selected for pre-
fetch processing.   Archive Manager will ignore duplicate object requests 
in the batch. 
•  After all rows in the table have been processed in this manner, a report 
will be produced giving the total number of rows which have been pre-
fetched. 
JCL requirements 
The following JCL may be used to execute the utility: 
//* 
//STEP130  EXEC PGM=OTDBP130,REGION=4096K 
//*     
//STEPLIB   DD  DSN=Database.Manager.load.library,DISP=SHR         
//          DD  DSN=Archive.Manager.load.library,DISP=SHR 
//*          
//OTASxxxx  DD  DSN=Archive.Manager.index.dataset,DISP=SHR 
//SYSIN     DD  DSN=Execution.parameter.file,DISP=SHR    
//SQLIN     DD  DSN=Pre-fetch.criteria.file,DISP=SHR    
//SYSPRINT  DD  SYSOUT=* 
//* 
DD entries should be specified as follows: