TS/MP 2.5 Pathsend and Server Programming Manual

Considerations
• HP recommends that no-waited IOs initiated by SERVERCLASS_DIALOG_BEGINL_ must be
completed by a call to AWAITIOXL. If the message size is less than or equal to 32KB,
AWAITIOX can also be used.
• If both the read-write buffers used in the call are 2 MB in size, you might be able to do only
7 concurrent no-waited calls, instead of 255. For more information, see “Retaining Concurrent
Sends Limit” (page 114)
• If the SERVERCLASS_DIALOG_BEGINL_ 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_END_ Procedure
The SERVERCLASS_DIALOG_END_ procedure cleans up resources for the specified
dialog after the server has ended it.
A call to SERVERCLASS_DIALOG_BEGIN_ must be matched by a call to
SERVERCLASS_DIALOG_ABORT_ or SERVERCLASS_DIALOG_END_ at the end of
the dialog. For the SERVERCLASS_DIALOG_END_ procedure to work correctly, the
server must previously have ended the dialog by replying with an error value other
than FEContinue (70).
This procedure does not perform any I/O operations.
Syntax
The syntax of the SERVERCLASS_DIALOG_END_ procedure is:
! i
error := SERVERCLASS_DIALOG_END_ (
dialog-id );
returned valueerror
INT
returns an error word containing one of these values:
0 (FEOK) indicates that the call was successful.
233 (FESCErr) indicates that an error occurred. You can call the SERVERCLASS_SEND_INFO_
procedure to get detailed information about the error.
inputdialog-id
INT(32):value
is the dialog identifier previously returned from the SERVERCLASS_DIALOG_BEGIN_ call that began
the dialog.
This is a mandatory parameter.
Considerations
None.
SERVERCLASS_DIALOG_SEND_ Procedure
The SERVERCLASS_DIALOG_SEND_ procedure initiates a send within the specified dialog.
SERVERCLASS_DIALOG_END_ Procedure 85