TS/MP Pathsend and Server Programming Manual (H06.05+, J06.03+)

This parameter is required.
inputmaximum-reply-len
INT:value
is the maximum number of bytes that the reply message from the server class can contain. The range
of acceptable values is 0 through 32767 bytes.
No more than maximum-reply-len bytes of the actual reply are placed into message-buffer upon
successful completion of a send.
It is not an error if the server replies with a byte count not equal to the maximumreply- len value
specified by the requester in the call to this procedure. If the server replies with a byte count greater
than the
maximum-reply-len
value, the actual bytes transferred are truncated to maximum-reply-len.
This parameter is required.
outputactual-reply-len
INT:ref:EXT:1
returns a count of the number of bytes returned in the server process reply. This parameter is for
waited I/O only and can be omitted for nowait I/O. The return value of this parameter is 0 if nowait
I/O is used. For nowait I/O, the actual reply length is returned by AWAITIOX.
inputtimeout
INT(32):value
specifies the maximum amount of time, in hundredths of a second, that the LINKMON process waits
for the completion of this send. This value must be either -1D or a value greater than 0D. The default
is -1D (wait indefinitely).
If there is an outstanding I/O operation to a server process when a SERVERCLASS_DIALOG_BEGIN_
operation times out, the I/O operation is canceled.
See “Timeout Considerations for Pathsend Programming” (page 106) later in this section for details
about timeout for waited and nowait operations.
For more information on Pathsend error 904 and file-system error 40, see “Server Timeout” (page 106).
inputflags
INT:value
flags.<15>
with a value of 1 indicates that this operation is to be performed nowait. A value of 0 indicates
that this operation is to be performed waited. The default is 0.
flags.<14>
if set to 0, selects the one-transaction-per-dialog model. In this model, the dialog records the
transaction identifier that is current at the time of the SERVERCLASS_DIALOG_BEGIN_ call.
Subsequent SERVERCLASS_DIALOG_SEND_, SERVERCLASS_DIALOG_ABORT_, and
SERVERCLASS_DIALOG_END_ calls that use the returned dialog-id must specify this transaction
identifier, or the calls will fail. ENDTRANSACTION will fail unless the dialog has ended (not
aborted).
When this bit is set to 0, the TMF subsystem treats a dialog like an I/O operation: the
ENDTRANSACTION operation fails until the dialog has finished. The same restriction applies
to a nested server (a server that receives a request and then becomes a requester to other
servers): if a server receives a message in a dialog and then initiates a dialog with another
server, it must complete the entire initiated dialog before replying to the message from the
received dialog.
A value of 1 selects the any-transaction-per-dialog model. In this model, all server-class send
operations within the dialog will contain the transaction identifier that is current at the time of
SERVERCLASS_DIALOG_BEGIN_ Procedure 81