StorageTek Lifecycle Director DB2 Manager 312564001 User Manual

Page of 189
 
110 
DB2 Manager User Guide 
 StorageTek 
Proprietary 
migrated rows in the DB2 table will be resolved by the utility.  This is required 
to ensure that re-organization of non-archive partitions can occur without 
reference to migrated rows in the Archive Manager database. 
The table to be processed is identified by the customer via an SQL 
command. Execution of the program is controlled via a series of parameters 
in file SYSIN. 
A print report is issued by the utility giving details of the execution 
parameters, and detailed and/or summary information about objects which 
have been deleted from Archive Manager.   The detailed report will contain 
one entry for each object which has been deleted from the Archive Manager 
database.  Each entry will contain the key of the Archive Manager object. 
Functions 
The DB2 Manager database housekeeping utility performs the following 
functions: 
•  It will process and validate a series of execution parameters from file 
SYSIN, and a table identification parameter from file SQLIN which will 
govern execution of the utility.  The utility will then obtain information from 
DB2 about the table to be analyzed. 
•  It will sequentially scan the DB2 table identified in the SQLIN file, and for 
each migrated row will record information about the Archive Manager 
database object containing the migrated row.  No access to the migrated 
rows themselves is required during the procedure. 
•  When all rows have been scanned, the utility will analyze the collected 
information to identify objects in the Archive Manager database which no 
longer contain any active migrated rows.  It will issue a standard Archive 
Manager object deletion request for each such object.   An entry may 
optionally be written to the detailed processing report for each deleted 
objects. 
•  At the end of processing, a report will be produced giving a summary 
analysis of the rows in the DB2 table and the objects deleted from the 
Archive Manager database. 
JCL requirements 
The following JCL may be used to execute the utility: 
//* 
//STEP170  EXEC PGM=OTDBP170,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=Table.identification.file,DISP=SHR    
//SYSPRINT  DD  SYSOUT=* 
//*