Utility Statements › FASTLOAD › JCL Considerations

JCL Considerations

When you submit a FASTLOAD utility through the batch command facility, the JCL to execute the facility must include statements to define:

• Files containing the areas to be loaded
• The intermediate work files
• Sort space

Note: For more information about the generic JCL used to execute the batch command facility, see the chapter for your operating system in this guide.

Intermediate work files

The following tables indicate which work files are created and read by the different utility steps depending on the use of the SORTEXIT and REUSE WORKFILE options.

Note: The RELDCTL file is read in steps IDMSDBL2, IDMSDBL3, and IDMSDBL4.

Work file JCL Considerations for STEP mode

FASTLOAD normally runs as a single step but runs as separate steps using the "STEP step-name" syntax. When running in step mode, input files should have dispositions to state that the file already exists, for example, "DISP=OLD."

Preserve output files on successful completion but not when the job fails, for example, "DISP=(NEW,CATLG,DELETE)."

See the "Intermediate Work File" table to determine which files are input and which files are output and when they are used.

The RELDCTL file is always input to every step.

The SYSPCH file is created by an IDMSDBLx step and used as input to a SORTx step. When used as input, it is defined as SYS001.

Work file record lengths:

• The RELDCTL file is a fixed length file with a record length of 60 bytes.
• The SYSPCH file is a fixed length file with a record length of 80 bytes.
• All SYSxxx files are variable length files. The record length can vary from one step to the next, from one job to the next. Do not code an LRECL value in the JCL, just code a BLKSIZE value. A BLKSIZE value should be chosen based on the optimal size for the device being used, for example, 1/2 track if disk or 32k if tape.