StorageTek 312564001 User Manual
DB2 Manager User Guide
85
StorageTek
Proprietary
at the first commit point (as controlled via the COMMIT parameter) after
reaching this value. ‘nnnnnn’ must be a 1-6 digit numeric value in the
range 0-999999. A value of 0 indicates that there is no maximum to the
number of rows to be migrated during execution of the utility. If this
parameter is omitted, a default value of 0 is used.
reaching this value. ‘nnnnnn’ must be a 1-6 digit numeric value in the
range 0-999999. A value of 0 indicates that there is no maximum to the
number of rows to be migrated during execution of the utility. If this
parameter is omitted, a default value of 0 is used.
•
TIME=nnnn|0
This is an optional parameter specifying the maximum time for which
execution of the utility is to continue. The utility will terminate processing
at the first commit point (as controlled via the COMMIT parameter) after
reaching this value. ‘nnnn’ must be a 1-4 digit numeric value in the range
0-999999. A value of 0 indicates that there is no maximum to the
execution time of the utility. If this parameter is omitted, a default value of
0 is used.
SQLIN entry specification
The SQLIN file is a fixed-block sequential dataset with a logical record length
of 80 bytes. It must contain one or more records containing a free-format text
description of the rule(s) to be used for selection of objects to be migrated
from DB2 to Archive Manager. 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 the SQLIN file.
of 80 bytes. It must contain one or more records containing a free-format text
description of the rule(s) to be used for selection of objects to be migrated
from DB2 to Archive Manager. 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 the SQLIN file.
Rules for migration are specified in the format of a standard DB2-compatible
SQL SELECT command, which must have the general format:
SQL SELECT command, which must have the general format:
SELECT key1, key2, .... keyn FROM table_name
WHERE migration_criteria
where ‘key1’, ‘key2’, …. ‘keyn’ are the names of the columns which are used
to establish a unique key for each row in the database, ‘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), and ‘migration_criteria’ are the criteria specified by the user for
selection of rows which are to be eligible for migration to Archive Manager
(eg):
to establish a unique key for each row in the database, ‘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), and ‘migration_criteria’ are the criteria specified by the user for
selection of rows which are to be eligible for migration to Archive Manager
(eg):
SELECT ACCOUNT, SUBCODE FROM OTDBTEST.TAB1
WHERE DATE < ’01.02.1997’
Note that migration criteria are specified using the standard DB2-compatible
SQL criteria specification format.
SQL criteria specification format.
A unique key must exist for each row in the database in order for it to be
eligible for archival by the utility. The maximum number of key fields which
may be specified is 8. Any valid SQL selection criteria may be entered in
order to identify rows which are to be eligible for migration.
eligible for archival by the utility. The maximum number of key fields which
may be specified is 8. Any valid SQL selection criteria may be entered in
order to identify rows which are to be eligible for migration.
The archival 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.
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.