The APPC/MVS Programming Interface
Like CPI Communications, APPC/MVS's MVS-specific services let your programs communicate with other programs on the same z/OS system, OS/390 systems, or other operating systems in an SNA network. Unlike CPI Communications, programs using the MVS-specific services are not portable to other systems. MVS-specific services make use of the MVS/ESA architecture, including data spaces and asynchronous processing, and also provide TP scheduling options, server functions, and test services.
The MVS-specific services are divided into the following categories:
- TP Conversation Services
- Provide access to all the conversation functions described in The Elements of Conversation. This set of services is to be used by transaction programs and has equivalent SNA LU 6.2 services and CPI Communications routines.
- Advanced TP Services
- Provide access to more advanced transaction program interfaces, including scheduling options and test services.
- Allocate Queue Services
- Provide access to LU 6.2 server functions, which allow you to direct inbound allocate requests to server address spaces. These services have no equivalent SNA LU 6.2 services or CPI Communications routines. The APPC/MVS allocate queue services are described in z/OS MVS Programming: Writing Servers for APPC/MVS.
- System Services
- Provide access to system services not normally used by transaction programs, but used by other MVS components, management subsystems, and transaction schedulers. The APPC/MVS system services are described in z/OS MVS System Messages, Vol 3 (ASB-BPX).