StorageTek Lifecycle Director DB2 Manager 312564001 User Manual
DB2 Manager User Guide
97
StorageTek
Proprietary
This is an optional parameter specifying the number of secondary extent
blocks to be used during allocation of temporary dataset OTDBS120 used
during execution of the utility. ‘nnnnnnn’ is a 1-7 digit numeric value in
the range 1-8388607. If omitted, a default value of 10000 will be used.
The length of each block will be equal to 100 times the concatenated field
lengths of the table columns which are used to uniquely index each row in
the table (see “SQLIN entry specification” on page 97 for a discussion of
the unique index requirement).
blocks to be used during allocation of temporary dataset OTDBS120 used
during execution of the utility. ‘nnnnnnn’ is a 1-7 digit numeric value in
the range 1-8388607. If omitted, a default value of 10000 will be used.
The length of each block will be equal to 100 times the concatenated field
lengths of the table columns which are used to uniquely index each row in
the table (see “SQLIN entry specification” on page 97 for a discussion of
the unique index requirement).
•
S120UNIT=xxxxxxxx
This is an optional parameter specifying the unit name to be used for
allocation of temporary dataset OTDBS120 used during execution of the
utility. ‘xxxxxxxx’ is any valid disk or VIO unit name. If omitted, a default
value of ‘VIO’ is used.
This is an optional parameter specifying the unit name to be used for
allocation of temporary dataset OTDBS120 used during execution of the
utility. ‘xxxxxxxx’ is any valid disk or VIO unit name. If omitted, a default
value of ‘VIO’ 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 rows to be restored from
Archive Manager to DB2. 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 rows to be restored from
Archive Manager to DB2. 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 row restore are specified in the format of a standard DB2-
compatible SQL SELECT command, which must have the general format:
compatible SQL SELECT command, which must have the general format:
SELECT key1, key2, .... keyn FROM table_name
WHERE row_restore_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 ‘row_restore_criteria’ are the criteria specified by the user
for selection of rows which are to be restored 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 ‘row_restore_criteria’ are the criteria specified by the user
for selection of rows which are to be restored to Archive Manager (eg):
SELECT ACCOUNT, SUBCODE FROM OTDBTEST.TAB1
WHERE ACNO = ‘123456789’
Note that row restore criteria are specified using the standard DB2-
compatible SQL criteria specification format. Note also that where more than
one unique index exists for the table, keys from any of these indexes may be
used in the SELECT statement. In these circumstances, the choice of
unique key(s) should be influenced by the search argument, in order to allow
selection of rows for restore to be performed via INDEXONLY processing
where possible.
compatible SQL criteria specification format. Note also that where more than
one unique index exists for the table, keys from any of these indexes may be
used in the SELECT statement. In these circumstances, the choice of
unique key(s) should be influenced by the search argument, in order to allow
selection of rows for restore to be performed via INDEXONLY processing
where possible.
The row restore 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.
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.