HCL Workload Automation, Version 9.4

Rerunning a process chain job

Process chain jobs can be rerun from the start, rerunning the entire process chain, or they can be restarted from a specific process. Restarting a process enables you to restart without rerunning the whole process chain again. You can choose to either restart from the failed processes in a process chain, or restart a specific process indicating the related process ID.

To rerun an SAP job that submits a process chain, you can use one of the following user interfaces:

conman: For details, refer to the User's Guide and Reference.
Dynamic Workload Console: See Procedure for rerunning a process chain job for information about performing this task from the console.

For information about rerunning an SAP Standard R/3 job, see Rerunning a standard SAP job.

In general, when you rerun a process chain job, the new job is assigned the name of the alias you specify. To keep the original job name, set the HCL Workload Automation global option enRetainNameOnRerunFrom to yes. For details about this option, see Administration Guide.

On extended agents, an alias is mandatory for each action you perform on the process chain job and the action itself, is the prefix of the alias name. For example, if you choose to restart a process chain from the failed processes, and assign PCHAIN1 as the alias for the process chain job, then the new job name is Restart_PCHAIN1.

In a z/OS environment, the process chain job maintains the same name and the Monitor Jobs view always displays the status for the last action performed on the job. Every time a rerun is performed on a process chain job, a new instance is generated each with a different ID.

Note:

By default, if you do not specify any setting, rerunning a process chain job corresponds to submitting a new process chain instance.
If you kill an HCL Workload Automation job that submits a process chain, the process chain is removed from schedule in the SAP Business Information Warehouse system. To restart the same process chain instance with r3batch, you require at least the following SAP Business Information Warehouse versions:
- 3.0 with SP25
- 3.1 with SP19
- 3.5 with SP10
- 7.0
If your version of SAP Business Information Warehouse is earlier, you can restart the process chain only manually, through the SAP graphical interface.

Table 1 shows the action performed when you rerun an HCL Workload Automation job that submits a process chain, depending on the settings you specify. These are the actions performed when you submit the rerun operation using the Rerun button from the Monitor Jobs view.

Table 1. Actions performed when you rerun a process chain job
Action performed	Description and setting
A new process chain instance is submitted	HCL Workload Automation creates another process chain instance and submits it to be run again. This action occurs when: On extended agents, you specify `RERUNvalue` as the step to rerun, where `value` is any value you want. This setting overrides the settings in the job definition and options file, if any. In an end-to-end environment, you can perform this action on a centralized job by adding the following parameter to the script file: `-flag pchain_rerun` In the job definition, you set `-flag pchain_rerun`. This setting overrides the setting in the options file, if any. For a description of this parameter, see Table 1. In the options file, you set the pchain_recover option to `rerun`. For a description of this option, refer to Table 1.
The original process chain is rerun from the failed processes	HCL Workload Automation restarts the original process chain from the failed processes to the end. In this way, after you detected the error that caused the failure and performed the recovery action, you can rerun the process chain job from the failed processes and have its run completed. This action is performed only if at least one process in the process chain did not complete successfully. It occurs when: On extended agents, you specify `RESTARTvalue` as the step to rerun, where `value` is any value you want. This setting overrides the settings in the job definition and options file, if any. In an end-to-end environment, you can perform this action on a centralized job by adding the following parameter to the script file: `-flag pchain_restart` In the job definition, you set `-flag pchain_restart`. This setting overrides the setting in the options file, if any. For a description of this parameter, see Table 1. In the options file, you set the pchain_recover option to `restart`. For a description of this option, refer to Table 1.
The process that you specify is restarted	HCL Workload Automation restarts the process of the original process chain that you specify, and monitors the process chain run until its final state. On extended agents, this action occurs when you specify `PROCESSprocessID` as the step to rerun, where `processID` is the identifier of the process you want. For example, if the process ID is `3`, you must specify `PROCESS3` as the step. You can view the process IDs in the following ways: Dynamic Workload Console, version 8.5 or later. From the panel where the details about the process chain are displayed, see the column named Process ID. For details about how to display the process chain details, refer to Displaying details about a process chain job. HCL Workload Automation job log, as follows: +++ EEWO1071I Start of process chain PCHAIN1 Process Chain PCHAIN1 (Log ID:D3C0ZWAYESD58PXOYPEOGNZK7). -------------------------- Process Type: TRIGGER. Process Variant: PCHAIN1_STARTER. Actual State: F. ... >> Process ID: 3. Process Type: ABAP. Process Variant: Z_PCHAIN1_NODE3. Actual State: F. Instance: D3C0ZXL3IJ8LR5O9Q1D9A4Y4N. >> Process ID: 4. Process Type: ABAP. Process Variant: Z_PCHAIN1_NODE1. Actual State: . Instance: D3C0ZZKS0RR88DKRJQ09Z1WW7. +++ EEWO1072I End of process chain PCHAIN1 The following list shows the meaning of the alphabetic value used as the actual state in the job log: Actual state Meaning A Active F Completed G Successfully completed P Planned Q Released R Ended with errors S Skipped X Canceled Y Ready blank Undefined In an end-to-end environment, you can perform this action on a centralized job by adding the following parameter to the script file: `-pchain_pid processID`
The status and details of the original process chain are updated	HCL Workload Automation monitors the original process chain until its final status. This action occurs when: On extended agents, you specify `REFRESHvalue` as the step to rerun, where `value` is any value you want. This setting overrides the setting in the job definition, if any. In an end-to-end environment, you can perform this action on a centralized job by adding the following parameter to the script file: `-flag pchain_refresh` In the job definition, you set `-flag pchain_refresh`. For a description of this parameter, see Table 1.