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

94 Chapter5
Intrinsic Descriptions
MCGetAllocate
the local TP must convert it from EBCDIC to ASCII. The MPE
CTRANSLATE intrinsic, or the intrinsic on MPE XL, may be used.
On MPE XL, LocalTPName is an input ASCII parameter. It must match
the value in the
LocalTPName parameter of the TPStarted intrinsic.
The
LocalTPName parameter contains the TP name sent by the remote
TP. This TP name must be configured in the APPC configuration branch
of NMMGR. The configuration file associates each TP name with a job
file, which may be located in any group and account. When LU 6.2 API
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 configured to receive
multiple allocate requests from remote TPs, LU 6.2 API waits until
any conversation with the local TP process has been deallocated, and
then it allocates a conversation with the local TP process.
2. If the local TP is not active, or if it is configured to receive only one
allocate request per execution instance, LU 6.2 API initiates a new
local TP process by streaming the job file associated with the TP
name. Then, it allocates a conversation with the local TP process.
A remotely initiated TP on MPE XL is configured 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 configuration.
ResourceID Required; 16-bit signed integer; output. This number
identifies the conversation being allocated. It must be
used in all subsequent intrinsic calls, so that LU 6.2
API can determine which conversation the intrinsic
calls belong to.
Status Required; 32-bit signed integer; output. Indicates the
result of intrinsic execution. See the “Status
Parameter” section, earlier in this chapter, for more
information.
SyncLevel 16-bit signed integer; output. This parameter
determines the synchronization level (whether or not
confirmation will be used) for this conversation.
Possible values are as follows:
0 = CONFIRM
Denotes that the MCConfirm and MCConfirmed
intrinsics can be called. It also means that the confirm
request option of any intrinsic may be used.
2 = NONE