BMC Automated Mainframe Intelligence (AMI) Ops Monitor for z/OS

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	BMC Automated Mainframe Intelligence (AMI) Ops Monitor for z/OS is a monitoring, management, and automation technology designed for z/OS systems and subsystems. This technology enables the user to detect problems that affect normal system operation, determine the root cause of problems, resolve the problem, and automate processes to prevent problems from reoccurring. Any changes in system workload, resource, and application usage and other factors that impact information technology (IT) infrastructure metrics can be monitored. This technology was renamed from BMC MainView for z/OS on 01/21/2021.
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:	This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v24.4
Decision Date:	04/10/2024 at 17:17:07 UTC
Aliases:	BMC MainView for z/OS, BMC AMI Ops Monitor
Introduced By:	CDCO Supported Architecture Components
Vendor Name:	BMC Software

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
3.0.x	11/17/2010
3.1.x	09/14/2012
3.2.x	02/20/2015
6.x	06/22/2017

Current Decision Matrix (04/03/2024)

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VA IT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported. Any major.minor version that is not listed in the VA Decision Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for use.
Yellow	Approved w/Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Unapproved: This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Divest: VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unapproved may be found on the Decision tab for the specific entry.
Black	Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Planning/Evaluation Constraint:The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology approved with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology approved with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

<Past

CY2019

CY2020

CY2021

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

3.0.x

Unapproved

3.1.x

Unapproved

3.2.x

Unapproved

6.x

Approved w/Constraints
[4, 5, 6]

Approved w/Constraints
[4, 5, 7]

Approved w/Constraints
[5, 7, 8]

Decision Constraints


[1]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[2]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[3]	This product only runs on the z/OS operating system. Users must only use approved versions of z/OS if they plan to implement this technology. If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

[4]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[5]	Users should check with their supervisor, Information Security Office (ISO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations.

[6]	This product only runs on the z/OS operating system. Users must only use approved versions of z/OS if they plan to implement this technology. If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

[7]	This technology only runs on the z/OS operating system. Users must only use approved versions of z/OS if they plan to implement this technology. If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

[8]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

Note:

At the time of writing, version 6.4.00 is the most current version, released 11/02/2023.

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

Technology Components

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Name	Description
BMC Automated Mainframe Intelligence (AMI) Ops Automation	BMC AMI Ops Automation (also referred to asBMC AMI OpsA) is a BMC Software product that provides software to improve an operator’s ability to provide high system availability. BMC AMI OpsA helps the operator through error minimization, improved productivity, and problem determination and prevention.
BMC Automated Mainframe Intelligence (AMI) Ops Infrastructure	This component stores information related to Alarm Management, and supports the deployment of definitions to other CASPERM registries on other systems.
BMC Automated Mainframe Intelligence (AMI) Ops Monitor Comprehensive Management Facility (CMF)	BMC CMF Monitor, an integrated component of the BMC MainView monitoring solution, is a compatible replacement for International Business Machines (IBM)`s Resource Measurement Facility (RMF) that can produce all of the IBM System Management Facilities (SMF) Type-70 records. BMC CMF Monitor provides real-time and historical data about workloads, resources, devices, and delay activities; and provides users with the data to manage and improve system performance across all of their z/OS images. This component follows a different version scheme than BMC MainView for z/OS. Documents may not be accessible without creation of a customer account on BMC's documents site.
BMC Automated Mainframe Intelligence (AMI) Ops Monitor for Customer Information Control System (CICS)	Mainview for Customer Information Control System (CICS) Management is a performance management monitoring solution with automation for managing traditional CICS and parallel processing environments. This component follows a different version scheme than BMC MainView for z/OS.
BMC Automated Mainframe Intelligence (AMI) Ops Monitor for Unix Systems Services (USS)	BMC MainView for USS allows users to monitor workloads and resources consumed from the USS perspective that traditional performance monitors are unable to see. It monitors processes, file systems, BPXPRM parameters, Hierarchical File System (HFS) global buffers and user information. BPXPRMxx contains the parameters that control the z/OS UNIX System Services environment and the file systems. This component follows a different version scheme than BMC MainView for z/OS. Documents may not be accessible without creation of a customer account on BMC's documents site.
BMC Automated Mainframe Intelligence (AMI) Ops Monitor for z/OS	This component allows users to manage their z/OS monitoring and automation environments from a web browser, using a common graphical user interface (GUI) that does not require any off-platform software. This component follows a different version scheme than BMC MainView for z/OS. Documents may not be accessible without creation of a customer account on BMC's documents site.
BMC Automated Mainframe Intelligence (AMI) Ops SYSPROG Services	This component provides the ability to issue an alert when a threshold is being exceeded, in addition to monitoring metrics such as resource utilization, workload performance, job performance, coupling facility and enclaves. This component follows a different version scheme than BMC MainView for z/OS. Documents may not be accessible without creation of a customer account on BMC's documents site.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Systems Management Systems Management Tools	Monitoring

Operating Systems Supported by the Technology

z/OS - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

No runtime dependencies have been identified.

Comparable Technologies:

Companion Technologies/Supported Standards:

No companion technologies/standards have been identified.

General Analysis

Adoption Benefits

This technology may improve z/OS mainframe stability and help reduce the amount of system failures through proactive monitoring and alerts.
This is a well-documented technology.

Adoption Risks

There are known Common Vulnerabilities and Exposures (CVEs) associated with this technology. Please see https://nvd.NIST.gov/vuln/search for more details.
There are other VA-approved comparable technologies and the adoption of this technology could result in duplicate functionality and compatibility issues.
The potential exists to store Personally Identifiable Information (PII), Protected Health Information (PHI) and/or VA Sensitive data and proper security standards must be followed in these cases.
This technology has a free trial period, which carries the potential for the disruption of service delivery and inaccurate financial planning.
Due to the rapid release schedule of this technology, the VA may be unable to update to the most recent patch and may require a deployment model requiring the use of specific versions.
There is no indication based on either the vendor documentation or the Cryptographic Module Validation Program (CMVP) that this technology is Federal Information Processing Standard (FIPS) 140-2 compliant.

Architectural Risks

This technology is not portable as it runs only on z/OS systems.

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (04/03/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (04/03/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Risks

EMAIL UPDATES