AOEXEC VDELL
This command deletes one or more long variables from one of the
BMC AMI Ops Automation
variable pools.
Command | Parameters |
|---|---|
AOEXEC VDELL | [POOL(SHARED|PROFILE)] VAR(var1....var2....var3...varn) SS | SSID(subsystem identifier) [AOOPTION | AOOPT(ANV, CAO, IAO, IIZ, MAO, QAO, or TSH)] [TGTJNT()] [TGTSS(target subsystem identifier)] |
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. |
VAR | Name of one or more variables | Each variable name can be up to 32 characters. Maximum parameter length is 252. Variables beginning with the character Q are reserved for system variables and cannot be modified. |
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 (+).
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. AOOPTION cannot be specified if TGTSS or TGTJNT are also specified. |
TGTJNT() | optional | 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, 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 BBISSPxx. |
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. | |
8 | Variable does not exist. |
12 | An attempt was made to delete a read-only variable. |
16 | Sysplex variable name is too long (exceeds 13 characters, the limit for long sysplex variable names). |
20 | Serious (fatal) error has occurred during parse. |
22 | VDEL has failed. |
24 | Variable name was not specified. |
53 | Command is not supported under Netview. |
Examples
The PROFILE pool is searched for a long variable with the name of X. If found, it is deleted.
REXX EXEC example:
CLIST example:
Related topic