MQMANAGER Configuration Syntax

Prognosis MQ Manager configuration is completed through the MQMANAGER Configuration document. This document can be accessed through the Prognosis Web Application - Administration Tool. To do this, select the required server name then on the Home page go to the Configuration section and click on the MQMANAGER item. This will open the Configuration update page.

SUBSYS MQMANAGER
QMAN (TEST.QUEUE.MANAGER,PRODUCTION.QUEUE.MANAGER,DEV.QUEUEMAN)
MQINST ($DATA01.MQV810, PROD, PRODUCTION.QUEUE.MANAGER)
MODELQ (SYSTEM.DEFAULT.MODEL.QUEUE)
ADMINQ (SYSTEM.ADMIN.COMMAND.QUEUE)
EVENTQ (SYSTEM.ADMIN.PERFM.EVENT)
EVENTDAT (YES)
QFILTER (SYSTEM.*)
QTYPE (LOCAL)
QSTATS ({Y|N|YES|NO})
CHANFILT (SYSTEM.DEF.*)
CHANTYPE (ALL)
PROCFILT (SYSTEM.*)
MSGQFILT (SYSTEM.*)
MAXQMGR (1)
MAXQUEUE (100)
MAXCHAN (50)
MAXPROC (20)
MSGTIME (5)
CMDTIME (30)
USESTATICQ ({0|1})
DYNQPREFIX (PRGN)
STAQPREFIX (PROGNOSIS)
CLOSEREPQ ({0|1})
Any variable whose keyword is not present in the active MQMANAGER Configuration will take its default value. If all keywords are omitted, then all variables take their default values.

As multiple Queue Managers can be specified by using the QMAN keyword, each MQ Manager keyword can be optionally qualified with the name of the Queue Manager to which it applies by adding two values, the first being the Queue Manager Name and the second being the value itself:

i.e. KEYWORD ( [QueueManagerName,] value )

If not so qualified (i.e. only one parameter is supplied) or the first parameter (QueueManagerName) is * then the keyword applies to all Queue Managers.

The QueueManager name specified for a keyword must be explicitly specified as a Queue Manager to monitor in the QMAN keyword. If the QMAN keyword is omitted then the keywords will apply to all QueueManagers monitored by default.

Syntax Elements

QMAN

Name of the Queue Manager(s) to connect to (case sensitive). A single MQ Queue Manager name or a list of multiple MQ Queue Manager names (comma separated) are required, the default will be to the MQ Default Queue Manager.

MQINST -New-

This is for HPE NonStop only

Prognosis uses the MQINST syntax to determine which instance of MQ each Queue Manager is a member of, and also to assign a label to each instance. Use a new entry for each instance.

MQINST( <Guardian Subvolume of MQ install location>, <Label>, <Comma separated list of Queue Managers that belong to this instance of MQ> )

Example:

MQINST ($DATA01.MQV810, PROD, PRODUCTION.QUEUE.MANAGER)
MQINST ($DATA02.MQV810, DEV, DEV.QUEUEMAN)

If MQINST is used in the configuration of a platform other than HPE NonStop the first argument is ignored.

MODELQ

Name of system default model queue (case sensitive). A valid MQ queue name is required, or the default will be SYSTEM.DEFAULT.MODEL.QUEUE.

ADMINQ

Name of system administration queue (case sensitive). A valid MQ queue name is required, or the default will be SYSTEM.ADMIN.COMMAND.QUEUE.

EVENTQ

Name of system performance event queue (case sensitive). This parameter should not need to be set, as in all supported versions of IBM MQ this queue will always be called SYSTEM.ADMIN.PERFM.EVENT, which is the default value for this parameter.

EVENTDAT

This option allows for the collection of event related data, the options being YES or NO (case sensitive). If EVENTDAT is set to 'YES' Prognosis will provide statistical information on the following;

  • Number of messages placed on a queue.
  • Number of messages taken off a queue.
  • Time since the last message was put on a queue.
  • Highest count of messages placed on a queue.

Enter YES to collect event data, anything else defaults to no collection of event data.

QFILTER

The Queue filter parameter is used to limit the number of queues to be monitored. Enter the queue name to be monitored, this is case sensitive and can be up to 48 characters in length. If required the wildcard character * can be used to monitor multiple queues.

To monitor all queues, remove the QFILTER parameter from the configuration or leave the line commented out. The default is to monitor all queues.

Multiple QFILTER entries may be configured in order to fine tune the filters to monitor smaller numbers of entities, thereby saving on the system resources utilized by the IBM MQ Collector. To specify multiple queue filters, a separate QFILTER statement  needs to be added for each one.

QTYPE

The Queue type parameter determines what information is collected based on the type of queue. The valid queue types are;

(LOCAL)

Queues managed by the local queue manager.

(MODEL)

Template queues for creating dynamic queues.

(REMOTE)

Managed by the remote queue manager.

(ALIAS)

These are queues managed by the remote queue manager but are given another name or alias by the local queue manager.

(CLUSTER)

These are queues logically associated together in a cluster.

(ALL) 

All queues regardless of type, this is the default.

QSTATS

Specifies whether to populate the following queue statistics fields of the MqSeriesQueue record:

  • MessagesEnqueuedTotal,
  • MessagesDequeuedTotal,
  • MessagesEnqueuedPerSecond
  • MessagesDequeuedPerSecond

