Defining OSPI virtual terminals

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

To use the OSPI interface, you must be running VTAM 3.0 or later.

MainView AutoOPERATOR 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, MainView AutoOPERATOR has logon capabilities and complete access to any VTAM application’s data stream. In this way, MainView AutoOPERATOR 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 CICS and IMS for more information.

This section includes the following topics:




This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments