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 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/ file.

To configure alarm attributes as operational categories

  1. Open the ctmticket/etc/ file in a text editor.
  2. Set the values of the three REMEDYOPCAT parameters. For example, modify the following default values available in the file:





    - You can set alarm attributes as operational categories only from the attribute list available in the ctmticket/etc/ 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 Open link in the Remedy IT Service Management online documentation.

  3. 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/ file.

Refer to the following table for the description of these attributes.

control-mIndicates the name of the BMC Control-M Workload Automation server (data center) that processes the job.
order_idRepresents the unique number of the failed job.
rbaIndicates the relative byte address that holds the order ID of the job.
group_rbaIndicates the group relative byte address.
applicationProvides 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_typeBMC Control-M plug-in type.
groupIndicates 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_nameIndicates a non-unique name of the Control-M job.
mem_nameRepresents the script name.
mem_libRepresents the path to the script that was called.
order_tableIndicates the scheduling table name.
ownerRepresents the run-as user running the job.
descriptionProvides 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_typeDefines the type of job that determines which fields are exposed in a job definition.
time_zoneIndicates the time zone used by the job.
in_BIM_serviceIndicates whether the job resides within the BIM service.
job_statusRepresents the Control-M status flag to indicate the completion status of the job (for example, Ended Not OK).
job_stateRepresents the Control-M execution state flag.
state_digits Represents the job's visual state flag.
odateIndicates the job order date.
otimeRepresents the time when then job is placed into active environment.
next_timeDetermines the next time that the job runs for reruns or cyclic jobs that use the Interval option.
rerun_counterIndicates how many times the job was run.
average_runtimeRepresents the average time taken, in minutes, for the job to run. This statistic is compiled from the last successful runs of the job.
start_timeIndicates the start time of the job.
end_timeIndicates the end time of the job.
criticalDetermines whether the job is a critical-path job in Control-M, which ensures resources allocation order.
cyclicRepresents the Cyclic indicator, often related to "Next time".
emergencyDetermines whether the z/OS job is an Emergency job.
Was this page helpful? Yes No Submitting... Thank you