RSC/MP Programming Manual

API Function Descriptions RscNotifyThread [RSCNOTH]
Remarks
This function is supported on the Windows platform only. It is not for use in ins tallations
where RSC/MP runs as a service or for application that run under Terminal Services.
Before calling RscNotifyThread:
Create a connection handle by calling the RscConnect function.
Create a session handle by calling the RscBeginSession function.
Identify a thread through which your application will receive notifications.
Identify a message number to be sent to that thread, and ensure that the receiving
thread has a message queue (see the Windows API documentation for information
about message queues).
Then, call RscNotifyThread according to your application‘s needs:
To receive notification of no waited RscWriteRead completions, call
RscNotifyThread 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 thread once for each subsequent nowaited RscWriteRead
completion, until the session ends.
To receive notification of UMS messages, call RscNotifyThread once with uType
set to RSC_NOTIFY_UMS. This approach causes RSC/MP to send a message to
your thread once for each subsequent UMS message received for the session,
until the session ends.
You can choose to combine these methods in order to receive notifications of both
types, by calling RscNotifyThread twice. In this case, your application can distinguish
between the two types either by using separate threads or by sharing a common
thread and using unique message numbers.
The RscNotifyThread function requests delivery of messages to a thread‘s message
queue only; it does not perform any RSC/MP thread registration. A thread that simply
receives notifications is not required to register.
Note. Any thread other than the main thread that will call RSC/MP API functions (including
RscIoCheck and RscUmsCheck) must register itself with RscRegisterThread.
Because the notification message sent to yo ur thread 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.
The connection and session handles are passed back to an application, through the
wParam and lParam parameters, respective ly; RSC/MP uses a Windows API call to
deliver notification:
PostThreadMessage(ulThreadId, ulWinMessage, ulConnectionHandle,
ulSessionHandle);
HP NonStop Remote Server Call (RSC/MP) Programming Manual — 522360-006
10 - 24