APPC allows two programs to communicate, and LU 6.2 defines
the actions or verbs that each program may
execute in an APPC application.
The Application Program Interface (API) consists of a set
of intrinsics. These intrinsics are predefined subroutines that
implement the LU 6.2 architected verbs. They can be called from
within application programs.
Hewlett-Packard's LU 6.2 API implements the set of mapped conversation
verbs defined for LU 6.2. SNA defines two types of conversations
between communicating programs: basic conversations and mapped
conversations.
In a basic conversation (one that uses
basic conversation verbs), the application must perform some error
recovery and data formatting activities.
In a mapped conversation (one that
uses mapped conversation verbs), the application focuses only on
data handling and relies on an underlying program or system to provide
error recovery and data formatting. Hewlett-Packard's LU 6.2 API
supports mapped conversations.
Supported Languages |
 |
The programming languages supported by LU 6.2 API intrinsics
are listed below, for MPE V and MPE XL systems:
MPE V: | MPE XL: |
|---|
COBOL II | COBOL II |
Pascal | Pascal |
Transact | Transact |
| C |
IBM's CICS |
|
Hewlett-Packard's LU 6.2 API intrinsics are often
used to write applications that communicate with IBM LU 6.2 applications
running under the Customer Information Control System
(CICS). CICS is a subsystem that enables data transmitted
over communication lines to be processed by host application programs.
These host application programs can be written in COBOL, PL/1, or
Assembler. Appendix B contains a sample CICS program and an HP 3000
program that communicates with it using LU 6.2 API.
