Skip to Content

Viewer commands

Commands are pre-configured operator inputs that are attached to a message via an RDL2 rule.

When an operator right-clicks a message in the Java viewer, the list of commands is presented as an Actions sub-menu on the context menu. Each message may have an arbitrary number of commands. attached to it.

To invoke a message action in the browser-based viewer, click or tap on the message to open the message details panel. The actions and commands attached to the message appear at the top of the message details panel.

Each message has an optional COMMANDS array that contains the command information. Each element of the COMMANDS array is a map that contains a DESCRIPTION and either a FUNCTION or an ACTION string.
 The FUNCTION string is the text that is sent back to the session as if it was typed in the operator input field. The DESCRIPTION string is the text that appears on the actions sub-menu.
The ACTION string contains an action to be executed within the viewer. For more information on all possible actions, see Action detail notes.

The following example shows how to give an operator predefined choices for the $HASP483 message:

Information
Example

trigger on message.MSGID == "$HASP483"

message.COMMANDS[0].DESCRIPTION = "Terminate JES2"
message.COMMANDS[0].FUNCTION = "R," & message.REPLYNUM & ",N"

message.COMMANDS[1].DESCRIPTION = "Rebuild job queue"
message.COMMANDS[1].FUNCTION = "R," & message.REPLYNUM & ",Y"

message.COMMANDS[2].DESCRIPTION = "BMC.com"
message.COMMANDS[2].ACTION = "browser:http://www.bmc.com"

Related topic

Administering

 

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

BMC AMI Console Management for zEnterprise, BMC AMI Console Automation for zEnterprise, and BMC AMI SecureHMC 4.0