Optim™ can create
load and SQL statement files to support the z/OS® loader. Use the DB Alias tab
in the Load Request Editor to define the specific
parameters needed to create the files.
The FTP Options on
the Load Request Editor allow you to automatically
transfer the files to the z/OS FTP
server and optionally run the loader.
Mode
- Replace entire Tablespace
- Select this check box to indicate that all rows
in the table space should be deleted before the Load Process is performed.
- Resume
- Select this check box to indicate that existing
rows in the table space should not be deleted when the Load Process
is performed.
Sysin Load Statement Options
- Perform Logging during Load
- Indicates
whether to perform logging during the load.
- Use Single Load Data File
- Indicator for grouping all tables to be converted
into a single data file, instead of using an individual file for each
table.
Note: You can only use a Single Load Data File when all the
tables are to be loaded in the same tablespace.
- Run inline Runstats
- Invokes RUNSTATS to ensure that statistical data
is accurately updated. RUNSTATS is invoked at the tablespace level
and includes all tables and indexes in the tablespace.
- Produce Statistics Report
- Produce report of Runstats, when Run
inline Runstats is selected.
- Enforce RI during Load
- Indicates whether data can be loaded into dependent
tables without verification of RI constraints. Before the database
can be used, RI enforcement determines that the load has not violated
RI rules. For example, proper parents must exist for all rows inserted
into a child table.
- Load When Source Is Empty
- Select this check box to perform the load if a table to be loaded
contains no rows. If you do not select this check box, any tables
in the Extract File containing no rows will be skipped in the load
phase. Using load with an empty source table deletes rows from the
target table, resulting in a clean test environment.
To create
a clean test environment:
- For an existing target table, use
- Load When Source Is Empty
- an empty source table
- Replace entire Tablespace mode
- For a newly created table, use
- Load When Source Is Empty
- an empty source table,
- Resume mode
- Target Code Page
- Specify the target code page to use for proper character
translation for the DB2® z/OS environment.
- Discard Limit
- Enter the number of rows up to 999999999, that the
loader can discard during the Load Process. The process stops when
the specified number of rows is discarded.
- To end the process if a single row is discarded,
specify 1 as the maximum.
- To set no limit to the number of rows that can be
discarded, specify zero (0) or leave blank.
FTP Options
- Transfer File to z/OS
- Indicator for transmitting files to the FTP server
after successfully converting the row data. Select this check box
to enable the remaining FTP Options.
- Submit Job on z/OS
- Indicator to submit the generated JCL to z/OS after Optim transmits the required files. The job
number is provided in the Informational Messages of the Load Process
Report.
Note: Optim does not
return any output from the actual job. You can, however, determine
the status of the job by signing onto z/OS and
locating the job in the JES spool.
- Review Generated JCL
- Indicator to display the Viewing File dialog
to review the generated JCL after the files have been transmitted
to the z/OS machine but before
the job is submitted.
Note: This option is available only when Submit
Job on zOS is selected.
- Save Generated JCL on z/OS
- Indicator to save the JCL to z/OS, allowing you to run the job manually.
- Use FTP login from Personal Options
- Indicator to use FTP login information on the Load tab
in Personal Options instead of the login information in the FTP Options.
- FTP Server
- Enter a TCP/IP address or z/OS FTP server name.
- Port
- Enter the port used by Optim to open a connection. Enter 0 to use
the default.
- User ID
- Enter a z/OS FTP
server User ID.
- Password
- Enter the password for the z/OS FTP server User ID.
- z/OS Dataset
Qualifier
- Enter the DSN qualifier(s). The dataset is prefixed
with the User ID and the qualifier(s). Use a single quote as the first
character to indicate that all datasets transmitted to z/OS are fully qualified and will not be prefixed
with the User ID.
The total length of the dataset
name cannot exceed 44 characters. The last two qualifiers of the dataset
require up to 12 characters (the first 8 characters of the Extract
File name and 4 characters for a unique generated file number). For
example, ‘userID.qualifier.FileName.X001.'
- JCL Template
- Enter the name of the file used to construct the
generated JCL submitted to z/OS.
A template file, LOADDB2.JCL, is distributed with Optim in the RT/Samples/JCL directory.
It is recommended that you copy this file to your default data directory
and modify the JCL to meet the requirements at your site.
Work path for interim files
Specify a directory path for storing the temporary loader
files on your workstation or network server.
Viewing File
The Viewing
File dialog displays the generated JCL for review. Click OK to
submit the job. If you click Cancel, the job
is not submitted; however, the transmitted files remain on the z/OS machine, and you can run the
job manually.