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.

Defining OSPI virtual terminals

This section describes defining Open Systems Procedural Interface (OSPI) virtual terminals.

BMC AMI Ops Automation

 provides OSPI the as an interface to VTAM-based products. OSPI provides a means for REXX- or CLIST-based automation procedures to interface with any LU2 VTAM application that uses full screens to communicate with users.

With OSPI, BMC AMI OpsA has logon capabilities and complete access to any VTAM application’s data stream. In this way, BMC AMI OpsA can interact with the application by analyzing the output data and issuing the VTAM application’s own commands.

By automatically interfacing with critical VTAM applications and simulating a user at a VTAM terminal, OSPI can communicate with various data center software products and decrease the number of VTAM-based terminals.

This terminal emulation requires that some number of OSPI virtual terminals be defined to VTAM. In addition, some applications, such as CICS and IMS, might require local definitions for OSPI terminals. Refer to OSPI-terminal-definitions-for-IMS-and-CICS for more information.

This section includes the following topics:



 

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