gtpc2mam | C/C++ Language Support User's Guide |
The function provided by the TPF Advanced Program-to-Program Communications
(TPF/APPC) interface is an implementation of IBM's Advanced
Program-to-Program Communications (APPC) architecture. TPF/APPC is an
interface that allows TPF transaction programs to communicate with remote SNA
nodes that have implemented the APPC interface using LU 6.2
protocols. See the TPF ACF/SNA Data Communications
Reference for more information about TPF/APPC support in general.
Before using this support, you must be familiar with the SNA LU 6.2
protocol architecture as defined in the following documents:
- IBM Systems Network Architecture Format and Protocol
Reference Manual: Architecture Logic for LU Type 6.2
- IBM Systems Network Architecture LU 6.2
Reference: Peer Protocols
- IBM Systems Network Architecture Transaction
Programmer's Reference Manual for LU Type 6.2.
This chapter contains a general description of the TPF/APPC mapped
conversation interface, and an alphabetic listing of each function. The
following information is shown for each function:
- Format
- The function prototype and a description of any parameters.
- Description
- What service the function provides.
- Return Codes
- A list of return codes for the specific function.
- Note:
- This section replaces the Normal Return and Error Return sections that are
used in TPF API Functions.
- Programming Considerations
- Remarks that help the programmer to understand the correct use of the
function and any side effects that may occur when the function is
executed. If the use of a particular function affects the use of
another function, that is also described.
- Example
- A code segment showing a sample function call.
- Related Functions
- Where to find additional information pertinent to this function.
Notes:
- Remember to include tpfeq.h in the source program, even
though it is not shown in any of the function prototypes. The
tpfeq.h header must be the first header file included in any
TPF C source module.
- Programs that issue any of the API functions for the mapped conversation
verbs must be authorized in the allocator to issue restricted use macros and
must have KEY0 write authorization.
See TPF/APPC Basic Conversation Functions. for descriptions of the TPF/APPC basic conversation
functions.