MVS load job steps

This section describes the steps in the load job when you include MVS objects in the load process.

  1. VSAMALOC—Pre-allocate VSAM files for JES3 (IDCAMS)

  2. VSAMCRTE—Delete and/or Define VSAM Files (IDCAMS)This step creates any new VSAM clusters that did not exist at the time of the interactive portion of the Load function.

    This step also deletes the existing VSAM clusters if the Delete/Define load option was set to YES.

  3. FILEDLTE—Delete Non VSAM files (IDCAMS)This step deletes the existing non-VSAM files if the Delete/Define load option was set to YES.
  4. FILEALLC—Allocates the Non-VSAM files that did not exist during the interactive load process or that have been deleted when the Delete/Define option was set to YES. (IDCAMS)

  5. CLEAN1ST—File Cleanup (IDCAMS)

    This step deletes any existing files that are to be created in this job. This enables you to keep and rerun a JCL stream.

  6. LDDRV—Load Driver (XFREXEC)This step checks user authorization for subsequent steps and separates the extract file into multiple files, one file per object to be loaded.

  7. SORTnnn—File Sort Utility (SORT) or ICETOOL Multiple File SortThis step sorts a file containing the data to be loaded in the associated LDMVSIN step.

    The sort sequence is based on the clustering index for that object. If no clustering index exists, sort sequence is based on the primary index for that object. If no primary index exists, sort sequence is based on the first-defined index for that object.

    This step is generated and executed for each object to be loaded (SORT), or once for all files to be loaded (ICETOOL).

  8. LDMVSIN—MVS Insert (XFREXEC)This step generates and executes the DELETE and INSERT statements to load data into objects from the sorted files created in step 4. If you specified YES in the Del All column for an object, all data in that file will be deleted before the extracted data will be inserted.

    If you specified Yes in the Replace Matches field on the Insert/Load Option screen and the target object contains a unique key, File-AID/RDX will replace existing data in the target object with data from the extract file. If you specified No in the Replace Matches field and the target object contains a unique key, File-AID/RDX will discard data that already exists in the target object.

  9. CLEANLST—File Cleanup (IDCAMS)This step deletes all File-AID/RDX temporary files used in this job. Deleting these files in the last job step enables the job to be restarted in any prior step.

  10. CLEANCTL—File Cleanup (IEFBR14) - OptionalThis step deletes the File-AID/RDX control card PDSEs. Whether step CLEANCTL is commented out or executed is determined by the global job option Delete in-stream data datasets at EOJ. If the job option is set to NO, File-AID/RDX

     control card PDSEs created in the load and delete jobs will NOT be deleted. Keeping the data sets until all steps run successfully allows for the restarting of the JCL at any step.

  11. CLEANEXT—File Cleanup (IDCAMS) - OptionalThis step deletes the File-AID/RDX EXTPARMS parameter file. Whether step CLEANEXT is commented out or executed is determined by the global job option Delete in-stream data datasets at EOJ. If the job option is set to NO, File-AID/RDX

     EXTPARMS files created in the load and delete jobs will NOT be deleted. Keeping the data sets until all steps run successfully allows for the restarting of the JCL at any step.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*