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

98 Chapter5

Intrinsic Descriptions

MCGetAllocate

job ﬁle through conﬁguration. When the HP 3000 receives the TP name

from the remote TP, it does one of two things:

1. If the local TP is already active, and if it is conﬁgured to receive

multiple allocate requests from remote TPs, LU 6.2 API waits for

any current conversation with the local TP process to be deallocated,

and then it allocates a conversation with the local TP process.

2. If the local TP is not active, or if it is conﬁgured to receive only one

allocate request per execution instance, LU 6.2 API initiates a new

local TP process by streaming the job ﬁle associated with the TP

name. Then, it allocates a conversation with the local TP process.

A remotely initiated TP on MPE XL is conﬁgured to conduct either

single or multiple conversations with the remote TP. A TP that

conducts a single conversation must call MCGetAllocate only once;

another instance of the TP will be started each time a remote TP

requests a conversation. A TP that conducts multiple conversations can

call MCGetAllocate many times; only one instance of it may be running

at once. See the APPC Subsystem on MPE XL Node Manager’s Guide

for more information on TP conﬁguration.

On MPE XL, a timer for the MCGetAllocate intrinsic may be

conﬁgured. The timer prevents the local TP from being suspended

indeﬁnitely if no allocate request arrives from the remote TP. The timer

is a value from 0 (no timer) to 480 minutes (8 hours), conﬁgured

through NMMGR/XL. If your program calls MCGetAllocate, and no

allocate request arrives from the remote TP before the timer expires,

control is returned to your program. See the APPC Subsystem on

MPE XL Node Manager’s Guide for more information.

The

LocalTPName

passed in the MCGetAllocate intrinsic must be

conﬁgured in the APPC subsystem branch of NMMGR. It must match

the TP name sent by the remote TP, and it must match the

LocalTPName

passed in the TPStarted intrinsic.

NOTE

If you are migrating a TP to LU 6.2 API/XL from LU 6.2 API/V or from

a version of LU 6.2 API/XL prior to the Node Type 2.1 version, you must

change the

LocalTPName

parameter from an output parameter to an

input parameter.

Figure 5-3 shows how a local TP is started when a conversation

allocation request is received from a remote TP.