Providing data for these fields requires issuing a separate request to MQSeries for every configured queue, therefore this can incur an extra overhead when running an MqSeriesQueue Display. The default is NO, which will cause these fields to be filled with asterisks.

The collection of this data requires a valid queue entry in the EVENTQ parameter if the default SYSTEM.ADMIN.PERM.EVENT does not exist.

CHANFILT

The Channel filter parameter is used to limit the number of WebSphere MQ channels to be monitored. Enter the name of the channel to be monitored, this is case sensitive and can be up to 48 characters in length. If required the wildcard character * can be used to monitor multiple channels.

To monitor all channels, remove the CHANFILT parameter from the configuration or leave the line commented out.  The default is to monitor all channels.

Multiple CHANFILT entries may be configured in order to fine tune the filters to monitor small numbers of entities, thereby saving on the system resources utilized by the IBM MQ Collector.

CHANTYPE

Type of Channel filter when collecting channel information (case sensitive). CHANTYPE allows only one value, that is, it will not allow a comma-separated list.

(SDR)

Sender channel, this is the outgoing channel. It initiates transfers, removes messages from a transmission queue and moves them to a receiver or requester channel.

(RCVR)

Receiver channel, this channel responds to the sender channel, taking the message from a communication link and placing it on a local queue.

(SVR)

Server channel, this channel responds to the requester channel removing messages from the transmission queue.

(RQSTR)

Requester channel, this channel is started remotely by a sender channel. The requester channel accepts messages from the sender channel and puts the message on the local queue.

(CLNTCONN)

Client connection channels, the type of MQI channel definition associated with an MQI client.

(SVRCONN)

Server connection channels, the type of MQI channel definition associated with a server that runs a queue manager.

(CLUSRCVR)

Cluster server channel, this channel will respond to a sender channel, taking the message from a communication link and placing it on a local clustered queue.

(CLUSSDR)

Cluster sender channel, the CLUSSDR channel initiates transfers, removes messages from a transmission queue and moves them to a receiver or requester channel.

(ALL)

All channels, this is the default.

PROCFILT

The Process filter parameter is used to limit the number of IBM MQ processes to be monitored. Enter the name of the MQ process to be monitored, this is case sensitive and can be up to 48 characters in length. If required the wild character * can be used to monitor multiple processes.

To monitor all processes, remove the PROCFILT parameter from the configuration or leave the line commented out. The default is to monitor all processes.

Multiple PROCFILT entries may be configured in order to fine tune the filters to monitor small numbers of entities, thereby saving on the system resources utilized by the IBM MQ Collector.

MSGQFILT

Name of the queue to select messages from (case sensitive).  Will take up to 48 characters and * can be used for a wild character.  Filters are set by the QFILTER parameter and the queue type must be local.

Multiple MSGQFILT entries may be configured in order to fine tune the filters to monitor small numbers of entities, thereby saving on the system resources utilized by the IBM MQ Collector.

MAXQMGR

Maximum number of queue manager instances, default = 1.

MAXQUEUE

Maximum number of queue instances to collect data on per interval, default = 100

MAXCHAN

Maximum number of channel instances to collect data on per interval, default = 50

MAXPROC

Maximum number of IBM MQ processes to collect data on per interval, default = 20

MSGTIME

Maximum message wait time in seconds, default = 5. The default value should be accepted unless the MQ Server is extremely heavily loaded and 15603 Prognosis errors are occurring.

CMDTIME

Maximum time to wait on a reply queue message in seconds, default = 30

USESTATICQ

This parameter sets the use of static or dynamic reply queues, enter 0 to set dynamic reply queues or 1 to set static reply queues. If this parameter is omitted, the default will be 0 (dynamic), which is the recommended mode of operation, as it requires no additional setup within IBM MQ.

DYNQPREFIX

When the USESTATICQ option is set to 0, use this parameter to set a queue name prefix of up to four characters (longer names can be added but they will be truncated at 4 characters). The specified prefix will be applied to all dynamic reply queue names and. If no prefix is specified, a default prefix of ‘PRGN’ is used.

STAQPREFIX

When the USESTATICQ option is set to 1; use this parameter to set a queue name prefix of up to 20 characters. The specified prefix will be applied to all static reply queue names. If omitted, the prefix will default to 'PROGNOSIS' (case sensitive). If using this option, the static queue names must also be manually defined within IBM MQ, the following queues are required by Prognosis:

<prefix>.QUEUES.REPLY.QUEUE

<prefix>.QSTATUS.REPLY.QUEUE

<prefix>.STATS.REPLY.QUEUE

<prefix>.CHANNELSTATUS.REPLY.QUEUE

<prefix>.CHANNEL.REPLY.QUEUE

<prefix>.CHANNELSTATUS.REPLY.QUEUE

<prefix>.QMGR.REPLY.QUEUE

<prefix>.PROCESS.REPLY.QUEUE

<prefix>.MSGS.REPLY.QUEUE

<prefix>.QMGR.REPLY.QUEUE

CLOSEREPQ

When the USESTATICQ option is set to 0, the CLOSEREPQ parameter allows for queues larger than the Prognosis collection size to be emptied using GET requests instead of closing and re-opening the dynamic queue.  Enter 1 to turn this option on.

An .ini file configuration existed in earlier versions of Prognosis for the Dynamic and Static Reply Queue settings. This .ini file can still be used, however, if any Dynamic or Static Queue settings are also made in the MQMANAGER Configuration file, then these will take precedence over the .ini file.
Provide feedback on this article