AMT JCL Script

Batch ID

The batchId can be passed from a parent job into the JCL script. It is thereafter possible to use the Batch ID's value to start the new program job. If no batchId was provided before starting a JCL script, a UUID is automatically generated for batchId.

Configuring a JCL Script for Restart

When a JCL script is configured to be restartable, a restart log file is created to store which cycle file was added when running the script. This restart log file is made unique by adding the Batch ID into the filename. This enables a user to restart a specific instance of a script that has run. The restart log files are stored in the ..<AMT_Root>/Extracts/RestartLog folder with the following filename specification: <script_name>_<batch_id>.json.

Two parameters can be passed to create restarting conditions:

restartat
Use parameter --restartat to specify the step at which the job should restart. Use the following syntax to restart a job at a specific step:
--restartat=<JobStepName>.ProcStep.

Jobs with a step that has no step name can be restarted from the step using the following syntax: --restartat=.ProcStep.

restartbatchid (optional)
Use the optional parameter --restartbatchid to specify the Batch ID of the restart log file to be used. If no restartbatchid parameter is specified, the most recent restart log file is used (the restart log file that starts with the script name).