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

Chapter 5 97
Intrinsic Descriptions
MCGetAllocate
HP 3000 then runs the local TP, which calls MCGetAllocate to allocate
the local side of the conversation.
Once the MCGetAllocate intrinsic has executed successfully, the local
TP is in Receive state and the remote TP is in Send state.
When the MCGetAllocate intrinsic executes successfully, a ResourceID
is assigned to the allocated conversation. Just as the TPID uniquely
identifies one among many possible instances of the same TP, the
ResourceID uniquely identifies one among many possible
conversations conducted by one instance of a TP.
Every conversation requires one session on the APPC subsystem. On
MPE V, only 8 sessions may be active on the APPC subsystem at once.
On MPE XL, the APPC subsystem can support a maximum of 256
active sessions. The available active sessions must be shared among all
the TPs running on the APPC subsystem. For more information on
session limits, see the APPC Subsystem on MPE V Node Manager’s
Guide or the APPC Subsystem on MPE XL Node Manager’s Guide.
MCGetAllocate allows you to receive initialization information from
the remote TP in the Program Initialization Parameters (PIPs). These
parameters can be used, for example, to indicate whether a TP is
processing daily information or an end-of-month report. They can also
be used to inform the local TP of the type of data it will receive, the size
of the records, etc. PIPs can be used to transmit any special information
the local TP must receive from the remote TP before it executes.
Remotely Initiated Conversations on MPE V
On MPE V, MCGetAllocate can be called only once during the
execution of a TP. That is, each execution instance of a TP can have only
one conversation initiated by the remote TP.
On MPE V, when a conversation is initiated by the remote TP, the
MCGetAllocate intrinsic must be the first LU 6.2 API intrinsic called
after the TPStarted intrinsic, unless the TPEnded intrinsic is called and
the program terminated.
On MPE V, the TP name sent by the remote TP is the name of a job file
located in the APPC.SYS group and account. This TP name must match
the name of the job file exactly. The job file contains the MPE RUN
command that starts up the local TP. The executable TP file can reside
in any group and account. When LU 6.2 API receives the TP name from
the remote TP, it streams the job, which in turn runs the local TP. The
value returned in the
LocalTPName parameter is the TP name sent by
the remote TP.
Remotely Initiated Conversations on MPE XL
On MPE XL, the TP name sent by the remote TP is configured in the
APPC subsystem branch of NMMGR. The TP name is associated with a