The EPI is not complicated, but to use it you should understand the following terms:
A VTAM application is an application known to VTAM by its VTAM application ID.
An external product is an application or group of applications external to CA OPS/MVS with which the EPI can communicate. Usually each external product uses a single VTAM application ID, but this is not always true. A single product can use multiple VTAM application IDs, or a single VTAM application ID can give access to multiple external products.
Note: The EPI communicates only with external products that support IBM 327X type virtual terminals under VTAM. The EPI establishes sessions only with applications that are in the same VTAM domain as CA OPS/MVS or which are accessible as resources from that domain.
A virtual terminal is anything that looks like a physical terminal to VTAM. In this sense, the EPI emulates a physical terminal.
A disabled terminal is not connected to VTAM (no ACB is open for it) and cannot communicate or establish a session with any external product. Disabling a virtual terminal is the equivalent of shutting the power off on a physical terminal.
An enabled terminal is connected to VTAM (an ACB is open for it). An enabled virtual terminal can establish a session with any external product, or can be in session with an external product.
A virtual terminal is active when it is enabled and has established a session with an external product.
Note: After the EPI establishes a VTAM session with an external product, the external product can present a prompt sequence for signon information. While the EPI shows that a session has been established at that point, the external product cannot consider the session established.
An EPI session is a logical connection through a VTAM session between CA OPS/MVS and an external product. The EPI communicates only with an external product if a session exists between the two products.
|
Copyright © 2014 CA.
All rights reserved.
|
|