The BEA MessageQ main menu provides access to many BEA MessageQ command procedures and utilities. Before you access the BEA MessageQ main menu, make sure that you run the DMQ$SET_LNM_TABLE command procedure to connect to the group's environment.

After you start a BEA MessageQ group, invoke the BEA MessageQ main menu by entering the following commands:

$ DMQ:==@DMQ$EXE:DMQ$MENU $ DMQ

BEA MessageQ displays the main menu. Table 9-1 describes each BEA MessageQ main menu option and indicates where to find more information about each option.

The DMQ$LLS_VERIFY utility maps a message queuing group's buffer pool configuration and verifies the consistency of data structures for the global section. It validates the configuration specified in the Buffer Pool Configuration Table of the DMQ$INIT.TXT file.

The DMQ$LOOP utility tests message queuing bus communications by performing a loopback of messages, for both local and cross-group communications. This is a quick test to see if, and at what rate, messages of a specified size can be exchanged.

Note: The DMQ$LOOP utility can only be used with other local and cross-group OpenVMS groups. This utility is not supported for testing cross-group communications with groups on UNIX or Windows NT systems.

Note: When running DMQ$LOOP, large messages can fail if the screen queue quota on the OpenVMS system is too small.

When you enter the data, an X-Group loop test statistics screen is displayed.

Select V from the menu to suppress (or activate) data verification. Data
verification is generally ON. When you first select this option, the Data
Verification switch changes from ON to OFF. The next time, it will be toggled to
ON again.

Note: Use the data verification option to control writing and checking of a data pattern within each message. With small messages, this overhead is insignificant, however, if the message size increases, the overhead may become a large percentage of the cost of sending a message.

The DMQ$TEST utility tests BEA MessageQ API routines. It allows you to define, send, and receive messages interactively while being attached to a permanent or temporary queue. It also supports generating messages from a script.

To use this utility, choose Option 6 from the BEA MessageQ main menu. At the prompt, enter configuration information to set up the test.

Select Option 9 from the BEA MessageQ main menu to access the @CUSTOMIZE command procedure. The @CUSTOMIZE option allows you to access and edit the DMQ$BOOT.COM and DMQ$INIT.TXT files to customize your BEA MessageQ configuration. The previous versions of the files should not be purged until the new configuration files have been tested. Note that the default action is to purge the files.

Enter Y to create new include files for DMQ$INIT.TXT. The following messages are displayed:

... Translating DMQ$INIT.TXT to language include files.

Translating for ADATranslating for BASICTranslating for BLISSTranslating for CTranslating for COBOLTranslating for FORTRANTranslating for MACROTranslating for PASCALTranslating for PLIInserting files into library

Inserting files into library... Rebuild PAMScript symbols [Y/N] Enter Y to customize the BEA MessageQ Script Facility to your present configuration. The system displays the following message: *This step takes from 1-30 minutes depending on system load, * *processor type, and number of symbols in the files. *

Submit to batch [S], Run at terminal [T]... [S,T] (T):

Execute the customization procedure SYCUSTOMIZE.COM [Y/N] (N):

Enter Y to complete BEA MessageQ customization. Then press Return to return to the main menu.

SYCUSTOMIZE.COM can be modified to archive these changed modules: DMQ$BOOT.COM DMQ$INIT.TXT DMQ$TYPCLS.TXT

The DMQ$INIT.TXT file contains nine sections that you must customize for each group. Each section begins with a percent sign (%) following the name or an abbreviation for the name of the section. Refer to Defining the Message Queuing Environment, for instructions on how to customize the group initialization file.