AOEXEC VDEL

This command deletes one or more variables from one of the

BMC AMI Ops Automation

variable 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 VDEL	[POOL(SHARED\|PROFILE)] SS \| SSID(subsystem identifier) [AOOPTION \| AOOPT(ANV, CAO, IAO, IIZ, MAO, QAO, or TSH)] [TGTJNT()] [TGTSS(target susbsystem 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 See Using-sysplex-variables for more information about sysplex variables. PROFILE 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, the requested function is executed on the subsystem specified by the SS \| SSID keyword.	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. When the AOEXEC command originates in a NetView EXEC, the router and local BMC AMI OpsA PAS must have an active, valid BMC AMI OpsA Access NV key.
VAR	Name of one or more variables	The maximum length of this parameter is 252 bytes. All variables in a pool can be deleted by using the identifier ALL instead of naming all variables individually. A variable cannot begin with a numeric nor can it contain special characters. An example of using a pattern is AOEXEC VDEL VAR(CICS) SSID(RE61) The variable names can be expressed generically by using an asterisk. However, the VDEL command statement assumes that the presence of an asterisk means the end of the string. AOEXEC VDEL VAR(ABCD) SSID(RE61) is treated as if you coded AOEXEC VDEL VAR(ABC) SSID(RE61) In addition, if you try to use an asterisk within a string of text, you will receive a return code for invalid syntax usage. For example, if you try to issue a pattern AOEXEC VDEL VAR(CSMMSG12) SSID(RE61) you receive a return code of IMFCC=16 (for invalid syntax usage). Variables beginning with the character Q are reserved for system variables and cannot be modified.

Note

This command does not affect variables that were already retrieved from one of the pools.

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 15 characters).
20	Serious (fatal) error occurred during parse.
20	VDEL has failed.
24	Variable name was not specified.

Example

This example deletes all variables ending in the characters TEST from the shared variable pool and uses the VLST command to retrieve all variable names.

REXX EXEC example:

"AOEXEC VLST VAR(*) POOL(SHARED) SSID(RE61)"
do i=1 to lcnt
  if length(value('line'.i))< 4 then iterate
  if right(value(value(line.i)), 4)='TEST' then
  "AOEXEC VDEL VAR("value(line.i)") POOL(SHARED) SSID(RE61)"
end

CLIST example:

AOEXEC VLST VAR(*) POOL(SHARED) SSID(RE61)
SET I=1
DO WHILE &I LE &CNT
  SET LEN=&LENGTH(&SYSNSUB(2, &LINEI))
  IF &LEN LT 4 THEN GOTO SKIP
  IF STR(&SUBSTR(&LEN-3:&LEN, &SYSNSUB(2, &&LINEI))) +
  NE TEST THEN GOTO SKIP
  AOEXEC VDEL VAR(&SYSNSUB(2, &&LINE&I) ) POOL(SHARED) SSID(RE61)
SKIP: +
  SET I=&I+1
END

AOEXEC VDEL

Example

On this page