AOEXEC SYSINFO

This command searches the current MVS image for a

BMC AMI Ops Automation

subsystem that runs AOAnywhere support.

It returns information in variables regarding the success and failure of this search, as well as the XCF group name in which the targeted (or defaulted to) subsystem resides. Additionally, it returns the identifiers of all BMC AMI OpsA subsystems that are connected to each other (in the sysplex) and it identifies those subsystems that have been designated as Alert Receivers.

This information can be used in subsequent requests against AOAnywhere, which require the presence of a SSID identifier.

When the target BBI-SS PAS is not specified, for example the SSID, GROUP, and TGTJNT keywords are omitted from the command, and the AOEXEC SYSINFO command is running inside an BMC AMI OpsA PAS, the command returns the list of BBI-SS PASs that are in the same XCF group as the BMC AMI OpsA from where the command is issued.

When the AOEXEC SYSINFO command is running outside the BMC AMI OpsA PAS and none of the keywords (SSID, GROUP, TGTJNT) are specified, the command returns the list of BBI-SS PASs that belong to the default XCF group BMCAB.

This command has the following parameters.

Command	Parameters
AOEXEC SYSINFO	[SS \| SSID()] [GROUP()] [TGTJNT()]

The following table describes the parameters.

Parameter	Function	Notes
SS \| SSID	Specifies the subsystem identifier from which system information is obtained. One to 4-alphanumeric characters.	This parameter should be used only when separate XCF groups will be used within a sysplex. An XCF group for a specific subsystem is specified on the XCFGROUP= parameter in BBPARM member BBISSP00. When this parameter is specified, only information for the subsystems connected to the same XCF group as the targeted subsystem is obtained. Do not use this parameter with the GROUP() parameter. 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.
GROUP	Specifies the XCF group from which information is obtained. The parameter is one to 8 alphanumeric characters per IBM XCF naming conventions.	You should use this parameter only when multiple XCF groups are specified within a sysplex. You can specify an XCF group for a specific subsystem with the XCFGROUP= parameter in BBPARM member BBISSP00. When you specify this parameter, information for only the subsystems connected to the named XCF group is obtained. At least one BMC AMI OpsA subsystem that belongs to the specified XCF group should reside on the current MVS image. Otherwise, the request fails. If you do not specify the SSID() nor GROUP() parameters, GROUP(BMCAB) is the default. The first subsystem on the current MVS image belonging to this group is used to obtain information about all other BMC AMI OpsA subsystems connected to each other in this XCF group. XCFGROUP() or XCF() are aliases of this parameter.
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 value in the TGTJNT() parameter should match a TARGET=(tgtname) parameter that is entered in BBPARM member BBIJNT00. The EXEC is scheduled on 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.

The following table describes the variables that AOEXEC SYSINFO returns.

Variable name	Description
SYSTEM	name of the current OS/390 image (commonly referred to as the system name)
ALRT1 through ALRTx	value of YES or NO YES means this subsystem has been designated as an ALERT receiver by specifying ALRTRCVE=YES in BBPARM member BBISSP00. Otherwise the returned value is NO.
IMFXCFGP	name of the default or target XCF group referred to by the command If the SSID() parameter is specified, it contains the name of the XCF group of which the targeted subsystem is a member. If GROUP() was specified, the name is identical to the contents of this keyword.
LCNT	number of lines returned
SSID1 through SSIDx	BMC AMI OpsA subsystem (SSID) name that is supporting AOAnywhere where x is between 1 and the value contained in LCNT variable
SYSN1 through SYSNx	names of the MVS images that the relative SSID is active on where x is between 1 and the value contained in LCNT
MAO_x IAO_x ANV_x CAO_x QAO_x TSH_x	BMC AMI Ops Automation for z/OS BMC AMI Ops Automation for IMS BMC AMI Ops Automation Access NV BMC AMI Ops Automation for CICS BMC AMI Ops Automation for MQ BMC AMI Ops Automation TapeSHARE The value of x can be one of the following: YES: the product is present NO: the product is not present N/A: the targeted PAS does not have a level of code capable of returning the information.
Note The SSID, SYSN and ALRT variables are returned in sets. For example, SSID1, SYSN1 and ALRT1 are returned together; SSID2, SYSN2 and ALRT2 are returned together, and so on.

Return codes are listed in the following table.

Return code value	Description
Refer to 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.
44	Processing was terminated in the middle of processing an AOEXEC SYSINFO. If more than one BMC AMI OpsA PAS capable of processing an AOEXEC SYSINFO command is active on the local system, it is possible that this situation is temporary and a subsequent execution of SYSINFO will be successful.

REXX EXEC example:

When this EXEC is executed inside a BMC AMI OpsA BBI-SS PAS, it displays other BBI-SS PASs that belong to the same XCF group as the BMC AMI OpsA BBI-SS PAS. When this EXEC is executed outside of BMC AMI OpsA, it displays BBI-SS PASs that belong the default (BMCAB) XCF group.

/* REXX */
"AOEXEC SYSINFO"
if rc<> 0 then do
  say 'No active subsystems found'
  exit
end
do i=1 to lcnt
  if value('SYSN'i)=system then do
   myss=value('SSID'i)
   mysys=value('SYSN'i)
   leave
end
end
"AOEXEC VGET VAR(QJNLSTA) SSID("myss")"
say 'Current journaling status on 'strip(mysys)' is 'qjnlsta

CLIST example:

PROC 0
Control SYMLIST CONLIST LIST
AOEXEC SYSINFO
IF &LASTCC NE 0 THEN DO
  WRITE No active subsystems found'
  EXIT
END
SET I=1
DO WHILE &I LE &LCNT
  SET THISSYS=&&&STR(SYSN)&I
  IF &THISSYS=&SYSTEM THEN DO
    SET MYSS=&&&STR(SSID)&I
    SET MYSYS=&&&STR(SYSN)&I
    SET I=&LCNT
  END
  SET I=&I+1
END
AOEXEC VGET VAR(QJNLSTA) SSID(&MYSS)
WRITE Current journaling status on &MYSYS is &QJNLSTA

AOEXEC SYSINFO

REXX EXEC example:

On this page