The Full Wiki

More info on IBM Advanced Program-to-Program Communication

IBM Advanced Program-to-Program Communication: Wikis


Note: Many of our articles have direct quotes from sources you can cite, within the Wikipedia article! This article doesn't yet, but we're working on it! See more info or our list of citable articles.


From Wikipedia, the free encyclopedia

In computing, Advanced Program to Program Communication or APPC is a protocol which computer programs can use to communicate over a network. APPC is at the application layer in the OSI model, it enables communications between programs on different computers, from portables and workstations to midrange and host computers.

APPC was developed as a component of IBMs Systems Network Architecture or SNA. Several APIs were developed for programming languages such as COBOL or REXX.

APPC software is available for many different IBM and non-IBM operating systems, either as part of the operating system or as a separate software package. APPC serves as a translator between application programs and the network. When an application on your computer passes information to the APPC software, APPC translates the information and passes it to a network interface, such as a LAN adapter card. The information travels across the network to another computer, where the APPC software receives the information from the network interface. APPC translates the information back into its original format and passes it to the corresponding partner application.

APPC is linked with the term LU 6.2 ( Logical unit type 6.2 )

APPC is to a large extent limited to the IBM operating systems such AS/400, OS/2 and AIX. Microsoft also included SNA support in Microsoft's Host Integration Server. Major IBM software products have included support for APPC, including CICS, DB2, CIM, WebSphere MQ and MVS.

Contrary to TCP/IP, in which both communication partners always possess a clear role (one is always server, and others always the client), the communication partners in APPC are equal, i.e. everyone can be both servers and clients equally. The role, and the number of the parallel sessions between the partners, is negotiated over so-called 'CNOS' sessions (Change Number Of Session) with a special log mode (e.g. at IBM, 'snasvcmg'). Communication of the data is made then by 'data sessions', their log modes can be determined in detail from the VTAM administrator (e.g. length of the data blocks, coding etc..).

With the wide success of TCP/IP, APPC has declined.

External links



Got something to say? Make a comment.
Your name
Your email address