LU 6.2 API Application Programmer's Reference Guide (30294-90008)

ManualsBrandsHP ManualsSoftwareMPE/iX 6.0 Operating System

Chapter 2 35

Conversations

Establishing Conversations

a. If the local TP is conﬁgured to conduct multiple remotely initiated

conversations, and if it is already active and in conversation, the

APPC subsystem must queue the allocate request until the local

TP ﬁnishes the current conversation and calls the

MCGetAllocate intrinsic again. If the local TP is not currently

running, the APPC subsystem must stream the job that runs the

local TP.

b. If the local TP is conﬁgured to conduct only one remotely initiated

conversation, the APPC subsystem must stream the job that runs

the local TP.

4. The local TP must be coded to receive the allocate request from the

remote TP.

NOTE

On MPE XL, any local TPs that will conduct remotely initiated

conversations must be conﬁgured through NMMGR/XL. See the APPC

Subsystem on MPE XL Node Manager’s Guide for information on TP

conﬁguration.

Local Programmer Tasks

To prepare for remotely initiated conversations on MPE XL, you must

do the following:

1. Work with the programmer on the remote system to design and code

the TP. The local TP can be designed to receive multiple allocate

requests from the remote TP, or it can be designed to receive only

one allocate request. A TP designed to receive multiple allocate

requests must call the MCGetAllocate intrinsic multiple times. A

TP designed to receive only one allocate request must call the

MCGetAllocate intrinsic only once.

2. Together with the programmer on the remote system, decide on a

name for the TP. Make sure you and the other programmer agree on

the TP name; it must be coded into the local TP, and it must be sent

by the remote system in the allocate request. Tell the node manager

the TP name. The node manager must conﬁgure the TP name in the

APPC subsystem conﬁguration ﬁle.

3. Code the TP name into the

LocalTPName

parameter of the

MCGetAllocate intrinsic and the

LocalTPName

parameter of the

TPStarted intrinsic.

4. Ask the node manager for the name of an appropriately conﬁgured

session type, or ask the node manager to conﬁgure a session type for

the conversation. The session type must direct data to the remote

LU that serves the remote TP.

5. Code the name of the session type into the

SessionType

parameter

of the MCGetAllocate intrinsic.