Newer version of documentation BMC provides a newer version of the documentation for this version of the product. As a result, BMC no longer accepts comments in this space.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see bao8301.

AOEXEC VPUT

This command copies one or more variables from the EXECs function pool into one of the 

BMC AMI Ops Automation

 pools.

Note

This command supports the use of sysplex variables; see Using-sysplex-variables for more information about restrictions with sysplex variables (such as with wildcard characters and abbreviations) and other important information.

Command

Parameters

AOEXEC VPUT

[POOL(SHARED|PROFILE)]

SS | SSID(subsystem identifier)

[AOOPTION | AOOPT(ANV, CAO, IAO, IIZ, MAO, QAO, or TSH)]

[TGTJNT()]

[TGTSS(target subsystem identifier)]

VAR(var1....var2....var3...varn)

The following table describes the parameters.

Parameter

Function

Notes

POOL

Pool in which the designated variables reside

Valid values are one of the following pools:

SHARED is the default.

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 OpsA 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.

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.

Note

EXEC processing ignores the AOOPTION parameter when a non-wildcard SSID is specified in the SSID parameter.

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.

Note

The target subsystem named in the TGTJNT entry must exist within the current sysplex.

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, this subsystem is where the requested function is executed.

It 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 BBISSP xx.

BMC Software recommends that you do not use the XCFGROUP parameter in BBISSP xx.

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.

VAR

Name of one or more variables

Each variable name can be up to 32 characters. The maximum length of the combined variable values is 252 bytes.

Variables beginning with the character Q are reserved for system variables and should not be modified.

Return codes are listed in the following table.

Return code value

Description

See AOEXEC-common-return-codes for a description of return code values that are common to all AOEXEC commands. This table lists additional return codes for this AOEXEC command.

4

Variable did not exist in the pool and has been created.

This return code does not occur for sysplex variables. You will receive a RC of 0 whether or not the variable previously existed.

8

Variable value was too long.

12

An attempt was made to update a read-only variable.

16

Parse failed.

16

Sysplex variable name is too long (exceeds 15 characters).

20

Variable name was invalid.

24

Variable name was not specified.

Example 1

REXX EXEC example:

"AOEXEC VPUT VAR(ABENDS ABENDCOUNT ABENDREASON) POOL(SHARED) SSID(RE61)"

CLIST example:

AOEXEC VPUT VAR(ABENDS ABENDCOUNT ABENDREASON) POOL(SHARED) SSID(RE61

This example command saves the current value of ABENDS, ABENDCOUNT, and ABENDREASON in the SHARED pool.

Example 2

REXX EXEC example:

"AOEXEC VPUT VAR(ABENDS) POOL(PROFILE) SSID(RE61)"

CLIST example:

AOEXEC VPUT VAR(ABENDS) POOL(PROFILE) SSID(RE61

This example command saves the current value of ABENDS in the PROFILE pool.

Related topic

Performing-automation-with-the-AOAnywhere-API

 

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