| Home | ||||||||||
| Products | ||||||||||
| ||||||||||
| Support | ||||||||||
| FAQ | ||||||||||
| Contact | ||||||||||
apXCHANGE-MVS
apXCHANGE MVS is system software that enables any program in any MVS system in an SNA network to connect with and transfer data to any other program on any MVS system in that network. apXCHANGE MVS controls and manages the connections and the data transfer between the programs. Programs interact with each other through the use of two commands: SEND and RECV (RECEIVE).apXCHANGE provides a tightly coupled, distributed, peer-to-peer connection service. It is an inter-process communication (IPC) rather than RPC remote procedure call (RPC) facility. Programs can use apXCHANGE services to synchronize independent program execution in realtime and to pass data back and forth between programs. apXCHANGE MVS transparently provides the synchronization and data passing functions to requesting programs regardless of program location.
apXCHANGE MVS services are made available to the entire system by starting one or more apXCHANGE MVS brokers. A copy of apXCHANGE MVS is started on each MVS system to which access is needed. apXCHANGE MVS can be run as a long-running MVS job or as a started task. Once initialized, all of the apXCHANGE MVS brokers collectively monitor all address spaces in all systems for program-to-program requests. apXCHANGE MVS brokers coordinate program-to-program connections by using their Network Directories. VTAM and cross-memory services are used for the transfer of data between apXCHANGE MVS brokers on behalf of application programs. Cross memory services alone are used for data transfer in a single apXCHANGE MVS broker network.
apXCHANGE MVS operates in any MVS (XA or ESA) environment. If multiple brokers are used, ACF/VTAM Version 2.1 or higher is required.
Copyright © Cardinal Software