Configuring Control-M alarm field attributes as operational categories
Configuring Control-M alarm field attributes as operational categories enables you to route the incident to the right support group. The ctmticket_Remedy.properties file contains the default operational categories. You can configure operational categories as per your requirement. However, you can configure only the alarm attributes available in the ctmticket/etc/workinfo.properties file.
To configure alarm attributes as operational categories
- Open the ctmticket/etc/ctmticket_Remedy.properties file in a text editor.
Set the values of the three REMEDYOPCAT parameters. For example, modify the following default values available in the file:
REMEDYOPCAT1=control_m REMEDYOPCAT1=application REMEDYOPCAT3=groupto
REMEDYOPCAT1=owner REMEDYOPCAT1=application_type REMEDYOPCAT3=job_statusNotes
- You can set alarm attributes as operational categories only from the attribute list available in the ctmticket/etc/workinfo.properties file.
- Ensure that the operational categories that you set for the REMEDYOPCAT parameter must be valid operational categories available in Incident Management. For information about creating operational categories, see Creating operational categories
in the Remedy IT Service Management online documentation.- Save the file.
The incident created for the alarm event is then routed based on the operational category values that you have configured in the file.
Alarm field attributes
You can configure the following alarm field attributes as operational categories. These attributes are defined in the ctmticket/etc/workinfo.properties file.
Refer to the following table for the description of these attributes.
| Name | Description |
|---|---|
| control-m | Indicates the name of the BMC Control-M Workload Automation server (data center) that processes the job. |
| order_id | Represents the unique number of the failed job. |
| rba | Indicates the relative byte address that holds the order ID of the job. |
| group_rba | Indicates the group relative byte address. |
| application | Provides a logical name for sorting groups of jobs. This parameter is used to supply a common descriptive name to a set of related job groups. |
| application_type | BMC Control-M plug-in type. |
| group | Indicates the name of the Sub Application where the job belongs logically. It is a sub-category of the Application parameter. For example, the Application is Finances, and the Sub Application is Payroll. |
| job_name | Indicates a non-unique name of the Control-M job. |
| mem_name | Represents the script name. |
| mem_lib | Represents the path to the script that was called. |
| order_table | Indicates the scheduling table name. |
| owner | Represents the run-as user running the job. |
| description | Provides a description of the job in free text. A well written description can help you determine why the job was defined and how it fits into your business workflow. |
| task_type | Defines the type of job that determines which fields are exposed in a job definition. |
| time_zone | Indicates the time zone used by the job. |
| in_BIM_service | Indicates whether the job resides within the BIM service. |
| job_status | Represents the Control-M status flag to indicate the completion status of the job (for example, Ended Not OK). |
| job_state | Represents the Control-M execution state flag. |
| state_digits | Represents the job's visual state flag. |
| odate | Indicates the job order date. |
| otime | Represents the time when then job is placed into active environment. |
| next_time | Determines the next time that the job runs for reruns or cyclic jobs that use the Interval option. |
| rerun_counter | Indicates how many times the job was run. |
| average_runtime | Represents the average time taken, in minutes, for the job to run. This statistic is compiled from the last successful runs of the job. |
| start_time | Indicates the start time of the job. |
| end_time | Indicates the end time of the job. |
| critical | Determines whether the job is a critical-path job in Control-M, which ensures resources allocation order. |
| cyclic | Represents the Cyclic indicator, often related to "Next time". |
| emergency | Determines whether the z/OS job is an Emergency job. |
Comments
Log in or register to comment.