RSC/MP Programming Manual

API Function Descriptions RscNotifyWin [RSCNOT]
Return Value
The return va lue is zero if the function is successful; otherwise, the function returns
one of these result va lues:
RSC_PC_HEAP_EXHAUSTED
22
RSC_INTERNAL_ERROR
102
RSC_NOT_IMPLEMENTED
103
RSC_RESOURCE_FAILURE
104
RSC_PARAMETER_ERROR
105
Remarks
This function is supported on Windows platforms only. It is not for use in installations
where RSC/MP runs as a service or for applications that run under Terminal Services.
Before calling RscNotifyWin:
Create a connection handle by calling the RscConnect function.
Create a session handle by calling the RscBeginSession function.
Identify a window through which your application wi ll receive notifications, and
identify a message number to be sent to that window.
Then, call RscNotifyWin according to your application‘s needs:
To receive notification of no waited RscWriteRead completions, call RscNotifyWin
once with uType set to RSC_NOTIFY_IO before calling RscWriteRead for the first
time. This approach causes RSC/MP to send a message to your window once for
each subsequent nowaited RscWriteRead completion, until the session ends.
To receive notification of UMS messages, call RscNotifyWin once with uType set to
RSC_NOTIFY_UMS. This approach causes RSC/MP to send a message to your
window once for each subsequent UMS message received for the session, until
the session ends.
You might choose to combine these methods in order to receive notifications of both
types, by calling RscNotifyWin twice. In this case, your application can distinguish
between the two types either by using separate windows or by sharing a common
window and using unique message numbers.
Because the notification message sent to yo ur window does not identify a specific
nowaited I/O handle, your application should generally supply an I/O ha ndle of
RSC_IO_CHECK_ALL when calling RscIoCheck after receiving a notification.
HP NonStop Remote Server Call (RSC/MP) Programming Manual — 522360-006
10 - 27