MQ Admin

• DefaultBindType=ISOLATED

  impacto en el sincronismo de COMMIT y ROLLBACK con DB2.

Top

Homepage.

MQ Explorer is included with an MQ server installation and is also available for download as SupportPac MS0T.

MQ V 5 fa servir PCF ; MQ 6 uses Eclipse : Java.

Start it from Java : strmqcfg (dedicado a mi buen amigo Francisco)

El requeriment fa servir SYSTEM.ADMIN.COMMAND.QUEUE, on esta escoltant el command server. La resposta fa servir cues dinàmiques.

It will use SYSTEM.ADMIN.SVRCONN for any remote queue managers. It will use a bindings connection for any local queue managers, unless you explicitly add them as remote queue managers.

Enable Eclipse workbench : Window- Preferences - Explorer - Startup in an Eclipse workbench
url ; again.

M'agradaria tenir a la dreta :

• 6 canals (de 3 gestors diferents)
• 8 cues (de 4 gestors diferents)

• start setup.exe from C8471ML.zip (MQ Server), and choose Custom
• only Eclipse is required. 117 MB.
• url

Ensure that you have satisfied the following requirements before trying to use the MQ Explorer.

1. A command server is running on every remotely administered queue manager.
2. A suitable TCP/IP listener object must be running on every remote queue manager. This can be the WebSphere MQ listener or, on UNIX systems, the inetd daemon.
3. A server-connection channel, by default named SYSTEM.ADMIN.SVRCONN, exists on all remote queue managers. You can create the channel using the following MQSC command:
   DEFINE CHANNEL(SYSTEM.ADMIN.SVRCONN) CHLTYPE(SVRCONN) MCAUSER('mqexplor')
4. The system queue, SYSTEM.MQEXPLORER.REPLY.MODEL, "TYPE(QMODEL)" must exist.

url

The syntax of this command follows:

Optional parameters

-c
-clean is passed to Eclipse. This causes Eclipse to delete any cached data used by the Eclipse runtime.

-i
-init is passed to Eclipse. This causes Eclipse to discard configuration information used by the Eclipse runtime.

url

Sequence by JeffLowrey to fix local QM only accessible as remote ("-i", then "-c" - "i" does not start explorer, but cleans cache)

It will use SYSTEM.ADMIN.SVRCONN for any remote queue managers.

It will use a bindings connection for any local queue managers, unless you explicitly add them as remote queue managers.

Remote queue managers are stored in XML file :

A ZIP file can be exported using : select upper level "IBM WS MQ", right click and "Export MQ Explorer values..."

Delete the .metadata directory at

Mind Application Data directory is HIDDEN !

url

Local QM showed Status as "Disconnected", and no queue neither channels were displayed :

Solution : missing a PATH entry to "\Program Files\IBM\WebSphere MQ\java\lib". Ensure "mqjbnd05 loaded:" comes up as YES in WebSphere MQ - Properties \ Configuration information \

The explorer is a fully NLS'd product, so all languages are provided regardless of where you download the trial from. If your local machine is set to have french as its main language then the explorer will run in french.
As for making it run in another language without changing your whole machines locale ... you will need to find the two scripts:

which by default are installed in:

You only need to edit the one that is used (_rcp for rich client mode) but probably safest to edit both of them. In each file, find the line:

and after that insert the line:

Save the files and then launch the explorer using strmqcfg or the program icon as usual.

If for any reason you wish to use a different locale simply replace en_US with the appropriate locale (provided the explorer is translated into that language) and it will launch in that language.

The locales are simply standard java locale notation; a list of valid java locale's can be found here for those wishing to experiment: URL

url

RUNMQSC can NOT do : crtmqm, dltmqm, strmqm, endmqm. Neither dspmqaut, dmpmqaut, setmqaut.

MQexplorer can NOT do : RESET CLUSTER, START CHINIT.

MS0P = MQ Explorer - Configuration and Display Extension Plug-ins

Code here : "T42:\MQ\Explorer_Plugins".

How to install MH01 :

1. Click on 'Help' on the menu bar
2. Select 'Software Updates' and click on 'Find and install...'
3. Select 'Search for new features to install' and click 'Next'
4. Click on 'New Local Site...' and browse to the location of the unzipped SupportPac zip file contents.
5. Tick the box next to the new WMQ Healthcheck entry in the site list, and click 'Next'
6. In the displayed list of available features to install, choose the 'WebSphere MQ Explorer Healthcheck' entry and click 'Next'

Using WebSphere MQ Explorer as a read-only viewer

Security concerns when using MQ Explorer for remote admin

MisterQ, light-weight MQ explorer tool, plugin for the Eclipse platform.

Top

You can invoke the runmqsc command in 3 modes :

• verify mode - available only on a local qm.
• direct mode - commands sent directly to a local qm
• indirect mode - commands are run on a remote queue manager. Indirect mode of operation is performed through the default queue manager

The object source.queue.manager is the source queue manager from which you can issue MQSC commands and to which the results of these commands (operator messages) are returned. The object target.queue.manager is the name of the target queue manager, which processes the commands and generates any operator messages.

If you are using runmqsc with the -w option, source.queue.manager must be the default queue manager.

RUNMQSC is an utility that lets you view the queue manager objects and their attributes. It launches an interactive (command-line interface) administration session.

If input is from Script file, the syntax is : RUNMQSC QmgrName < InputFile > OutputFile

Complete details in MQSC Command Reference, SC34-6055-02

[1] RESET CHANNEL
If the command is issued to a sender or server channel, then in addition to resetting the value at the end at which the command is issued, the value at the other (receiver or requester) end is also reset to the same value the next time this channel is initiated (and resynchronized if necessary). If the command is issued to a receiver, requester, or cluster-receiver channel, the value at the other end is not reset as well; this must be done separately if necessary.

