Skip to Content

 

  

Information
Limited support BMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see ALTER and BMC AMI Change Manager for Db2 13.1.

JCL types

You can build the following types of JCL:

  • Initial JCL

    Initial JCL initially starts the job. The JCL is built to run the job for the first time from the worklist. The disposition of the data sets to be allocated is set to NEW.

  • Restart JCL

    Restart JCL restarts the job after it fails or stops with the -STOP command. You can build restart JCL from existing JCL. The product scans the previous JCL and worklist and modifies the file dispositions. In addition, the product preserves any data set name changes that were made to the old JCL and eliminates data set sizing and symbolic variable substitution. To restart the worklist, the product reads the sync table.

    In the course of executing a worklist, output is created in the form of records being inserted into the sync table. Sync table records are used as progress indicators during execution of a worklist and as a means of committing work to Db2. These records are used by Execution to restart or resume a job that has failed or has been stopped. (For more information about sync tables, see Sync-tables.)

    For more information about restarting a worklist, see Overview-of-the-restart-process.

  • Startover JCL

    Startover JCL executes the job from the beginning of the worklist or after the -STOP worklist command, depending on the type of worklist that you are processing.

    • If you are processing an alter-type worklist or a single-phase migrate-type worklist, startover JCL starts the job over from the beginning of the worklist after it has failed.
    • If you are processing a two-phase migrate-type worklist on the sending subsystem, the JCL starts over from the beginning of the worklist.
    • If you are processing a two-phase migrate-type worklist for a receive-type work ID on the receiving subsystem, the JCL starts after the -STOP command, which is the beginning of the second phase of the worklist. For more information about receive-type work IDs, see Creating-a-receive-type-work-ID.
Warning

Note

You can insert the -GOTO command after the first -SYNC command in the worklist, or in phase 2 of a migrate-type worklist on the receiving subsystem, to allow processing to start at a specified sequence number. For more information about the -GOTO command, see GOTO-Bypass-command.

You can build startover JCL from existing Execution JCL. The product scans the previous JCL and modifies the file dispositions. In addition, the product preserves any data set name changes that were made to the old JCL and eliminates data set sizing and symbolic variable substitution.

For more information about starting a worklist over, see Overview-of-the-startover-process.

Related topic

Execution-of-changes

 

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

ALTER and BMC AMI Change Manager for Db2 12.1