Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Ops Infrastructure 7.1 .

Defining BBI-SS PAS suffixes and target system parameters

Use the following procedures to define all eligible target systems and associate them with the subsystem IDs of their BBI-SS PASs.

Tip

This task is required for the following products but does not apply to other products:

  • BMC AMI Ops Automation
  • BMC AMI Ops Monitor for CICS
  • BMC AMI Ops Monitor for Db2
  • BMC AMI Ops Monitor for DBCTL
  • BMC AMI Ops Monitor for IMS Online
  • BMC AMI Ops Monitor for MQ

Related topics

System-variables-substitution-in-parameter-library-members

Manual-customization

 You need to:

  • Decide which target you want to associate with which BBI-SS PAS
  • Specify the targets and BBI-SS PASs in BBPARM member BBIJNT00

When a PAS first starts, the PAS contacts the CAS and retrieves a list of defined targets and targets that are active on other PASs from the CAS. The PAS appends this information to a list of targets that are built during startup from BBPARM member BBIJNT00.

Important

To define BBI-SS PAS suffixes and target system parameters

  1. Define a one- to four-character subsystem ID to dynamically establish a formal MVS subsystem.The name that you specify:

    • Must be unique from any other subsystem name and cannot be in the MVS subsystem name table (IEFSSNxx)

      Important

      If the subsystem ID that you specify is in IEFSSNxx, message SS0974E is issued and initialization terminates.

    • Cannot be Db2, IMS, CICS, or JES, which are reserved by MVS
    • Must not be the same as the name of any other BBI-SS PAS or CAS that is currently in use

  2. Define a one- to eight-character job name for each target to be managed by a BBI-SS PAS.

    Important

    If the target is a Db2 subsystem, specify the one- to four-character Db2 subsystem ID (SSID). If the target is a MQSeries queue manager, specify the one- to four-character name of that queue manager.

    Each BBI-SS PAS can manage the following targets on a single system image:

    • 128 CICS regions
    • 1 IMS control region or DBCTL region

    • 15 Db2 subsystems for supported versions

      A BMC AMI Ops Monitor for Db2 PAS can support monitoring of Db2 subsystems at two different Db2 releases. To do this monitoring, the appropriate Call Attach (CAF) compatibility level must be available in the Db2 load library used in the PAS. Contact IBM for further information about the two releases that you want to access. 

    • System where the BBI-SS PAS runs

    • Multiple queue managers

      BMC recommends that you monitor no more than 15 MVS queue managers per PAS. If you monitor more than 15, S32E-11C abends might occur. These abends are caused by MQ issuing too many STIMERM SET requests on behalf of the PAS.

  3. Define the type of target, which can be CICS, Db2, IMS, MVS, or QMGR.

  4. For Db2 or IMS targets, identify the target system release.

    Important

    If BMC AMI Ops Monitor for Db2 is dynamically discovering targets, this step is not required.

  5. For IMS targets, identify the type of target as DBDC or DBCTL.
  6. (Optional) Provide a 1- to 22-character description of the target system.
  7. Use the information that you gathered in the preceding steps to modify the parameters in your copy of BBPARM member BBIJNT00.These parameters specify a target/BBI-SS PAS pair and other systems with which this BBI-SS PAS must connect. You can specify multiple TARGET statements for different target systems that are monitored from the same BBI-SS PAS.

To specify a target system for this BBI-SS PAS

Important

  • This procedure is not required if BMC AMI Ops Monitor for CICS and BMC AMI Ops Monitor for MQ are dynamically discovering targets.
  • If BMC AMI Ops Monitor for Db2 is dynamically discovering targets, ALIAS is not supported. If you are using an ALIAS, you must define a static BBIJNT00 entry. If you are not using an ALIAS, this procedure is not required.

In this procedure, you will use member BBIJNT00, which supports the substitution of system variables. Use the following conventions when editing BBIJNT00:

  • All statements must be contained within columns 1 through 71.
  • Statements can be continued across multiple lines.
  • If a statement is continued, the TARGET parameter must appear on the first line.
  • Comments, which begin with an asterisk (*) in column 1, can be inserted anywhere, even between continued statements.
  • The TARGET parameter and comments must begin in column 1; continuations do not have to begin in column 1.

Make the following entry in BBIJNT00 to specify a static target system for this BBI-SS PAS:

TARGET=tgtname,TYPE=type,

IMSTYPE=systype,

SUBSYS=subsys,RELEASE=0vr0

[,DESC=desc][,IMSID=ssid][,ALIAS=name][,ATTACH=IMM | DEFER]

Use the following table to specify the parameters of the entry:

Parameter

Description

