Unable to get the correct job name to appear in the fetchmsg alarm

book

Article ID: 131548

calendar_today

Updated On:

Products

DX Infrastructure Management NIMSOFT PROBES

Issue/Introduction

The fetchmsg alarm generates with the wrong job name.

Cause

- alarm message configuration

Environment

- fetchmsg v1.52

Resolution

List the messages from the given queue, in this case the "ROBOT" queue which was manually created.

<Please see attached file for image>

fetchmsg all messages


Here is the original text used to create the alarm:

"$profile: $job_name $type should have started 10 minutes ago. This needs to be investigated immediately and called out per option 21." 

This is the alert that was generated: 

Job did not start:ROBOTJM should have started 10 minutes ago. This needs to be investigated immediately and called out per option 21. 


Here is the adjusted text used to create the proper alarm:

$profile: $text should have started 10 minutes ago. This needs to be investigated immediately and called out per option 21.

Job did not start:DUYTEST should have started 10 minutes ago. This needs to be investigated immediately and called out per option 21.

Additional Information

fetchmsg IM configuration - configure alarm messages

https://docops.ca.com/ca-unified-infrastructure-management-probes/ga/en/alphabetical-probe-articles/fetchmsg-fetch-system-messages-on-iseries/fetchmsg-im-configuration#fetchmsgIMConfiguration-ConfigureAlarmMessages

See section on the list of fetchmsg message variables that can be used in alarm messages.

fetchmsg.cfg section for the above profile/message.

<Job did not start>
      active = yes
      check_answered = no
      check_description = no
      check_id = no
      check_severity = no
      check_text = yes
      check_type = no
      min_severity = 0
      regexp_text = /.*did not start by.*/
      check_job_name = no
      check_user_profile_name = no
      in_queue = ROBOT
      message = JobDidNotStart
      if_not_matched_by_other = no
      action_send_alarm = yes
      action_answer_message = no
      time_frame = 
      msg_condition = 
      msg_count = 
      answer_limit_alarm = yes
      supp_key = $profile/$key
   </Job did not start>

Attachments

1558686714464000131548_sktwi1f5rjvs16f21.png get_app