Installation requirements for BMC AMI Ops products

BMC AMI Ops Automation for Capping ( iCap )

This product has the following requirements:

• The master PAS requires Version 1.13 or later of the IBM z/OS system.
• The agent PAS requires z/OS 1.12 or later.

• The IBM z/OS BCPii component-- Version 1.13 (HWIBCPIISTC) or later—must be running on the system where the master PAS runs.

  Important

  You should not run Version 2.1 of the IBM Capacity Provisioning (CPM) component for z/OS in parallel with iCap . Also, iCap does not support IBM z/VM guests.

• You must APF authorize the HLQ.BMCLINK or HLQ.BBLINK data set. 

BMC AMI Ops Infrastructure (including Runtime Component System , Alarm Management , and other components)

Provide READ access to the username under which your started task runs in your security authorization facility (SAF) to the CSFKEYS and CSFSERV classes when running the MainView Explorer server with:

• TLS enabled
• Private keys stored in ICSF

BMC AMI Ops Infrastructure uses the  BMC Execution Component for z/OS ( DBC ) component. For the authorization requirements for DBC , see DBC, NGL, and LGC authorization requirements.

• You must APF authorize the HLQ.BMCLINK or HLQ.BBLINK data set. 

All BMC AMI Ops products

All products have the following requirements:

• BMC AMI Ops Infrastructure version 6.2 or later
• Runtime Component System ( RTCS ), which is part of the BMC AMI Ops Infrastructure
• You must APF authorize the HLQ.BMCLINK or HLQ.BBLINK data set. 

This product has the following requirements:

• BMC Atrium Discovery and Dependency Mapping version 8.2.03 or later
• BMC AMI Ops Infrastructure version 6.0 with the following PTFs applied:
  • BPY8846
  • BPY8561
• BBX Subsystem Services version 1.6 with PTF BPB1324 applied
• You must APF authorize the HLQ.BMCLINK or HLQ.BBLINK data set. 

See the requirements for:

• BMC AMI Ops Monitor for Db2 in this table
• SQL and System Performance for DB2 solutions and products in Installation requirements for BMC AMI Data for Db2 products
• You must APF authorize the HLQ.BMCLINK or HLQ.BBLINK data set. 

This product has the following requirements:

• ULTRAOPT/CICS 4.2 or later
• VTAM 4.3 or later
• You must APF authorize the HLQ.BMCLINK or HLQ.BBLINK data set. 
• A security product such as the IBM Resource Access Control Facility (RACF) for the z/OS eNetwork Communications Server Version 2.5 (or later) Internet Protocol (IP) environment.

  Each unit of work in the system that requires Unix System Services must be associated with a Unix System Services identity. A valid identity refers to the presence of a valid Unix user ID (UID), a valid Unix group ID (GID), and a valid HOME directory for the user. The UID and the GID are defined through the OMVS segment, in the RACF profile, and in the RACF group profile.

  For more information about RACF, see the IBM IP Planning and Migration Guide.

  Important

  If the started task is not defined to a user ID that has a defined OMVS segment, error messages might be issued. If the HOME directory is not specified for the user ID, the socket call might fail.

This product has the following requirements:

• BMC AMI Ops for CICS 6.2 or later (recommended), Version 6.2 or later for IBM CICS Transaction Gateway for z/OS (CTG) correlation support
• BMC AMI Ops Monitor for Db2 9.1.00 or later, IBM DB2 Version 9 support requires version 9.2 or later of the BMC AMI Ops Monitor for Db2 product, and version 5.4 or later of the BMC AMI Ops Monitor for Db2 - Data Collector.
• BMC AMI Ops Monitor for IMS Online , version 4.3 or later, or BMC AMI Ops Monitor for DBCTL , version 4.3 or laterIn addition, BMC recommends the Energizer for IMS Connect product for IBM IMS Open Transaction Manager Access (OTMA) information support.
• BMC AMI Ops Monitor for MQ , version 4.3 or later, and BMC Software Extensions for IBM MQ (MQE) version 4.3 we recommend BMC AMI Ops Monitor for MQ , version 4.3.03 or later, and MQE version 4.4.
• Logger secondary log spaces allocated
• Virtual storage requirements:
  • 4 KB of CSA
  • 290 KB of ECSA
