This section contains corrections to the documentation that accompanies the Version 4.0A release.
This section provides corrections to the BEA MessageQ Installation and Configuration Guide for UNIX, part number 850-001005-002.
The description of the installation of MessageQ software from the BEA CD-ROM distribution media contains the following errors:
Table 1-2 on page 1-5 incorrectly shows all installation directories on the CD-ROM distribution media in lowercase. In fact, the installation files appear in uppercase on some systems and in lower case on others. When you enter the device, directory, and file name for the installation, you must use the proper case for your system.
The installation syntax for Solaris and NCR UNIX is incorrectly described in Step 1. The syntax for installing these platforms is as follows:
NCR UNIX mount -F cdfs device directory
Solaris mount -F hsfs -r device directory
The syntax for step 3 should read as follows:
For example, a full specification could read as follows:
Note that the back slash (\) character at the end of the line is required on some platforms to escape the semicolon (;) character on UNIX systems.
# tar -xvf /device_name/filename.tar
# tar -xvf /mnt/cdrom/HPUX/MQDEV400.TAR\;1
The MAX_CLIENTS field in the %CLS section of the group initialization file is used to limit the number of clients on OpenVMS systems only. This parameter is ignored on UNIX platforms. The maximum number of clients that can be configured and running on UNIX systems is restricted by system resources and is not controlled by the MessageQ MAX_CLIENTS configuration parameter.
The description of the queue number parameter incorrectly states that a queue can appear only once in the %QCT section of the group initialization file. A queue can actually appear in the %QCT section several times, however, the last valid entry supersedes all previous entries.
It is important to note that when using the naming feature, all path specifications must use the front slash (/) character regardless of whether the path specified is on a UNIX, Windows NT, or OpenVMS system. Using a backslash character (\) for the path specification is not valid.
When you stop a link using the Monitor utility, it is important to understand that you can only restart the link from the same group on which it was stopped. For example, if the Monitor utility is connected to group A and you stop the link to group B, you must restart the link from group A. It can not be restarted from group B.
Table 4-3 on page 4-21 of the BEA MessageQ Installation and Configuration Guide for UNIX incorrectly states that there are no runtime restrictions in changing the Security setting for a queue in the Queue Configuration Table (%QCT) section of the group initialization file. To change this queue characteristic at runtime, the queue does not need to be stopped, however, no process can be attached to it.
The Performance Test utility enables users to test the message throughput of their current configuration by sending messages in a selected MessageQ configuration and reporting messaging rates. This utility runs as a MessageQ application and is invoked using a simple command line interface. The utility can send or receive a series of messages up to the maximum message size of 4MB and supports all Delivery Modes and Undeliverable Message Actions.
The Performance Test utility has two modes of operation, client or server. When running as a client, it begins by sending messages. When running as a server, it begins by waiting for messages to arrive.
The MessageQ Performance Test utility requires the following environment:
Known Difference Between MAX_CLIENTS file on UNIX and OpenVMS Platforms (page 3-19)
Correction to Description of Queue Number parameter (page 3-28)
Caution When Using Global Naming (pages 3-34 through 3-37)
Restriction on Stopping Links Using the Monitor Utility (page 4-12)
Correction to Modifiable Queue Characteristics (page 4-21)
Addition of Performance Test Utility Documentation
If you have installed MessageQ Server software on a Windows NT system, run the Performance Test utility by typing the following command:
If you have installed the MessageQ Client software on a Windows 95 or Windows NT system, run the Performance Test utility by typing the following command:
Table 4-1 describes the optional parameters that can be used to control the operation of this utility.dmqperftest [optional parameters]
dmqclperftest [optional parameters]
The Performance Test utility outputs an online report of each performance test. Reports are displayed in tabular form with the output of a new header when the screen is filled with 24 lines. Rates are presented in messages per second, time is in seconds. The display is updated every 5 seconds. Table 4-2 describes the data field on each report.
The following examples illustrate how to use the Performance Test utility in both client and server modes. These examples provide the syntax for using the utility on a MessageQ Server system. To run these examples on a MessageQ Client system, use the executable file name dmqclperftest and the same parameter settings.
Use the defaults to send messages from the client to the server:
| In client mode... | In server mode... |
|---|---|
|
Attach to a temporary queue and send a message to queue 1: |
Attach to queue 1 and receive messages: |
|
|
|
Send messages from the client to the server, server returns messages to the client:
Send recoverable messagse from the client to the server:
| In client mode... | In server mode... |
|---|---|
|
Attach to a temporary queue, sends messages to queue 2: |
Attach to queue 2 and receives messages: |
|
|
|
Send messages from the client to server 1, server forwards the messages to server 2::
This section provides corrections to the BEA MessageQ Programmer's Guide, part number 850-001006-002.
The prototypes for the source and target arguments are incorrected stated as "q_address". The correct prototype for these arguments is "int32*".