JCL Considerations

Utility Statements › LOAD › JCL Considerations

JCL Considerations

When you submit a LOAD statement to CA IDMS/DB through the batch command facility, the JCL to execute the facility must include statements to define:

The dictionary containing table definitions
The files containing the areas associated with the tables being loaded
The intermediate work files
Sort work files, if doing a complete LOAD

LOAD utility uses intermediate work files

Each step of the load process produces intermediate work files to be used by later steps. If you run a complete LOAD without separating steps or phases, the LOAD utility sorts data in the intermediate files between the steps automatically. If you run a phased or stepped LOAD, you must run the intermediate sorts.

Note: When running a complete or phased LOAD, SYS002 andSYS003 must point to the same intermediate file. When the database being processed is so large that the intermediate file must be a multi-volume data set, it is required that all extents be physically allocated before jobstep initiation. If this is not possible, then a stepped LOAD should be used. When running a stepped LOAD, SYS002 and SYS003 must point to different intermediate files. The data that is output in SYS003 by each step is input to the next step in SYS002.

The following table shows the output of LOAD STEP1 and LOAD STEP2:

Step	Output	Size
STEP1 (WITH PRESORT)	SYS003	For each record: (MAX SORT CONTROL KEY SIZE) + (MAX FOREIGN KEY SIZE) + (MAX SCHEMA RECORD SIZE) + 24
	SYSPCH contains sort parameters	80 bytes
STEP1 (WITHOUT PRESORT)	SYS003	For each record: (MAX SORT CONTROL KEY SIZE) + (MAX FOREIGN KEY SIZE) + 24
	SYSPCH contains sort parameters	80 bytes
STEP2	SYS003	For each record: (MAX SORT CONTROL KEY SIZE) + (MAX FOREIGN KEY SIZE) + 24

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