This mandatory parameter is used to specify the subsystem identifier of the DB2 subsystem to be used during execution of the utility. The subsystem identifier ‘xxxx’ can be 1-4 characters in length.

PLAN=xxxxxxxx

This is an optional parameter which is used to specify the DB2 plan name to be used during execution of the utility, where ‘xxxxxxxx’ is the 1-8 character identifier of the plan. If omitted, a default value of OTDBL170 is used. Refer to “Perform DB2 system modifications” on page 25 for information about DB2 Manager plan creation processing.

PRINT=DETAILSUMMARY

This is an optional parameter which is used to control the level of reporting performed by the utility. If a value of SUMMARY is specified for this parameter, the detailed processing report will be omitted. All other print reports will be produced as normal. If the default value of DETAIL is specified, all print reports (including the detailed processing report) will be produced.

SQLIN entry specification

 

The SQLIN file is a fixed-block sequential dataset with a logical record length

 

of 80 bytes. It will contain one or more records containing a free-format SQL

 

SELECT command which will identify the DB2 table to be processed and the

 

key fields in the table. Character positions 1-71 will be used for this

 

description. Contents of character positions 72-80 in each record will be

 

ignored. A maximum of 15 records may be present in this file.

 

The SQL SELECT command should have the general format:

 

SELECT key1, key2, .. .., keyn FROM table_name

 

where ‘key1’, ‘key2’, …., ‘keyn’ are the names of the columns which are used

 

to establish a unique key for each row in the database, and ‘table_name’ is

 

the name of the DB2 table which is to be processed by the utility (ie. the

 

name of the table itself, not the view of the table created during product

 

installation processing)

 

(eg):

 

SELECT ACCOUNT, SUBCODE FROM OTDBTEST.TAB1

 

The database housekeeping utility will cause this statement to be validated

 

by DB2 for correct SQL syntax. Any invalid specification will cause an SQL

 

error to be received by the utility, which will cause it to terminate with a

 

condition code of 12. In these circumstances, the SQL statement should be

 

corrected and the job restarted.

 

Print reports

 

The database housekeeping utility will write a number of print reports to the

 

SYSPRINT dataset during execution. These consist of:

112

DB2 Manager User Guide

 

StorageTek Proprietary

Page 115
Image 115
StorageTek 312564001 manual Ignored. a maximum of 15 records may be present in this file