Resolution:
Description:
= = = = = =
Why is more latency seen on VMS platforms when sending and receiving TIBCO Rendezvous (RV) messages?

OS
= =
VMS specific.

Resolution
= = = = = =

The latency observed is possibly the result of not linking with the TIBCO recommended option /THREADS_ENABLE=UPCALLS.  In most circumstances, there is not a problem with using this option when linking RV applications.  In a small number of cases where customers include third party libraries which cannot be used with this option, there is no resolution for the increased latency.

This issue is not specific to any particular TIBRV or OpenVMS release. Multi-threaded applications on OpenVMS will display this behavior unless UPCALLS are enabled.  In RV 5.x and earlier, RV was single-threaded which explains why the behavior was not seen. As RV is now a multi threaded application you will need to link the application
with the  /THREADS_ENABLE=UPCALLS option.

Why is more latency seen on VMS platforms when sending and receiving TIBCO Rendezvous (RV) messages?