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

78 Chapter5
Intrinsic Descriptions
MCAllocate
NumPIPs
16-bit signed integer by value; input. This is the
number (from 0 through 16) of Program Initialization
Parameters (PIPs) to be sent to the remote TP. A
NumPIPs value of 0 indicates that no PIP data will be
sent.
Default: 0
PIPLengths
16-bit signed integer array; input. This is an array of up
to 16 integers that indicate the lengths, in bytes, of the
Program Initialization Parameters (
PIP1...PIP16 ).
The combined length of all the PIPs must not be greater
than 1980 bytes.
NOTE If NumPIPs is greater than 0, the PIPLengths parameter is required. If
NumPIPs is zero, the PIPLengths parameter is ignored.
PIP1, PIP2,...PIP16
character array; input; EBCDIC. Each PIP is a
character array containing a Program Initialization
Parameter for the remote TP. PIPs are used to transmit
any special information the local TP wants to send to
the remote TP at conversation initiation. The combined
length of all the PIPs must not be greater than 1980
bytes.
Because LU 6.2 API performs no translation on this
array, the local TP must convert it from ASCII to
EBCDIC. The MPE CTRANSLATE intrinsic, or the
NLTRANSLATE intrinsic on MPE XL, may be used.
NOTE If NumPIPs is greater than 0, the specified number of PIPs must be
supplied. If NumPIPs is zero, all PIPs are ignored.
Description
The MCAllocate intrinsic establishes a conversation between the local
TP that calls it and the remote TP specified in the
RemoteTPName
parameter. Once the MCAllocate intrinsic has executed successfully,
the local TP is in Send state and the remote TP is in Receive state.
When the local TP initiates a conversation, the MCAllocate intrinsic
must be the first LU 6.2 API intrinsic called after TPStarted, unless
the TPEnded intrinsic is called and the program terminated. See
MCGetAllocate, later in this chapter, for information about
conversations initiated by the remote TP.