OPS/MVS provides an External Product Interface, or EPI, that, when run on a system that uses VTAM, allows the product to interface with any VTAM application that supports IBM 3270 (SLU2) type virtual terminals. Through the OPS/REXX programming language, you can drive 327X sessions with other VTAM applications, creating OPS/REXX programs to:
How to use the EPI commands from OPSVIEW?
OPS/MVS-Event Management & Automation-for JES2
To assist in developing EPI applications in OPS/REXX, OPSVIEW provides several EPI commands. These commands can be issued from any of the following panels:
With all three methods, first issue the SETTERM termname command. This command designates termname as the current virtual terminal; subsequent commands with a termname of '*' reference this virtual terminal.
To issue commands from the Virtual Terminal List panel, just type in the command you want to enter. For example, entering DEFINE * will define the terminal termname you set with the SETTERM command. If you enter CHANGE * APPLID(YOURTSOAPPLID) and the CHANGE * LOGMODE(yourlogmode) command, it is the same as using the S termname line command, then filling in the resulting panel.
To access the Command Response Display panel for the termname you set with the SETTERM command, enter one of the following:
To enable the terminal, enter ENABLE *. A command response similar to the following displays:
Last command: ENABLE *
----------------------------------------------------------------------------------------
TERMINAL termname HAS BEEN ENABLED
------------------- Return code 0 from EPI cmd ENABLE * -----------------------
The advantage of issuing commands from the Command Response Display panel is that you can see the number of command responses, the actual command response, and the associated return code. A PFkey to RDSCREEN * can be assigned to view the screen content without accessing the Virtual Terminal Screen.
In the Virtual Terminal Screen panel, issue EPI commands from EPI OPS/REXX. The advantage of this method is that you can verify if you are waiting for the Keyboard Unlock and you can see the screens update.
Some EPI commands have the same names as ISPF commands. For example, both the EPI and ISPF have a HELP command and a LIST command. By default, ISPF interprets these commands and does not pass them to the EPI. To force ISPF to pass such commands to the EPI, use the "EPI" command prefix. See the previous EPI LIST * example.
Using the Virtual Terminal Screen along with the Command Response Display to issue EPI commands helps you create, test, and debug your EPI OPS/REXX code.