Load Utility Parameters

Panel

The prompts on the panel are provided to allow users to supply various parameters for the LOAD utility. All values you specify are profiled.

Delete All Rows in Tablespace

Option to delete all rows in the table space and Legacy Tables. Specify:

Y

Delete all rows. Include the REPLACE clause on the LOAD DATA statement.

If you enter YES for this keyword and YES for Create Full Image Copy, the COPY utility will be run during the Load process.

If this option is YES, any table in the Extract File with zero rows will be included in the Load Process, regardless of the value of the Load when Zero Rows User Option.

N

Do not delete rows. Include the RESUME YES or RESUME NO clause depending on entry for next prompt.

Note: If you enter NO for this keyword and YES for Create Full Image Copy, the COPY utility will be run after the Load process.

If NO, Can Tablespace have Rows

Option to require empty table space for the process. This setting is relevant only if the Delete All Rows in Tablespace prompt is NO. Specify:

Y

Table space can have rows. The LOAD DATA statement includes the RESUME YES clause.

N

An empty table space is required. The RESUME NO clause is included.

If YES, ReUse Dictionary

Option to reuse the DB2 Compression Dictionary while performing the Load. For additional information, see your IBM® Utility Guide. Specify:

Y

Reuse the DB2 Compression Dictionary while performing the Load. The LOAD DATA statement includes the KEEP DICTIONARY clause. Y is valid only if a Compression Dictionary exists and the table space has the COMPRESS YES attribute.

N

Do not reuse DB2 Compression Dictionary while performing the Load.

Perform Logging During Load

Option to perform logging during the Load. Note that you can perform logging and create a full image copy during the Load. If you elect to create a full image copy as a separate step after the Load, the Perform Logging During Load setting has no effect. Specify:

Y

Perform logging during the Load. The LOG YES clause is included on the LOAD DATA statement.

N

Do not perform logging during the Load. The LOG NO clause is included. If you enter NO, the table space is placed in COPY PENDING status. Consider entering YES for Reset Copy Pending or Create Full Image Copy.

If NO, Reset Copy Pending

Y

Reset the COPY PENDING flag. Entering YES resets the COPY PENDING flag without establishing a recoverable set of data. To establish a recoverable data set and reset the COPY PENDING flag while performing the Load, enter YES for Create Full Image Copy. Specify:

N

Do not reset the COPY PENDING flag.

Enforce RI Constraints During Load

Option to enforce Referential Integrity constraints during the Load. Specify:

Y

Discard any invalid row that is encountered during the Load. The ENFORCE YES clause is included on the LOAD DATA statement.

N

Include the ENFORCE NO clause on the LOAD DATA statement. This may be desirable if RI cycles are involved because this may be the only way to insert all data.

Referential Integrity is not checked on a row-by-row basis. Instead, the checks are suspended and the table is in “Check Pending” status. (For more information see Check Pending Status.)

Create Full Image Copy

Option to create a full image copy: Specify:

Y

Create a full image copy and reset the COPY PENDING flag.

Note: If you enter YES for Delete All Rows in Tablespace, the COPY utility is run during the Load. If you enter NO for Delete All Rows in Tablespace, the COPY utility will run as a separate step after the Load.

N

Do not create a full image copy. If you enter NO, the table space is placed in COPY PENDING status. Consider entering YES for Reset Copy Pending.

If YES, Number of Local Copies

The number of local copies to be created. This setting applies only if Create Full Image Copy is YES. Specify:

0

No local copies are created.

1

The primary local copy is created.

2

The primary and backup local copies are created.

Number of Remote Copies

The number of remote copies to be created. This setting applies only if Create Full Image Copy is YES. Specify:

0

Remote copies are not created.

1

The primary remote copy is created.

2

The primary and backup remote copies are created.

Invoke RUNSTATS

Option to invoke RUNSTATS in order to ensure that the statistical data required by the DB2 Optimizer is accurately updated. Specify:

Y

Invoke RUNSTATS. RUNSTATS is invoked at the table space level and includes all tables and indexes in the table space.

N

Do not invoke RUNSTATS.

If Yes, Select RUNSTATS method

The method of collecting statistical information. Specify:

I

Collect statistical information during the Load Process.

S

Collect statistical information as a separate step.

If Yes, Produce statistics report

Option for additional report information. Specify:

Y

Provide additional report information.

N

Do not provide additional report information.

Age Date Values

Option to age date values as part of this process. Specify:

Y

Age date values. The Specify Aging Parameters panel is displayed. On this panel, specify aging values to be used. These values supplement the specifications for columns mapped with the AGE function and are used, if requested, to age DATE and TIMESTAMP columns that are not explicit targets of an AGE function.

N

Do not age date values. The specifications for aging on the Column Maps included in the process are ignored.

For additional information, see Age Date Values.

Sort rows on Cluster Index (if it exists)

Option to sort the data by any cluster index. Specify:

Y

Sort data.

N

Do not sort data.

Allow Restart on (Keep Work Datasets)

Option to retain work files to enable restart ability on a specified level. Specify:

W

Retain the files if warnings or errors occur. (The return code is 4 or greater.)

E

Retain the files if errors occur. (The return code is 8 or greater.)

N

Always delete the files when the step completes.

Note that each tablespace is processed in a separate job step and generates a set of work files. This setting applies to each job step.

Also, when a warning occurs, processing continues, but the job is terminated on an error. The processing that precedes the step that generates the error is retained. You must run the load for the succeeding steps.

Display Template Assignments

Option to display a panel for assigning template names to Load files.

Y

Display a pop-up prompting for template names for Load files. Any entry is profiled and remains in effect until you replace it. Entries must reference a file in the template library defined at installation or an error occurs at execution. The Load program uses parameters from the template to dynamically allocate the file, rather than a DD statement.

N

Do not display the pop-up. N is the default setting. Any earlier template assignments remain in effect for this execution.

Sort Work File Unit

Option to dynamically allocate work files required by the sort program. When you enter a value for this keyword, the SORTDEVT keyword is included in the Load statement. If you do not supply a value, DD statements for the required files are generated in the job stream.

Number of Sort Work Files

The number of work files for the sort program. When you enter a value, the SORTNUM keyword is included in the Load statement. Specify:

1-99

Any value in this range.

blank

Use default value.

Stop if there are 'N' Discards

The maximum acceptable number (1 through 2147483647) of discarded rows. Specify:

1

Terminate the Load Process if any rows are discarded.

>1

Terminate the Load Process when the specified number of rows are discarded.

Review Propagation Key Sets

Option to display the Propagating Key Set(s) panel before the Load Process is performed. This option is presented only when the PROP function is used in one or more Column Maps used by the Load Process. Specify:

A

Always display the panel prior to performing the process.

E

Display the panel prior to performing the process if the PROP specifications are in error.

For additional information, see View PROP Specifications.

Review or Save JCL Before Job Submission

Option to review the JCL and control statements prior to job submission. Specify:

N

Submit job, do not display or save the JCL and control statements.

R

Display the JCL and control statements for review prior to job submission. The JCL and control statements are displayed in the ISPF editor, where you can modify them and save them to submit later.

S

Save the JCL and control statements. Prompts are provided for you to specify the name of a file in which to store the JCL and control statements.

Process Report Type

The level of information to be included in the Load Process Report. Specify:

D

Display a detailed report that includes Column Map information.

S

Display summarized information in the report.

Force all LOB data to External PDSE

Indicates whether Large Object (LOB) data from the Archive or Extract File is always to be stored in a Partitioned Data Set - Extended (PDS/E) dataset. When LOB data is stored in a PDS/E dataset, the Load Utility input file (SYSREC) does not contain LOB data. Instead, the Load Utility input file contains reference pointers that point to the PDS/E dataset and member name in which each instance of LOB data is stored. Storing LOB data in a PDS/E dataset reduces the length of table rows in the Load Utility input file. In turn, this allows the Load Utility to load table rows that would otherwise be too long to load. Specify:

Y

Always store LOB data from the Archive or Extract File in a PDS/E dataset that is separate from the Load Utility input file.

N

Store LOB data from the Archive or Extract File in a PDS/E dataset only when the Load Utility input file would otherwise contain table rows that are greater than 32 KB in size (default).

Generate SYSTEMPERIOD override

When a Temporal table is selected as the target in CM processing, Optim™ will provide the ability to “override” the GENERATED ALWAYS timestamp columns with values from the extract/archive file or values specified by the user.

Load DSN Prefix

Data set name prefix for all loader and field specification files. Specify a prefix up to 35 characters following standard data set naming conventions. This parameter allows Optim to create the required field specification files dynamically during load preparation, instead of statically during JCL generation. When you specify this parameter, field specification statements for all loaded tables and their associated data are stored in dynamically allocated data sets, named as:

dsnprefix.Lseq

For loader files, where dsnprefix is the prefix specified with this parameter and seq is a unique sequential number assigned by Optim.

dsnprefix.Xseq

For field specification files, where dsnprefix is the prefix specified with this parameter and seq is a unique sequential number assigned by Optim.

Generate Disk/Tape compatible JCL

Indicate the media compatibility mode for the input ARCHIVE or EXTRACT file when located on TAPE.

N

(Default) The generated JCL is compatible with JCL generated with Optim code in releases before 11.7 and before APAR PH64152. When the EXTRACT, or ARCHIVE, file resides on tape, the generated JCL might be different from the JCL generated when such data set resides on disk. The order of tables listed in the TM and the order of the load steps, as well as the order of the related DD statements, might be different. With this default, the generated JCL might be sensitive to the type of media on which the input EXTRACT, or ARCHIVE, file resides.

Y

The generated JCL is the same irrespective of the media on which the input EXTRACT, or ARCHIVE, file resides. Such JCL may not be executed with Optim code at the PTF level before APAR PH64152. Note that the generated JCL will contain the DISKTAPE_COMPAT YES control keyword reflecting the option's value.