Issue Message panel

Use the Issue Message panel to enter message text that the Rule sends.

This panel is available to all event types. The following figure shows an example of the Issue Message panel.

 BMC Software  --------------- Issue Message ------------------ BMC AMI OpsA
 COMMAND ===>                                                 TGT  --- AOAO     
                                                                               
 Message Type ===>                        WTO, JRN, or WJ                       
                                                                               
 Message Text ===>                                                              
                                                                               
                                                                               
 Optional Route and Descriptor Codes (ignored for JRN messages)                 
 Route Codes  ===>                                                              
 Desc Codes   ===>                                                              

 Console Name ===>                        Optional for WTO type                 
                                                                               
 Optional Delay Time in seconds                                                 
 Delay Action ===>                        5 - 99999                             
                                                                               
                                                                               
 Press END to return to previous panel with fields populated, or  CANCEL to     
 cancel changes

The following table describes the fields on this panel.

Field name

Description

Message Type

Specify where Rule sends the message.

Possible values are as follows:

  • WTO: specifies that the message is a write-to-operator (WTO) message
  • JRN: specifies that the message is written to the BBI Journal
  • WJ or JW: specifies that the message is both a WTO and also written to the BBI Journal

EVENT and SHARED variables are valid.

For event type MSG:

  • if you use IMFTEXT, the reply ID is stripped from the message
  • WORD1 is the first word after the reply ID
  • TEXT ID is the first word after the reply ID
  • TEXT STRING does not include the reply ID
  • if you journal the message, the entire message (including the reply ID) is written to the journal

Message text

Specify a 1-125 character message to be sent to an MVS console.

The message is issued without routing or descriptor codes unless specified with the R (route) or D (descriptor code) keywords (or both), and followed by a colon (:) or if you use the Route Codes or Descriptor codes fields.

Route Codes

Specify one or more route codes to be used for a message sent as a WTO. Separate multiple route codes with a blank; for example 1 2 3

Descriptor Codes

Specify one or more descriptor codes to be used for a message sent as a WTO.

Separate multiple descriptor codes with a black; for example: 5 9

Console Name

Specify the name of MVS Console to send WTO. If not specified, the WTO is sent to the console or consoles defined by Route Codes.

Delay Action

Specify the number of seconds to wait before the Rule issues this message.

Valid values 1 through 99999.

If the BBI-SS PAS is stopped for any reason before BMC AMI Ops Automation can issue the messages that are scheduled with a Delay, the delayed messages are not re-issued when the BBI-SS PAS restarts.

Daylight Saving Time considerations:

For more information about how changing the local MVS time affects specifying a delayed action, see section, 'Managing daylight saving time and BMC AMI OpsA time-initiated automation' in the Using-BMC-AMI-Ops-Automation-basic-applications.


Related topic

Additional-panels


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*