TS/MP 2.5 Pathsend and Server Programming Manual

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 requestor 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 the send, and there are no restrictions on
ENDTRANSACTION other than those associated with calls to the WRITEREAD
procedure.
The default is 0.
flags.<0:13> must be 0.
NOTE: For information on setting flag 9, see “Bridging Pathsend API into Pathway Domain”
(page 113).
outputscsend-op-num
INT:ref:EXT:1
returns the server-class send operation number. You can use the server-class send operation number
in place of the file-number parameter in calls to CANCEL, CANCELREQ, and AWAITIOX for
nowait sends, and in calls to FILEINFO for waited and nowait sends, to indicate that the calls refer
to server-class send operations. The value of scsend-op-num is determined on the first successfully
initiated nowait send. This value is returned on every subsequent nowait send that is initiated
successfully. A value of -1 is returned for nowait sends that are not initiated successfully. A value of
-1 is always returned for waited sends.
For more information about the server-class send operation number, see “Server-Class Send Operation
Number” (page 110) later in this chapter.
inputtag
INT(32):value
is used for nowait I/O only. The tag is stored by the system and then passed back to the application
by the AWAITIOX procedure when the nowait operation is completed. You can use the tag parameter
to identify multiple nowait I/O operations. For waited I/O, this parameter is not used and can be
omitted. The default is 0D.
Considerations
If the SERVERCLASS_DIALOG_BEGIN_ procedure fails but does not return a valid dialog identifier,
the dialog was never created. In this case, there is no need to abort the dialog.
For additional considerations, see “Usage Considerations for Pathsend Procedures” (page 108) at
the end of this chapter.
SERVERCLASS_DIALOG_BEGINL_ Procedure
The SERVERCLASS_DIALOG_BEGINL_ procedure initiates a dialog with a server process in a
server-class and sends the first message in the dialog.
The procedure identifies the server-class to the system and returns a dialog identifier for subsequent
dialog operations. A SERVERCLASS_DIALOG_BEGINL_ call must match with a
SERVERCLASS_DIALOG_ABORT_ or SERVERCLASS_DIALOG_END_ call at the end of the dialog.
SERVERCLASS_DIALOG_BEGINL_ Procedure 81