Communication between a z/VM and Non-z/VM System
In Figure 1, AVS and VTAM connect the TSAF collection (made
up of two z/VM® systems) to a non-z/VM system in the SNA network. AVS translates
information between APPC/VM and APPC/VTAM (the VTAM implementation of APPC).
VTAM provides the path between the TSAF collection and the system in the SNA
network.
Suppose you have a program, running in a non-z/VM system located in
the SNA network, that requests data from a database. Your request is made
using APPC. The database manager program is located in a system in the TSAF
collection. Your request is routed to the TSAF collection over a path through
the SNA network between your workstation and VTAM in the TSAF collection.
VTAM routes your request to AVS which translates the request from APPC/VTAM
to APPC/VM. TSAF then routes the connection to the database manager program
through the path established between TSAF virtual machines because AVS and
the database manager are on different systems in the collection. The database
manager program gets the data and then sends it back to your program.
CPI Communications programs on workstations and APPC/VM programs on VM/ESA systems in a CS collection can communicate with APPC programs located in an SNA network. The AVS component and VTAM provide a path between VM/ESA systems in the CS collections and the SNA network. ISFC, AVS, and VTAM provide a transparent connection between the CPI Communications or APPC/VM program in the CS collection and the APPC program in the SNA network. Using ISFC, AVS, and VTAM, programs in the CS collection can access wide area network resources and programs in this network can communicate with resources in the CS collection.