• MainView Transaction Analyzer uses the  BMC Execution Component for z/OS ( DBC ) component. For the authorization requirements for DBC , see DBC, NGL, and LGC authorization requirements.
• You must APF authorize the HLQ.BMCLINK or HLQ.BBLINK data set. 

BMC AMI Storage products

This product has the following requirements:

• You must APF authorize the HLQ.BMCLINK or HLQ.BBLINK data set. 
• Virtual storage requirements:
  • Approximately 38 KB of CSA if SVOS has ever been started
  • Approximately 400 KB if SVOS is currently active
  • Approximately 5 KB for each time SVOS has been started and stopped since the last IPL
• To use an EMC VMAX DASD device, you must have:
  • Version 8 of the EMC ResourcePak Base for z/OS component (part of the EMC Mainframe Enablers suite) installed on the system that is running BMC AMI Storage
  • The EMC SCFMAIN program running in a started task if EMC devices are using Virtual Positioning (thin devices)
  • The EMC ESFGPMBT program in the system LINKLST or in a library concatenated in the STEPLIB of the SVOS JCL.    
  • The EMC EMCCMD program in the system LINKLST or in a library concatenated in the STEPLIB of the SVOS JCL.
     
• To use the tape reporting facility, you need one of the following tape library systems:
  • CONTROL-T
  • CA1
  • RMM
     
