Reliable Transaction Router
Release Notes

There are no known problems with workarounds in this release that are specific to this platform.

8.4 Restrictions

• 14-1-155 Confusion between host and node names
  To fully support protocol failover between TCP/IP and DECnet on Windows NT and Windows 95 systems, the unqualified IP host name of the machine should be the same as the DECnet node name.
• 14-1-160 RTR for Windows requires TCP/IP
  RTR for Windows NT, Windows 95, and Windows 98 requires TCP/IP protocol to be operational, since TCP/IP is used for inter-process communication between the RTR ACP and the application. If TCP/IP is removed using the Network applet in the Control Panel (for example, if DECnet has been installed), then trying to start RTR will result in a Winsock error.
• 14-1-253 V3 WIN32 FE Can't connect to V2 TR
  There is a known deficiency for Windows clients running Pathworks DECnet trying to connect to a V2 router node. The connection does not always come up reliably at the first attempt. If this is a problem in your environment please report it to Compaq.
• 14-1-516 Excessive occurances of ERROR WSASYSNOTREADY 10091 in rtr-log file
  Entries of the following type may be writen to the RTR log file as applications exit:

  %KNL-W-SYSTEM, ioctlsocket FIONBIO blocking, (10091: *No message text found for 10091 (317)*), knl_net.c:1780 %KNL-W-SYSTEM, ioctlsocket FIONBIO nonblocking, (10091: *No message text found for 10091 (317)*), knl_net.c:1708

  
  These are caused by RTR trying to send data from an exit handler installed by RTR in the application. This currently does not work on Windows as the network is unavailable from an exit handler. The problem can be avoided by ensuring that the application closes all its RTR channels prior to exiting.

• 14-1-594 Incomplete cleanup by COMSERV after CLI exits
  When executing commands from the RTR command line (CLI), if the process that opens a channel goes away, the PID associated with that channel also goes away, due to the way Windows NT and Windows 95 identify the requester. This can cause invalid channel arguments, but is normal behavior in a test or experimental environment using the CLI.

Previous

Contents

Contents