Chapter 4 . Corrections to Documentation

Corrections to the MessageQ Client for Windows User's Guide, Version 4.0A

This section provides additions and corrections to the MessageQ client for Windows User's Guide, part number 850-001012-001.

Addition of Performance Test Utility Documentation

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:

If you have installed MessageQ Server software on a Windows NT system, run the Performance Test utility by typing the following command: 

dmqperftest [optional parameters]

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: 

dmqclperftest [optional parameters]

The following table describes the optional parameters that can be used to control the operation of this utility.
Optional Switch Description

-? or -h

Prints a listing of command line parameters

-q queue

Attaches to the queue number provided. If a zero (0) is used, the utility attaches to a temporary queue. In client mode, the default is zero. In server mode, the default is one (1).

-t queue or group queue

The target queue to receive messages. If the group number is omitted or is zero, the local group is assumed. In client mode, the default group is local and the default queue is one (1). In server mode, the default group and queue is the source address sent by the client.

-n number

In client mode, this parameter specifies the number of messages to send. The default is 10000 messages.

-b number

In client mode, this parameter specifies the number of messages to send before waiting for returned messages. The default is 50 messages.

-l number

The length of the message in bytes. The default is 1000 bytes.

-d delivery

The delivery mode is in string form (may be upper or lower case). The default is wait for memory (NN_MEM).

-u uma

The undeliverable message action (may be upper or lower case). The default is discard (DISC).

-x

Explicitly confirm each message. The queue must have the explicit confirm attribute enabled. Post confirmation journaling is not supported.

-r

In client mode, receives messages sent back by the server. In server mode, returns messages back to the client. If omitted clients only send messages and servers only receive messages.

-v

Prints additional returned status information

-c

Operate as a client. A client sends messages. It may receive returned messages by using the -r switch. the client will exit when it finishes sending/receiving the number of messages provided with the -n switch.

-s

Operate as a server. A server receives messages. The server has three modes of operation. It can absorb the received messages. This is the default mode. It can return the messages to the client by using the -r switch. Or it can forward the messages to another server by using the -r switch and by supplying a target by using the -t switch. If neither the -c or -s switch is supplied then the -s is assumed. The server will continue running and must be terminated with a CTRL-C.

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.

The following table describes the data field on each report.
Field Description

Current

The rate calculated between 5 second intervals

Average

The overall rate for this run

Peak

The highest rate reached for this run

Sent

The number of messages sent thus far

Received

The number of messages received thus far

Time

The time accumulated while sending or receiving messages. This is used to calculate the average. This is not the same as the elapsed real time.

Examples

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.

Use the defaults to send messages from the client to the server:

In client mode
attaches to temporary queue
sends messages to queue 1

In server mode
attaches to queue2
receive and absorb messages

dmqperftest -c

dmqperftest

Send messages from the client to the server:

In client mode
attaches to a temporary queue
sends messages to queue 1

In server mode
attaches to queue1
receive and absorb messages

dmqperftest -c

dmqperftest

Send messages from the client to the server, server returns messages to the client:

In client mode
attaches to a temporary queue
sends messages to queue1
receives returned messages

In server mode
attaches to queue 1
receive and return messages to client

dmqperftest -c -r

dmqperftest -r0

Send recoverable messages from the client to the server:

In client mode
attaches to queue 1
sends messages to queue 2

In server mode
attaches to queue 2
receive and absorb messages

dmqperftest -c -q 1 -t 0.2 -d wf_dqf -u saf

dmqperftest -s -q 2

Send messages from the client to server 1, server forwards the messages to server 2.

In client mode
attaches to temporary queue
sends messages to queue 1

Server 1
attaches to queue 1
receive and forward messages to queue 2

Server 2
attaches to queue 2
receive and absorb messages

dmqperftest -c

dmqperftest -r -t 0.2

dmqperftest -q 2

Part no. 850-001012-001