Chapter 2 . Corrections to Known Problems

This chapter describes corrections to known problems for DECmessageQ for UNIX, Versions 4.0A, 4.0, 3.2B, 3.2A and 3.2.

Corrections to MessageQ Version 4.0A

This section describes corrections to MessageQ for UNIX, Version 4.0A.

Corrections to MessageQ Version 4.0

This section describes corrections to MessageQ for UNIX, Version 4.0.

Corrections to the PAMS API

The decnet_node field is now part of the LIST_ALL_GROUPS message as documented in the BEA MessageQ Programmer's Guide.
Previously, the pams_get_msg returned messages in the wrong order when using a selection mask and an ordering of PSEL_TYPE, PSEL_CLASS, and PSEL_SOURCE. This problem has been corrected.
The pams_get_msg and pams_get_msgw functions now properly fill in the transfer_size field when the user supplies a show buffer.
Previously the pams_set_select function did not accept multi-reader queues in the 'queue' field of the selection array component structure. This problem has been corrected.
The return code PAMS__NOTDCL is no longer a valid return code for the pams_exit() call. The only valid return code for the pams_exit function is now PAMS__SUCCESS.
Applications can now supply the queue address of an unattached multi-reader queue as a response queue using the pams_put_msg function.
Previously, the MessageQ UNIX Client returned the value PAMS__JOURNAL_ON from pams_attach_q function if MRS was enabled but the CLS security file did not grant access to the client. This has been changed to return PAMS__NOACCESS, and the journal file is not opened.
Previously, messages enqueued on NCR UNIX systems were labeled as big endian format. This problem has been corrected and these messages are now properly labeled as little endian format.

Corrections to Link Drivers

Previously, the memory usage of the link drivers would increase as a result of failed connection attempts to remote groups. This problem has been corrected.

Corrections to the Monitor Utility

The Monitor utility now correctly displays queue traffic rates and queue traffic counts when monitoring more than 100 queues.
Previously, displaying statistics for a large number of queues could cause the Monitor utility to hang. This problem has been corrected.

Corrections to Message Recovery Services

Previously, when multiple processes attached to a multi-reader queue as their primary queue, duplicate sequence numbers could be generated causing the journal process to exit. This problem has been corrected.
Previously, the journal process failed to mark journal files as open when they were reopened as a group restarted. Failure to mark these files as open, prevented the journal process from recovering these files because they were not identified as requiring recovery. This problem has been corrected.

Corrections to MessageQ for UNIX Version 3.2B

This section describes corrections to MessageQ for UNIX, Version 3.2B.

Corrections to Link Drivers

The Link Sender process no longer leaks memory on failed connections to remote groups.
The Link Sender and Link Receiver processes no longer hang on exit as a result of a semaphore deadlock.
The Link Sender now properly closes all file descriptors (sockets) on link shutdown.

Correction to Message Recovery Services

Recoverable messages are now presented to the target queue using the original priority specified when the message was enqueued.
The journal utilities, dmqjourn, dmqjdump, and dmqjplay, now properly mark a file as open when it is opening allowing these files to be properly recovered after a system crash.

Corrections to MessageQ for UNIX Version 3.2A

This section describes corrections to MessageQ for UNIX, Version 3.2A.

Corrections to Message Recovery Services

Recoverable messages that are dequeued from a multi-reader queue but not confirmed before the dequeuing process exits are now requeued without requiring a stream restart.
The time it takes for the journal process to restart a queue when it becomes attached has been reduced from approximately 40 seconds to less than 1/100th of a second.
Recoverable messages are no longer pushed to an inactive queue. This reduces the number of PAMS__POSSDUPL messages a process may receive.

