This chapter describes corrections to known problems with the MessageQ Client for Windows for Version 4.0A, 3.2-2 and 3.2.
In Version 3.2 some pams_attach_q errors would cause a section of allocated memory to be deallocated twice. This resulted in an "invalid heap pointer" error. This has been corrected in Version 4.0A.
In Version 3.2, an application error occurred in MSVCRT40.DLL when tracing messages, if the message contained non-ASCII data. This problem has been corrected in Version 3.2-2
In Version 3.2, messages could be misdirected by the OCX if more than one message was pending when polling was enabled. If this occurred, the OCX delivered all messages to the message control which had a MsgType value matching the first pending message. This problem has been corrected in Version 3.2-2.
The MessageQ Client for Windows Custom Control library (dmqclcc.ocx) provided on the Version 3.2 kit contained an error which caused an out-of-process OLE server to throw an exception if the PollingRate property was set to a non-zero value. The Version 3.2-2 kit contains an updated OCX to correct this problem.
The Version 3.2 kit would generate an application error on Windows 95 if the application was using timer-based automatic reconnect or statistics logging. This problem has been corrected in Version 3.2-2.
In Version 3.2, the installation program used the CPU environment variable to determine the machine architecture. This could cause an installation on Alpha to incorrectly install Intel files if the CPU environment variable was undefined. For Version 3.2-2, the installation program checks both the CPU and PROCESSOR_ARCHITECTURE environment variables.
It is now possible to use either an IP host name or address, or a DECnet node name or address as the Host name in dmq.ini file. This correction applies to both the Default Server and the Failover Server entries. Previous versions did not support the use of IP or DECnet addresses.
Previous versions of the 32-bit DLL (dmqcl32.dll) were not able to trace messages to the Event Watcher utility on Windows NT or Windows 95. This limitation has been corrected in the Version 3.2 release. On Windows NT or Windows 95 it is no longer necessary to start the Event Watcher before running your application.
Support for automatic reconnect to permanent queues used by the CLS for OpenVMS is now available using CLS version 3.0.006c or 3.0-10 included in the MessageQ for OpenVMS Version 3.0 release.
All of the API restrictions based on using a Multithreaded CLS on OpenVMS are removed using CLS Version 3.0-10 (or later). This version of CLS is included in the MessageQ for OpenVMS Version 3.0 release. Previous versions of CLS for OpenVMS on MessageQ Versions 2.0 and 2.1 did not support the pams_set_timer function and some specific selection filter combinations.