AOEXEC MSG
This command logs a message in the BBI-SS PAS Journal log.
Command | Parameters |
|---|---|
AOEXEC MSG | `MessageText' SS | SSID(subsystemIdentifier) [AOOPTION | AOOPT(ANV, CAO, IAO, IIZ, MAO, QAO, or TSH)] [TGTJNT()] [TGTSS(targetSubsystemIdentifier)] |
The following table describes the parameters.
Parameter | Function | Notes |
|---|---|---|
Message text | Text of the message to issue | Maximum length is 252 bytes |
SS | SSID | Specifies the subsystem identifier of a local subsystem | Generic wildcard characters are supported for this keyword. You can specify 1 to 4 asterisks (*) or plus signs (+). If you specify a single asterisk (*), any BBI-SS PAS found on the same LPAR might be used to process the EXEC. You can also specify SS(P*) and the EXEC can be processed by any BBI-SS PAS that begins with P. You can use also the plus sign (+) to indicate a positional wildcard such as SS(+++P). In this example, the EXEC can be processed on any BBI-SS PAS that ends in P. Use the AOOPTION parameter to further filter on the wildcard value. By specifying a value with AOOPTION, you can route the EXEC to the BMC AMI Ops Automation BBI-SS PAS that is running a product option or group of product options. AOOPTION is mutually exclusive with TGTSS and TGTJNT, and it is ignored on a fully qualified SSID specified with SS or SSID parameter. |
AOOPTION | Specifies the product options that must be active in the BMC AMI OpsA PAS. The following values are valid: ANV, CAO, IAO, IIZ, MAO, QAO, or TSH. IIZ represents the BMC AMI OpsA BMC Impact Integration for z/OS product. The stand-alone BMC Impact Integration for z/OS product does not support AOAnywhere processing. | The specified product option must be active in the BMC AMI OpsA PAS. The value specified with the AOOPTION parameter is valid only when the SSID parameter specifies a wildcard value. AOOPTION cannot be specified if TGTSS or TGTJNT are also specified. |
TGTJNT() | A JNT entry that identifies the SSID which processes this request | Use this parameter to specify a different target from the target system where the EXEC is invoked. The specified TGTJNT() should match a TARGET=(tgtname) parameter that is entered in BBPARM member BBIJNT00. The EXEC is scheduled on the subsystem that corresponds to the subsystem that is specified by the SS | SSID parameter of the JNT entry. The specified TGTJNT() may also be an SSID with which the original subsystem communicates. This keyword is mutually exclusive with the TGTSS() keyword. |
TGTSS | If the TGTSS() keyword is specified, the subsystem specified by the SS | SSID() keyword is considered a router and the actual function is executed on the subsystem specified by TGTSS(). If TGTSS() is not specified, the requested function is executed on the subsystem specified by the SS | SSID keyword. | The EXEC must be in the same sysplex as the BBI-SS specified with the SSID() keyword, and both systems must have the same XCFGROUP specified in the BBPARM BBISSPxx. When the AOEXEC command originates in a NetView EXEC, the router and local BMC AMI OpsA PAS must have an active, valid BMC AMI Ops Automation Access NV key. |
Return codes are listed in the following table.
Return code value | Description |
|---|---|
8 | Internal failure occurred while converting ACA to PQE. |
Example
This example sends a message to the BBI-SS PAS monitoring the target named CICA. The message is logged on the remote Journal, and no entry is made on the originating system's Journal.
REXX EXEC example:
CLIST example:
Related topic