Rerunning a standard SAP job
You can rerun a standard SAP job from the start, or from a specific numeric step of the SAP instruction.
About this task
- conman
- For details, refer to the HCL Workload Automation: User's Guide and Reference.
- Dynamic Workload Console
- Dynamic Workload Console
For details about how to rerun a job that submits an SAP process chain, refer to Rerunning a process chain job.
For
an SAP extended
agent, a step is the numeric step of the SAP instruction
from which a job can be restarted. Before you rerun an SAP job
with HCL Workload Automation,
you have the option of providing a step name for the job. This affects r3batch in
the following ways:
- If you use a step name that is up to 9 digits (or 8 digits preceded by a character) in length, this name is used as the starting step number for the rerunning job.
- If you use any different format, the name is ignored and the job is rerun starting from the first step.
In z/OS environments, you need to set the status of the job to Ready before you can rerun the job.
Note: By default, if you specify
a job step to rerun, the new job is assigned the name of the step
you indicated. To keep the original job name, set the HCL Workload Automation global
option enRetainNameOnRerunFrom to yes. This
option works only when used with the following arguments: rr jobselect;from=[wkstat#]job.
For details about these arguments, see HCL Workload Automation:
User's Guide and Reference, Managing objects in the plan - conman,
Conman commands, rerun. For details about this option, see HCL Workload Automation:
Planning and Installation.
When r3batch reruns a job from its first step, either because you specified it as the starting step or because no starting step was specified, it uses the new copy feature, if applicable. If the starting step is greater than one, r3batch uses the old copy to rerun the job. For a description about the difference between the new and old copy of a rerunning job, refer to Old copy and new copy of a rerunning job.
To rerun a SAP Standard R/3 job from the Dynamic Workload Console, perform the following steps: