Actions
Last updated
ProcMan Admin Guide V6.0.0
Last updated
How to define actions is described in the documentation . For each Control-M module process we need:
one or several activity actions
one report action
one cleanup action
Activity actions, report action and cleanup action have to be specified in the process definition. How to define process definitions is described in the documentation .
To browse the by the Control-M module processes handled folders in the Object Browser, a special action for this purpose can be defined. The Object Browser action has to be specified in the Object Browser definition. How to define Object Browser definitions is described in the documentation .
In the Administration Dialog of actions, the command can be either specified in the URL notation, or by separated command and command parameters (see examples below). In the following text we will use the URL notation.
Example of a URL notation:
Example of separated command and command parameters (equivalent to the URL notation in the example above):
Dependent on how many activities a process definition has and on, whether different configurations of the Control-M module for the activities are needed, one or several activity actions have to be defined. A command which is executed by an activity action looks like this:
or
hos_ctm_call_config file is a Control-M module call configuration file in the etc directory, having the structure of the etc/hos_ctm_call_config.php file described above.
options can be used to override the options specified in the configuration file.
Example:
Although there is a possibility to specify different report actions for each activity, normally we need only one report action for all activities of the process. For report actions the configuration option readonly must be set to 'Y'. That can be either done in a special configuration file for the report action or by using a configuration file of an activity action and overriding the readonly option in the call parameter. A command which is executed by the report action looks for the first case like this:
or for the second case like this:
hos_ctm_call_config file is a Control-M module call configuration file in the etc directory, having the structure of the etc/hos_ctm_call_config.php file described above.
Example:
The cleanup action is called when a process is deleted. A command which is executed by the cleanup action looks like this:
hos_ctm_call_config file is a Control-M module call configuration file in the etc directory, having the structure of the etc/hos_ctm_call_config.php file described above.
Example:
The Object Browser action is called when a user clicks on an Object Browser menu item. A command which is executed by the Object Browser action looks like this:
hos_ctm_call_config file is a Control-M module call configuration file in the etc directory, having the structure of the etc/hos_ctm_call_config.php file described above.
Example:
