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

Chapter 5 95
Intrinsic Descriptions
MCGetAllocate
Denotes that no confirmation will be used. If a
SyncLevel of 2 is specified, the MCConfirm and
MCConfirmed intrinsics cannot be called during this
conversation, nor can the confirm request option of any
intrinsic be used during this conversation. If any
confirmation is attempted with
SyncLevel set to 2, a
status info value of -31 is returned.
Timer 16-bit signed integer by value; input. This is an integer
from 0 through 28800 that indicates the maximum
number of seconds LU 6.2 API will wait after executing
an intrinsic before returning control to the TP. (28800
seconds = 8 hours.) For example, if the local TP sets its
Timer to 600 (10 minutes) and issues MCRcvAndWait,
and no data arrives within 10 minutes, LU 6.2 API will
issue a status info of +80 to the local TP, which
indicates that the allotted time has expired.
A
Timer value of zero indicates that no timer is to be
used, which means that the program will wait
indefinitely for an intrinsic call to complete.
The following intrinsics use the
Timer :
MCConfirm
MCDeallocate ( DeallocateType = CONFIRM)
MCPrepToRcv ( PrepToRcvType = CONFIRM)
MCRcvAndWait
MCWait
Default: 0
Security 16-bit signed integer by value; input. Reserved for
future use.
NumPIPs 16-bit signed integer by value; input/output. Indicates
the number of Program Initialization Parameters
(PIPs) to be used for this conversation.
Input:
The NumPIPs value that the local TP passes to the
intrinsic specifies the maximum number of PIPs the
local TP can receive from the remote TP on this
conversation.
Output:
The
NumPIPs value that the intrinsic returns to the
local TP indicates the number of PIPs that the remote
TP actually sent to the local TP.