Command Line Operation Steps

A Command Line operation step enables you to build the job type through the command line. The following topics describe how to define a pre-execution, execution and post-execution command line operation step.

You can edit an Execution operation step by clicking the Execution operation step and editing as required. If you want to delete an operation step, click next to the Operation step that you want to delete and click Delete. If you have created parameters and want to delete them, you need to manually delete them from the Designer area.

If you want to use Control-M variables, which are not defined in the job type, you need to add them in the Command Line field as an environment variable.

To use variable %%MYLIBPATH, in the Command Line field, type one of the following:



When adding a Command line step for the first time, the Run As field is automatically added to the Connection Profile field in the Designer area. The Run As field is not mandatory and you can remove it you do not require security impersonation.

In Windows, Run As automatically requires a password field. The following are prerequisites for Run As:

  • A Windows user

  • Domain\User A (with Administrator rights)

    For Linux, the Run As user must be root.

For an Execution operation step, you can create multiple variables under one command and add execution steps which are added sequentially in the order that they are inputted, although you can add, remove and reorder the steps. For each operation step you can add the following:

  • Return Codes: Decides how to handle the command return code and control the job end status.

  • Output Handling Rules: Indicates how to handle the command standard output to control the job end status, or extract data from it.

  • Runtime Information Rules: Enables you to execute an operation step during the job run to retrieve progress and status from the application.

  • Manual Abort Operation Rules: Enables you to define another operation step to be performed when the job is requested to be killed.

  • Job Completion Verification Rules: Enables you to define the operation step to run to identify job completion (asynchronous executions).