DCE Application Programming Guide

NonStop DCE Jacket Functions
HP NonStop DCE Application Programming Guide—429551-003
C-10
SERVERCLASS_DIALOG_BEGIN_
cannot determine whether the canceled message was sent or canceled before the server pro-
cess finished processing the request. If the begin is canceled because of expiration of the tim-
eout parameter, then the function returns with an error value of 233 (FEScError);
DCE_SERVERCLASS_SEND_INFO_() will show Pathsend error 918 (FEScSend Opera-
tionAborted) and Guardian file-system error 40 (FETimedOut
The message_buffer parameter should refer to static or heap-allocated storage.
Also, it is possible to pass a heap-allocated RPC parameter (pointer). Also, since Native DCE
threads follow the static model, thread stacks (including thread stack variables) reside in the
heap. When the RPC parameter (input) is passed to the function and output is received in the
same buffer, there is no effect on the input parameter because it refers to the same heap stor-
age before and after the thread switch. But the application writer needs to ensure that enough
heap storage is available to receive the output from the function. This will NOT be detected
by the threads runtime.
Multiple DCE_SERVERCLASS_DIALOG_BEGIN_() operations can be in progress in
different threads within a process; the maximum number of concurrent calls is determined by
the number of threads and the Pathsend limit of 512 for each LINKMON.
RETURN VALUES
The function returns the following Guardian file-system error numbers:
0 (zero) (FEOK)
if the DCE_SERVERCLASS_DIALOG_BEGIN_() operation is completed
successfully.
70 (FEContinue)
if the server is ready for next message in the dialog.
233 (FEScError)
Call DCE_SERVERCLASS_SEND_INFO_() to get more information about the
error.
RELATED INFORMATION
Functions: DCE_SERVERCLASS_SEND_INFO_(3).
Books: TS/MP Pathsend and Server Programming Manual.
Figure C-3. DCE_SERVERCLASS_DIALOG_BEGIN_(3) Reference
Page (page4of4)