During normal group shutdown, the journal process sometimes fails to validate a DQF or SAF file and then it disables the SAF or DQF. As a result, users receive a status of PAMS__NO_SAF or PAMS__NO_DQF when enqueuing to a disabled SAF or DQF. This problem also prevents users from dumping and replaying the contents of SAF and DQF files.
In the case of a message queuing group with a valid local SAF file forwarding recoverable messages to an invalidated (disabled) remote DQF file, this problem causes the message recovery system to lose messages. The longer the group is left running in this state, the more messages are lost.
Occasionally, during normal shutdown conditions, the journal process would fail to delete all semaphores if it exited after the group control process. This problem has been corrected.
Previously, if a user ran the Journal Dump utility to display the undelivered contents of the SAF or DQF files, it marked all of the messages as "read." Therefore, when MessageQ attempted to resend the messages from the recovery journals, they were erroneously presented to the target application as possible duplicates. This problem has been corrected.

Corrections to the Group Control Process

The group control process now accepts dollar sign ("$") and hyphen ("-") characters in queue names in the %QCT section and in names in the %GNT section of the initialization file.
The group control process now accepts queue numbers without a qualifying group number in the %GNT section. For instance:
```
%GNT
TheQueue 7 L
%EOS
```
where 7 defines the number for the queue and the group is assumed to be zero, which translates to the number of the currently running group.

Corrections to the Message API

When registering for AVAIL/UNAVAIL services for a queue in a remote group, the AVAIL_REG_REPLY is no longer sent to the distribution queue. It is now sent to the original enqueuing source like all other AVAIL/UNAVAIL registrations.

Corrections to the PAMS API

When receiving a message of class MSG_CLASS_PAMS and a type of MSG_TYPE_TIMER_EXPIRED on RISC systems, the pams_get_msgw call no longer generates a fault when the caller supplies an unaligned buffer.
When a MessageQ application fork()s a child process but does not follow the fork() with an exec() that child process no longer causes the parent process to become detached.
The timer_id argument to the pams_set_timer function now properly recognizes 0 (zero) as invalid.
When a value less than 0 (zero) is supplied to the p_timeout argument of the pams_set_timer function, the function now returns PAMS__BADPARAM as documented in the MessageQ Programmer's Guide. This function previously returned PAMS__INVALIDNUM.
MessageQ now returns the correct error codes when a user sends a message to queue zero using the pams_put_msg function.

Corrections to Link Drivers

A problem has been corrected that sometimes caused the link drivers to be hung in a retry loop while continuously trying to re-establish a two-way connection after one side of the connection failed.
A problem has been corrected that sometimes caused the link driver to send a kill signal to pid 0 resulting in the message queuing group going down.
Previously, on Digital UNIX, the link sender process would enter a long loop when attempting to establish a DECnet connection. The loop could last for several (3-5) minutes during which time the CPU could be completely consumed. This problem is now fixed.
A problem occurred in message queuing groups with cross group verification set to enabled. When these groups received an unsolicited connection from a message queuing group not defined in the cross-group section (%XGROUP) of their group initialization file, it caused a segmentation fault to occur in the link driver. This problem has been corrected.

Corrections to the Monitor Utility

The Group Detail command in the group menu of the character-cell Monitor utility now properly invokes the Group Detail display.

Corrections to MessageQ for UNIX Version 3.2

This section describes corrections to MessageQ for UNIX Version 3.2.

Corrections to Message Recovery Services

This release includes fixes to several run-time and crash-recovery journal corruption problems.
Processes no longer block indefinitely when enqueuing messages with a recoverable WF delivery mode.

Corrections to Scripts

The script processor is now properly invoked when you specify a script file using the DMQ_SCRIPT environment variable.
Script echoing and logging for single byte values larger than 127 now function properly.

Corrections to the Installation Verification Procedure

The IVP program (dmqivpipc) now properly cleans up resources if processing is interrupted before completion.
The IVP program now stops allocating resources once it determines that sufficient resources exist to support the proposed configuration.

Corrections to the Group Control Process

The length of LIST_ALL_xxx response messages is no longer always set to zero.