RSC/MP 7.2 Programming Manual

API Function Descriptions
HP NonStop Remote Server Call (RSC/MP) Programming Manual—522360-004
10-25
RscNotifyThread [RSCNOTH]
If your application uses multiple concurrent RSC/MP sessions, then you can exploit
this behavior and use a single thread to receive nowaited I/O completion notifications
for many sessions, supplying the ulConnectionHandle and ulSessionHandle from each
notification message in your corresponding call to RscIoCheck. The same holds true
for UMS notifications.
If RSC/MP fails to post a notification message to your thread’s message queue, it does
not retry. Under Win-32, message queues are dynamically resized by the system as
necessary; an error in posting a message generally indicates a severe error (absence
of a message queue for the receiving thread, termination of the receiving thread, or
system-wide resource exhaustion).
Note. When RSC/MP runs as a service, the PostThreadMessage function may not be able to
make a successful notification because the RSC service is running in a different desktop from
the RSC/MP application, or because of a security restriction. The underlying limitations in the
PostThreadMessage function changed between Windows NT and Windows 2000, as
described in the Windows SDK documentation. In general, RscNotifyThread should not be
used in applications for which RSC/MP will run as a service, nor in applications that run under
Terminal Services.