HP 3000 Manuals HP 3000 Manuals
Chapter 3 DATA COMMUNICATIONS LU 6.2 API/XL by Kathleen Hoski Business Networks Division LU 6.2 API/XL implements the IBM LU 6.2 programmatic interface. Now HP customers have the ability to develop applications that are distributed between a HP 3000 Series 900 and an IBM host in an SNA environment. LU 6.2 or APPC (Advance Program-to-Program Communication) is an architecture developed by IBM for distributed transaction processing in the SNA network. The applications on the Series 900 HP 3000 and IBM host are called Transaction Programs (TPs). These TPs are typically responsible for completing a transaction, such as database update or file transfer.The mapped conversation verbs defined by the IBM LU 6.2 interface have been implemented as LU 6.2 API/XL intrinsics. These intrinsics provide functionality from the base set and several option sets of the mapped conversation verbs. HP customers will write application TPs that call these intrinsics. One component of the LU 6.2 API/XL product is the APPC subsystem. The APPC subsystem is shared by all HP LU 6.2 products. This subsystem provides a common node manager interface among HP LU 6.2 products. SNA Link/XL is an already released product which is an implementation of the IBM Physical Unit Type 2.0. SNA Link/XL consists of the Programmable Serial Interface hardware and SNA Transport and Node Management Services (NMS) software. SNA Link/XL provides the transport between the SNA subsystems on the Series 900 HP 3000 and an IBM host. SNA Link/XL provides PU 2.0 support for LU 6.2 API/XL. FEATURES AND BENEFITS The features and benefits of LU 6.2 API are summarized in the following table: Table 1. LU 6.2 API/XL Features and Benefits --------------------------------------------------------------------------------------------- | | | | Remote Program Invocation | Allows the HP 3000 LU 6.2 API/XL transaction program to | | | remotely invoke a LU 6.2 application resident on an IBM | | | host mainframe. | | | | | Remote Attach | Allows an IBM host mainframe LU 6.2 transaction program | | | to remotely invoke an HP 3000 resident LU 6.2 API/XL | | | transaction program. | | | | | Multiple LU 6.2 Sessions | Up to 8 LU 6.2 sessions are available for up to 8 | | | concurrently running LU 6.2 API/XL transaction programs. | | | | | Mapped Conversation LU 6.2 | Easy-to-use programmatic interface handles | | Programmatic Interface | | | | | | Application Compatibility | LU 6.2 API/XL may be run concurrently with other HP | | | SNA/XL services, such as SNA IMF/XL and NRJE/XL over the | | | same SNA Link to the IBM host. | | | | | Customization | As with all HP SNA/XL services, customizable error and | | | help facilities are provided. | | | | --------------------------------------------------------------------------------------------- FUNCTIONAL DESCRIPTION The TP on the HP 3000 uses the LU 6.2 API/XL intrinsics to communicate with the TP on the IBM host. These intrinsics are used in mapped conversations between the HP 3000 TP and the IBM host TP. Conversations are the logical communication between two TPs. Conversations use a LU-LU session temporarily. The LU 6.2 API/XL intrinsics support the COBOL II, Pascal, C and Transact programming languages and are summarized in the following table: Table 2. LU 6.2 API Intrinsics -------------------------------------------------------------------------------------------- | | | | Intrinsic | Definition | | | | -------------------------------------------------------------------------------------------- | | | | TPSTARTED | Initializes access to the LU 6.2 API intrinsics and reserves | | | resources for a transaction program. | | | | -------------------------------------------------------------------------------------------- | | | | TPENDED | Terminates access to the LU 6.2 API intrinsics and releases | | | resources for a transaction program. | | | | -------------------------------------------------------------------------------------------- | | | | MCALLOCATE | Establishes a mapped conversation between TP's. | | | | -------------------------------------------------------------------------------------------- | | | | MCCONFIRM | Sends a confirmation request to the remote TP and waits for a | | | reply. | | | | -------------------------------------------------------------------------------------------- | | | | MCCONFIRMED | Sends a confirmation reply to the remote TP in response to | | | receiving a confirmation request. | | | | -------------------------------------------------------------------------------------------- | | | | MCDEALLOCATE | Ends a mapped conversation between TP's. | | | | -------------------------------------------------------------------------------------------- | | | | MCERRMSG | Provides the text message description for a given return code. | | | | -------------------------------------------------------------------------------------------- | | | | MCGETALLOCATE | Receives the request from a remote TP to start a conversation | | | and then establishes the conversation. | | | | -------------------------------------------------------------------------------------------- | | | | MCGETATTR | Returns information pertaining to a mapped conversation. | | | | -------------------------------------------------------------------------------------------- | | | | MCFLUSH | Flushes the LU's send buffer. | | | | -------------------------------------------------------------------------------------------- | | | | MCPOSTONRCPT | Causes LU 6.2 API to post the conversation when information | | | arrives. | | | | -------------------------------------------------------------------------------------------- | | | | MCPREPTORCV | Informs the remote TP that the local TP will now receive data on | | | this conversation. | | | | -------------------------------------------------------------------------------------------- | | | | MCRCVANDWAIT | Waits for information to arrive on the mapped conversation and | | | then receives the information. The information an be data, | | | conversation status, or request for confirmation. | | | | -------------------------------------------------------------------------------------------- | | | | MCRCVNOWAIT | Receives information as MCRCVANDWAIT that is available on the | | | mapped conversation without waiting. | | | | -------------------------------------------------------------------------------------------- | | | | MCREQTOSEND | Notifies the remote TP that the local TP is requesting to send | | | data. | | | | -------------------------------------------------------------------------------------------- | | | | MCSENDDATA | Sends the data to the remote TP. | | | | -------------------------------------------------------------------------------------------- | | | | MCSENDERROR | Informs the remote TP that the local TP has detected an error. | | | | -------------------------------------------------------------------------------------------- | | | | MCTEST | Tests the conversation for the receipt of information. | | | | -------------------------------------------------------------------------------------------- | | | | MCWAIT | Waits for the receipt of information on one or more | | | conversation(s). | | | | -------------------------------------------------------------------------------------------- Control of the APPC subsystem through the MPE command interpreter is provided by the APPCCONTROL command. The following functions can be performed by the APPCCONTROL command: * START: Activates the APPC subsystem. * STOP: Deactivates all configured LU-LU sessions and brings down the APPC subsystem. * STATUS: Displays the status of the APPC subsystem. * VERSION: Displays software module version information for the APPC subsystem and LU 6.2 products. * SESSIONS: Sets the number of active LU-LU sessions for a specified APPC session type. * PERFORMANCE: Displays session statistics and performance related data. * DUMP: Dumps the APPC subsystem execution history and control information to a dump file. PRODUCT REQUIREMENTS The following software and hardware is required for LU 6.2 API/XL. Host Hardware and Software Requirements Hardware Requirements: * An IBM host, which can be any IBM plug-compatible computer that supports CICS. The IBM mainframes include the 434x, 438x, 303x, 308x or 309x. * An IBM 3705, 3710, 3720 ICA, or 3725 compatible Communications Controller that supports an SNA line. Software Requirements: * Multiple Virtual Storage/System Product (MVS/SP), or Multiple Virtual Storage/Extended Architecture (MVS/XA) operating system. * Advanced Communication Function for the Virtual Telecommunications Access Method(ACF/VTAM) version 2.1 or later. * Advanced Communication Function for the Network Control Program (ACF/NCP) remote transmission control program version 3.1 or later. * Customer Information Control System (CICS) version 1.7 or later. HP 3000 Hardware and Software Requirements Hardware Requirements: * A 900 Series HP 3000 computer system. * An HP 30253A Programmable Serial Interface (PSI) card compatible with link driver version A.00.01 or later, and the appropriate PSI cables. Generally, the PSI is purchased as part of the SNA Link product. * A full or half duplex data communications line (switched or leased) between the HP 3000 and the host. * A pair of modems for the communication line. * A block-mode terminal which is supported by VPLUS/3000 for SNA node configuration. Software Requirements: * MPE XL Operating System: Version 2.0 or later. * LU 6.2 API/XL * SNA Link bundled hardware and software product (HP 30291). * Node Management Services (part of FOS) * Pascal, C, COBOL II, or Transact compiler SUPPORT SUMMARY PRSD offers four levels of support for each customer with an HP 3000 system: Customer Support Plan (CSP), Account Management Support (AMS), Response Center Support (RCS) and Software Materials Subscription (SMS). In addition to the overall level of system support, customers need to order SMS support for both SNA Link/XL and LU 6.2 API/XL. DOCUMENTATION * Host System Programmer's References: This is a set of guides for the Host System Programmers who are involved in configuring the connection between the host and the HP 3000. (HP SNA Products: Manager's Guide (P/N 5958-8542), HP SNA Products: ACF/NCP and ACF/VTAM Guide (P/N 5958-8543), and HP SNA Products: CICS Guide (P/N 5958-8546)) * SNA Link/XL Node Manager's Guide (P/N 30291-61000): This manual is for the Node Manager and explains the steps required for configuring, monitoring and troubleshooting the SNA Link/XL product. * APPC Subsystem Node Manager's Guide (P/N 30294-61002): This manual is for the Node Manager. It provides instructions for day-to-day operation and subsystem troubleshooting. * LU 6.2 API/XL Node Manager's Guide (P/N 30294-61001): This manual is for the Node Manager and includes a configuration overview, detailed configuration instructions, description of LU 6.2 API conversations, and troubleshooting procedures. * LU 6.2 API Application Programmer Reference Manual (P/N 30294-61000): This manual describes the programmatic interface, and is written for the HP 3000 application programmer who has not necessarily been exposed to data communications or SNA.
![[]](../../pic3k/M000018/F03013c50.gif)