Use the DB Alias tab to define the parameters needed for the IBM® DB2® for z/OS® loader. The availability of certain options and fields might be
dependent upon your entries for related options and fields on the
tab. Use the FTP Options to automatically transfer
the files to the FTP server and optionally run the loader.
Mode
- Replace entire Tablespace
- Delete all rows in the table space before the load
is processed.
- Resume
- Do not delete existing rows in the table space when
the load is processed.
Sysin Load Statement Options
- Perform Logging during Load
- Use Single Load Data File
- When all the tables are to be loaded in the same
table space, group all tables to be converted into a single data file.
Do not create a file for each table.
- Run inline Runstats
- To ensure that statistical data is accurate, run
RUNSTATS at the table space level and include all tables and indexes
in the table space.
- Produce Statistics Report
- Produce report of RUNSTATS.
- Enforce RI during Load
- Verify RI constraints when loading data into dependent
tables. Before the database can be used, RI enforcement determines
that RI is intact. For example, that parent rows exist for all rows
inserted into a child table.
- Load When Source is Empty
- Complete the load if a table to be loaded contains no rows, deleting
any rows from the target. If not selected, empty source tables are
skipped.
- Target Code Page
- The code page needed to ensure accurate character
translation for the DB2 environment.
- Discard Limit
- The number of rows (up to 999999999) that the loader
can discard because of errors. Stop processing when the specified
number of rows is discarded.
- To end the process
if a single row is discarded,
specify 1 as the maximum.
- To allow an unlimited
number of rows to be discarded,
specify zero (0) or leave blank.
FTP Options
- Transfer File to z/OS
- Transmit files to the FTP server after successfully
converting the data. Select this check box to enable the remaining FTP Options.
- Submit Job on z/OS
- Submit the generated JCL after transmitting the
files. The job number is provided in informational messages in the
load process report. You can determine the status of the job by signing
onto z/OS and locating the
job in the JES spool.
- Review Generated JCL
- If Submit Job on z/OS is
selected, display the generated JCL before the job is submitted.
- Save Generated JCL on z/OS
- Save the JCL so that you can run the job manually.
- Use FTP login from Personal Options
- Use FTP login credentials from the Load tab in Personal Options, not login information in the FTP Options.
- FTP Server
- A TCP/IP address or FTP server name.
- Port
- The port used by the solution to open a connection.
Enter 0 to use the default.
- User ID
- User ID to access the FTP server.
- Password
- Password for the FTP server.
- z/OS Dataset
Qualifier
- Qualifiers for the data set name. The name is prefixed
with the user ID and the qualifiers. A single quotation mark as the
first character indicates that all transmitted data set names are
fully qualified and are not prefixed with the user ID. The data set
name cannot exceed 44 characters. The last two qualifiers require
up to 12 characters (the first eight characters of the file name and
four characters for a unique generated file number). For example, userID.qualifier.FileName.X001.
- JCL Template
- The name of the file used to construct the generated
JCL.
A template file, RT/Samples/JCL/LOADDB2.JCL, is distributed with the Optim™ solutions. You can copy this file to your default data directory
and modify the JCL appropriately.
Work path for interim files
The path for the temporary loader files on your workstation
or network server.
Viewing File
Review the generated JCL in the Viewing File dialog. Click OK to submit the job. If you
click Cancel, the job is not submitted but
the transmitted files remain on the z/OS system, and you can run the job manually.