Job definition parameters in Control-M for Oracle Retail enable you to apply values for the variables, as described in Using Control-M Workload Automation.
The following table describes the parameters for the Control-M for Oracle Retail.
RMS Job definition parameters descriptions
Parameter |
Description |
Defines the Control-M for Oracle Retail account. |
|
Defines the Oracle Retail type to use: RMS or RPM. |
|
Defines which Oracle Retail program to use. Note: You can use the "*" wildcard in the Program Name field to retrieve a list of matching programs. You can use the wildcard anywhere in the program name. |
|
Defines the path to the Oracle Retail program. You can select the Connection profile default, or type in a new path to override the default value. If you select the Connection profile default, verify it was defined in Control-M for Oracle Retail connection profile parameters. |
|
Defines the number of threads that the program runs concurrently. |
|
Defines when to run threads in the job. When selected, for threads with the following statuses: 'aborted', 'aborted in init', 'aborted in process', and 'aborted in final'; the job will restart the failed threads. If there are no failed threads, then all threads run from scratch. |
|
Defines the parameters needed for the program to run. |
|
Usage |
Displays the RMS program's usage as returned by the RMS program. |
RPM Job definition parameters descriptions
Parameter |
Description |
Defines the Control-M for Oracle Retail account. |
|
Defines the Oracle Retail type to use: RMS or RPM. |
|
Defines the name of the script to run. |
|
Defines the path to the Oracle Retail script. You can select the Connection profile default or type in a new path to override the default value. If you select the Connection profile default, verify it was defined in Control-M for Oracle Retail connection profile parameters. |
|
Defines the parameters needed for the script to run. |
Parent Topic |