• BMC AMI Storage Reporting requires:
  • EXTENDED BUFFER MANAGER ( XBM ) 5.4 or later (see EXTENDED BUFFER MANAGER and SNAPSHOT UPGRADE FEATURE requirements)
  • You must add the BUDGET and BUDDSN commands, which are used by the application collector, to the AUTHCMD section in your IKJTSOxx member in SYS1.PARMLIB.

    AUTHCMD NAMES( /* AUTHORIZED COMMANDS */ +
BUDDSN /* BMC SOFTWARE, INC */ +
BUDGET /* BMC SOFTWARE, INC */

    Because the BUDGET and BUDDSN TSO commands might be available to all users, consider using the BMC AMI Storage security exit to control access to the various functions of these commands.

Set a high dispatching priority for the associated Started Tasks for the:

• Performance collector, SGPPROC
• SVOS

If you are running in Goal Mode, it should run in service class SYSSTC.

• For the BMC AMI Storage FDR product requirements, see System requirements .
• For the BMC AMI Storage FDRPAS product requirements, see System requirements .
• For the BMC AMI Storage FATSCOPY product requirements, see System requirements .
• For the BMC AMI Storage IAM product requirements, see Requirements and IAM Storage Usage .

This product has the following requirements:

• z/OS

• VTAM 4.3 (or later)

• 60 KB of CSA storage

• You must APF authorize the HLQ.BMCLINK or HLQ.BBLINK data set. 
• MVS/TSO

• Sufficient ECSA
  The ULTRAOPT subsystem does not contain any hardware-sensitive code or files. You can change direct access storage devices (DASD), 37xx, modems, and so on at any time. The subsystem checks the CPU ID to verify that each product is authorized to run on this CPU. During the trial period, you can obtain a temporary product authorization code that enables the product to run on any CPU. If you need to change or add a CPU after you have obtained a permanent license, contact your BMC sales representative.
  Review the latest technical bulletins for authorized program analysis reports (APARs) that must be applied.

  Important

  At a time, only one version of ULTRAOPT can be active on a single MVS image.

BMC AMI Ops Monitor for CMF

BMC AMI Ops Automation

BMC AMI Ops Monitor for CICS

A UNIX file system is required for installing and maintaining BMC AMI Ops Monitor for CICS . This file system contains code that monitors the CICS Transaction Gateway (CTG). The file system is required even if you do not use BMC AMI Ops Monitor for CICS to monitor CTG.

Virtual storage requirements are as follows:

• For each active BBI-SS PAS:
  • 30 KB CSA plus 22 KB per active SRB
  • 280 KB ECSA
• Additional in BBI-SS PAS for each CICS target system:
  • 320 bytes CSA
  • 14 KB ECSA
• For each CAS:
  • 3 KB CSA
  • 2770 KB ECSA
• For the BBI-SS PAS private area storage:
  • Storage requirement is not constant, it depends on what is active; BMC recommends using REGION=0M for best performance
  • If REGION=0M is not used, set MEMLIMIT to a minimum of 100 GB for BMC AMI Ops Infrastructure to store data records above the bar; BMC recommends a higher MEMLIMIT (such as 500 GB) because 31-bit storage is used if above the bar storage is exhausted
• Make sure that you APF authorize the HLQ.BMCLINK or HLQ.BBLINK data set. 

BMC AMI Ops Monitor for Db2

This product has the following requirements:

• DB2 Solution Common Code (SCC) version 1.6.00 with current maintenance is required.
• To enable a BBI-SS PAS to connect to DB2 subsystems at two release levels, the DB2 load library that is used in the BBI-SS PAS must contain a compatible level of the Call Attach Facility (CAF). Additionally, the DB2 ERLY code in SYS1.LINKLST must be at a compatible level.
• For virtual storage requirements, some functionality requires storage above the 2 GB bar. This functionality includes the TRLTRAC view, current locks views (LS*), and page set statistics views (PS*) as well as background monitor DBIO. To calculate how much above the bar storage your environment requires, perform the following steps:

  1. If page set statistics are enabled (enabled is the default), complete the following equation:

     2 + (ZPARM DSMAX / 5242 + 1) = pppp MB

  2. Complete the following equation:

     (10 MB * x) + (1 GB * y) = nnnn MB

     x is the likely number of concurrent users of the current locks views (LS*).

     y is the likely number of concurrent users of the TRLTRAC view.

     nnnn is the minimum value for the IBM z/OS MEMLIMIT parameter.

     Example

     To support two locks view users and three TRLTRAC view users concurrently, the equation would be:

     (10 MB * 2) + (1 GB * 3) = 3092 MB

  3. Increase the MEMLIMIT parameter to at least the nnnn + pppp value calculated in steps 1 and 2 by performing one of the following actions:

     • In the BBI-SS PAS procedure, add the MEMLIMIT=nnnn MB parameter to the EXEC statement.

     • In the SYS1.PARMLIB member SMFPRMxx, verify that the MEMLIMIT parameter is set to nnnn MB.

• An additional virtual storage consideration when choosing your REGION size is the impact of the page set statistics below the 2 GB bar. Below the bar requirements for page set statistics are as follows:

  200 bytes * currently open data sets (see DSMAX) * (number of users of PS* views and 1 for DBIO background monitor) calculated for each DB2 subsystem being monitored

  Alarms on pages set statistics views should be considered in the number of users count.

  To control the use of page set statistic views and the impact that they can have on your virtual storage resource requirements, use one of the following techniques:

  • Add the following keyword to your DMRBEX00 for a specific DB2 subsystem, PAGESET= YES | NO
  • Issue one of the following global commands from a BMC AMI Ops COMMAND line:
    • STOPPS—Stop page set statistics and free resources, erasing session level statistics
    • STARTPS—Start page set statistics acquiring memory resources to gather session level statistics
    • SHOWPS—Show the status of page set statistics

• BMC AMI Ops Monitor for CICS  - Data Collector uses the  BMC Execution Component for z/OS  ( DBC ),  BMC Configuration Component for z/OS  ( LGC ), and Next Generation Logger ( NGL ) components.

  For the authorization requirements for DBC , LGC and NGL , see DBC, NGL, and LGC authorization requirements.

• You must APF authorize the HLQ.BMCLINK or HLQ.BBLINK data set. 

BMC AMI Ops Monitor for DBCTL

BMC AMI Ops Monitor for IMS Online

This product has the following requirements:

• Virtual storage requirements:
  • BMC AMI Ops AOI exit and Event Collector
    • 10 KB of IMS control region private storage18 KB of CSA (subpool 241)
    • 850 KB of ECSA (subpool 241)
    • 301 KB of ECSA (subpool 231) for Fast Path support
  • 5.2 KB CSA (subpool 241) for each active MWAIT monitor
  • For any active detail trace (MTRAC), the requirement of TRBUFF * TRSIZE dataspace, which is specified in BBPARM member IMFBEX00
  • For each CAS:
    • 16 KB CSA
    • 2770 KB ECSA
  • For each BBI-SS PAS:
    • 2500 KB private area storage
    • 10 KB CSA (subpool 241) per active BBI-SS PAS
    • 25 KB ECSA (subpool 241) per active BBI-SS PAS
  • For each TS:
    • 1000 KB private area storage
    • 8 KB ECSA (subpool 241) per active TS
    • 4 KB CSA (subpool 241) per group of 12 active TSs or fraction thereof
• You must APF authorize the HLQ.BMCLINK or HLQ.BBLINK data set. 

BMC AMI Ops Monitor for IMS Offline

Virtual storage requirements are as follows:

• BMC AMI Ops AOI exit and Event Collector
  • 10 KB of IMS control region private storage
  • 18 KB of CSA (subpool 241)
  • 850 KB of ECSA (subpool 241)
  • 301 KB of ECSA (subpool 231) for Fast Path support
• Each active MWAIT monitor requires 5.2 KB CSA (subpool 241)
• Make sure that you APF authorize the HLQ.BMCLINK or HLQ.BBLINK data set. 

BMC AMI Ops Monitor for IP

BMC AMI Ops Monitor for Java Environments

This product has the following requirements:

• IBM z/OS Version 2.3 or later (for the PAS)
• A 64-bit version of Oracle Java Version 7 or later (for the JVMs)
• Java Batch Toolkit for z/OS (JZOS) Version 7.2.1 or later
• A local TCP/IP port on the PAS (to receive unsolicited information from the BMC AMI Ops Monitor for Java Environments JVM)
• A local, unsecured, JMX-only port
• The following IBM PTFs are required: z/OS version 2.1:
  • UA76726
  • UA80398
  z/OS version 2.2:
  • UA80399

• BMC AMI Ops Monitor for Java Environments uses the BMC Execution Component for z/OS ( DBC ) component. For the authorization requirements for DBC , see DBC, NGL, and LGC authorization requirements.

• You must APF authorize the HLQ.BMCLINK or HLQ.BBLINK data set. 

BMC AMI Ops Monitor for MQ

This product has the following requirements:

• Level 2-compliant distributed IBM MQ
• 16 KB of CSA for the CAS
• 2770 KB of ECSA for the CAS
• 42 KB of ECSA for the PAS
• 180 KB of ECSA for each MVS Queue Manager
• BMC AMI Ops Monitor for MQ uses the  BMC Execution Component for z/OS   ( DBC ) component. For the authorization requirements for DBC , see DBC, NGL, and LGC authorization requirements.
• You must APF authorize the HLQ.BMCLINK or HLQ.BBLINK data set. 

BMC AMI Ops Monitor for Unix Systems Services

Virtual storage requirements are as follows:

• For each CAS:
  • 16 KB of CSA
  • 2770 KB of ECSA
• For each MVS PAS:
  • 12 KB+ of CSA
  • 2050 KB+ of ECSA
• For each Alarm Management PAS:
  • 0 KB of CSA
  • 23 KB of ECSA
• For each BBX:
  • 20 KB of CSA
  • 200 KB+ of ECSA, plus 32 bytes times the number of UCBs
• For each UAS:
  • 0 KB of CSA
  • Total of all of the ECSA values listed for Alternate Access (instead of the values for the TSO session) if you use Alternate Access instead of a TSO session to access the product

Private storage is obtained from high-end private subpools for CAS, PAS, and UAS; it is not restricted by the region size of the address space.

Make sure that you APF authorize the HLQ.BMCLINK or HLQ.BBLINK data set. 

BMC AMI Ops User Interface

BMC AMI Ops Monitor for z/OS

BMC AMI Ops SYSPROG Services