TARGET

(Required) Specify a one- to eight-character name of a target system. The specified name must be unique.

The target system is monitored by a BBI-SS PAS as follows:

  • For BMC AMI Ops Automation, specify the name of a target CICS, IMS, MVS, or QMGR, such as TARGET=MVSPROD.
  • For BMC AMI Ops Monitor for MQ, specify the queue manager subsystem ID (one to four characters), such as TARGET=CSQ1. It can be any name used to relate to a non-MVS queue manager name. The target name must be unique within a plex of BBI-SS PASs.
  • For BMC AMI Ops Monitor for CICS, specify the job name of a target CICS, such as TARGET=CICSA1. The target name must be unique within a plex of BBI-SS PASs.
  • For BMC AMI Ops Monitor for IMS Online, specify the name of a target IMS, such as TARGET=IMS71X.
  • For BMC AMI Ops Monitor for DBCTL, specify the job name or IMS ID of the DBCTL region, such as TARGET=IMSDBCP.
  • For BMC AMI Ops Monitor for Db2, specify a Db2 subsystem ID (one to four characters), such as TARGET=DB2P.

TYPE

(Required) Specify the type of target as follows:

  • For BMC AMI Ops Automation, specify TYPE=CICS for a CICS target or TYPE=IMS for an IMS target or TYPE=QMGR for a MQ queue manager target. BMC AMI Ops Automation always requires one TYPE=MVS specification for each BBI-SS PAS.
  • For BMC AMI Ops Monitor for MQ, specify TYPE=QMGR for a queue manager target.
  • For BMC AMI Ops Monitor for CICS, specify TYPE=CICS for a CICS target.
  • For BMC AMI Ops Monitor for IMS Online, specify TYPE=IMS for an IMS target.
  • For BMC AMI Ops Monitor for DBCTL, specify TYPE=IMS for an IMS target.
  • For BMC AMI Ops Monitor for Db2, specify TYPE=DB2 for a Db2 target.

IMSTYPE

(Required) Specify the type of IMS target.

Specify IMSTYPE=DBDC for an IMS DB/DC system (the default) or IMSTYPE=DBCTL for a DBCTL system. The IMSTYPE parameter is valid only when TYPE=IMS is specified.

SUBSYS

(Required) Specify a one- to four-character subsystem ID that is assigned to a BBI-SS PAS. If only one BBI-SS PAS is created, use the value SSA1.

RELEASE

(Required) For IMS, Db2 and DBCTL targets, specify the four-digit release number of the target. For example, RELEASE=0810 specified with TYPE=DB2 indicates Db2 Version 8.1.

DESC

(Optional)Specify a 1- to 22-character description of the target system. If the description contains any embedded commas or blanks, it must be enclosed in single quotation marks:

'xxx ... xxx'

IMSID

(Optional) For IMS targets, specify a unique one- to four-character subsystem ID of the IMS control region that you want to monitor.

Important

  • For IMS targets, if you specify IMSID, it overrides what was specified by the TARGET statement.
  • If you specify IMSID, you cannot specify ALIAS for an IMS target.

ALIAS

(Optional) Specify the ALIAS parameter as follows:

  • For BMC AMI Ops Automation for IMS, BMC AMI Ops Monitor for Db2, or BMC AMI Ops Monitor for IMS Online, specify a one- to eight-character alias name for the target subsystem. If you have two targets with the same tgtname controlled by different BBI-SS PASs, you must define an alias name, such as ALIAS=PRODDB2.

Important

  • If you specify ALIAS, it overrides what was specified by the TARGET statement.
  • If you specify ALIAS for an IMS target, you cannot specify IMSID.
  • For BMC AMI Ops Monitor for CICS, specify the one- to eight-character APPLID that is specific to the CICS region. The APPLID (which is used as the alias name) must be unique within a plex of BBI-SS PASs.

Important

  • If you do not specify ALIAS for a CICS target, the alias name defaults to the TARGET name (which must also be unique within a plex of BBI-SS PASs).
  • The alias name for a CICS target can only be used in full-screen mode.

ATTACH

For Group 3 products, the ATTACH parameter requests immediate or deferred target recognition when the BBI-SS PAS starts.

  • DEFER (the default) causes the service point to be created after the target is active. Data is not supplied in response to queries until the target becomes active or a monitor is started that collects data from that region. In most cases, ATTACH=DEFER should be used.
  • IMM causes the service point to become active when the BBI-SS PAS initializes. It remains active regardless of the target state, which is useful for viewing historical data from that target when it is no longer active. The target status is shown as active in the Plex Manager views. The PAS can collect data from the target, but that target itself is not active.

 

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