Skip to Content
Information
Newer version of documentation BMC provides a newer version of the documentation for this version of the product. As a result, BMC no longer accepts comments in this space.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see bao8301.

What is the IMFEXEC MVX API

The MVX API provides for a two-way data exchange between 

BMC AMI Ops

 products (such as 

BMC AMI Ops Monitor for CICS

, 

BMC AMI Ops Monitor for z/OS

, 

BMC AMI Ops Monitor for IMS

, and others) and a 

BMC AMI OpsA

 REXX EXEC.

Through the API, BMC AMI OpsA EXECs can explicitly request the data from a BMC AMI Ops product. The MVX API enables BMC AMI OpsA to gather data from the BMC AMI Opsdatabus to flow from any of the BMC AMI Ops products into BMC AMI OpsA.

BMC AMI OpsA EXECs process the BMC AMI Opsdata based on how a BMC AMI Ops view looks during a BMC AMI Ops terminal session, so you see the exact output in an EXEC exactly as you would see when the view is displayed from a BMC AMI Ops terminal session.

BMC AMI OpsA processes BMC AMI Opsdata as an array where data from the BMC AMI Opsdatabus (tabular and detail format views) is returned in rows and columns. An array is a table that consists of one or more rows and columns that are given names. A one-to-one relationship exists between the columns of a view and the columns in the resulting array. For more information about the naming conventions for array columns, see Customizing-BMC-AMI-Ops-Infrastructure-views-and-connecting-BBI-SS-PAS-to-a-CAS.

Warning

Note

Every command described in this section is prefixed by the literal MVX to avoid naming conflicts with existing IMFEXEC commands.

Related topic

Using-the-MainView-Extended-MVX-API

 

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

BMC AMI Ops Automation 8.3