MQ v 6.0 MQSC command reference, SC34-6597-00, csqzaj10.pdf, pagina 397 [417/501]

[2] RESOLVE CHANNEL
This command is used when the other end of a link fails during the confirmation period, and for some reason it is not possible to reestablish the connection. In this situation the sending end remains in doubt, as to whether or not the messages were received. Any outstanding units of work need to be resolved by being backed out or committed. Care must be exercised in the use of this command. If the resolution specified is not the same as the resolution at the receiving end, messages can be lost or duplicated.

Page 409, MQ v 6.0, "MQSC Command Reference", SC34-6597-00

Mind SYSTEM.DEF.SVRCONN has to have mcauser=mqm (temporarily). Otherwise

We recently implemented MQDocument at my shop. Every morning when my MS03 batch job runs to back up every QM in the system, it calls out to MQDocument to compare today's MS03 for each QM to yesterday's MS03s. It then produces a little report that gets emailed to me listing what if anything got added, deleted or changed on each QM. Plus it keeps a rolling 90 days of these reports. Gotta say that was the best money spent. Careful as people are, stuff happens. Scanning that report every morning has allowed me to catch some things that would eventually become big and hairy problems.

Top

MQ instrumentation events come in the following types :

• queue manager events - events related to the definitions of resources within queue managers. Eg.- an application tries to put a message to a queue that does not exist
• channel and bridge events - events reported as a result of conditions detected during their operation. Eg.- a channel instance is stopped.
• performance events - notifications that a threshold condition has been reached by a resource. Eg.- a queue depth limit has been reached.
• logger events - notifications that the queue manager has started writing a new log extent (qm that use linear logging only)

Monitoring, SC34-6593, page 33/411.

• authority events [AUTHOREV]
• inhibit events [INHIBITEV]
• local events [LOCALEV]
• remote events [REMOTEEV]
• start and stop events [STRSTPEV]

• channel events [CHLEV]
• IMS Bridge events [BRIDGEEV]
• SSL events [SSLEV]
• Channel auto-definition events [CHADEV]

 This event queue:            Contains messages from:       As
---------------------------- -------------------------     ----------------
 SYSTEM.ADMIN.QMGR.EVENT      Queue manager events          Not Authorized
 SYSTEM.ADMIN.CHANNEL.EVENT   Channel events                Channel stopped
 SYSTEM.ADMIN.PERFM.EVENT     Performance events            Queue full
 SYSTEM.ADMIN.CONFIG.EVENT    Configuration events          Change object
 SYSTEM.ADMIN.LOGGER.EVENT    Logger events                 New log extent

Monitoring MQ

Configuration events are reported when objects are created, or modified. The event messages for configuration events are put on the SYSTEM.ADMIN.CONFIG.EVENT queue.

Monitoring MQ

Top

Performance Event (Event Tab) Enabled

SYSTEM.ADMIN.PERFM.EVENT

Monitoring, SC34-6593

MQFMT = MQEVENT

MS0P

When enabled, a Queue Full event is generated when an application is unable to put a message onto a queue because the queue is full.

To enable Queue Full events on the queue MYQUEUE, use the following MQSC commands:

Automatically enabling events :

• a "Queue Full" event is automatically enabled by a "Queue Depth High" or a "Queue Depth Low" event on the same queue.
• a "Queue Full" event automatically enables a "Queue Depth Low" event on the same queue.

MQ v 6.0 Monitoring, page 36 [58/411].

Message descriptor (MQMD) in event messages : the message type is MQMT_DATAGRAM, and the message format is MQFMT_EVENT.

Message data in event messages - the event message data is in programmable command format (PCF), as is used in PCF command inquiries and responses. The event message consists of two parts: the event header and the event data.

Event header (MQCFH) - the information in MQCFH specifies:

• The category of event.
  Whether the event is a queue manager, performance, channel, configuration, command, or logger event.
• A reason code specifying the cause of the event.
  For events caused by MQI calls, this reason code is the same as the reason code for the MQI call.

MQCFH.Type := "Event" ;
MQCFH.Command := MQCMD_Q_MGR_EVENT | MQCMD_PERFM_EVENT | MQCMD_CHANNEL_EVENT | MQCMD_CONFIG_EVENT | MQCMD_COMMAND_EVENT | MQCMD_LOGGER_EVENT
MQCFH.Reason := MQRC_* ;

MQ v 6.0 Monitoring, chapter7 [71/411].

Top

If you used the lauchpad to install MQ, check this file in your user Temp folder : MQv6_Install_YYYY-MM-DDTHH-MM-SS.log

• stop the queue manager - kill "amqxssvn.exe" or "amqzxma0.exe".
• stop the listener - kill "runmqlsr.exe" or "endmqlsr".
• stop the command server - kill "amqpcsea.exe" or "endmqcsv".
• stop the channel initiator - kill "runmqchi.exe".
• stop the trigger monitor - kill "runmqtrm.exe".
• stop the sender channel (as there is no trigger monitor, messages shall stack on xmit q)
• stop the receiver channel - kill "amqrmppa.exe".
• set data queue to put(disabled)
• set DLQ to put(disabled)
• fill the data queue (decrease max depth)
• fill DLQ
• fill DLQ and send a Persistent message using a channel (it gets stopped)
• fill FileSystem, so AMQERR01.LOG can not grow !
• change AMQERR01.LOG owner to "sag" : 1x FDC per minut !

Environment :

Config & run :

Top

Overview

MQ v 6 Monitoring

Cacti.

MS0P = MQ Explorer - Configuration and Display Extension Plug-ins