MQ Admin

Top

Use PCFs instead of MQAI bags

\\MQ\Eines\PCF_Inquiry_channel\ (pcf), \\MQ\Eines\AMQSAILCH_display_channel_status\ (bags) PCF header (MQCFH) structure - CMQCFC.H file see "./mq_api.htm#mqapi_def"

texte from mqseries.net "MQAI will be dropped"

Top

You can find some samples (01*.cmd) at

• \\MQ\cluster\samples\
• \\MQ\eines\clustering_demo\
• \\MQ\eines\qm_resolution_sample\
• \\MQ\CMDS\<misc>

Veiem els detalls, per ordre lògic d'execució:

• 95_esborrar_gestor.cmd
• 91_crear_gestor.cmd
• 02_crear_objectes_gestor.cmd
• 11_engegar_listener.cmd

Aqui hi ha els equivalents de Linux ...

Top

• DefaultBindType=ISOLATED

  impacto en el sincronismo de COMMIT y ROLLBACK con DB2.

Top

Using AD See SysAdminGuide !

How to enable the OAM to talk to AD, so that it can verify that AD has authenticated a given user and find out what ids it belongs to : start here

You can certainly configure AD to act as a user repository so that the OAM knows that user A can PUT or GET from a given queue. - mqjeff

Top

Homepage.

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

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 / ReplyToQ.

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.

Do you know how to hide / display dynamic queues ?

Enable Eclipse workbench : Window- Preferences - Explorer - Startup in an Eclipse workbench
Writing Java tests for your WebSphere MQ environment to use in MQ Explorer : 0512_lane ; again.

Switch workspace options in MQ Explorer has been dropped from 7.1 and above

Still launch MQ explorer with a certain workspace by using the "-data" option, although doesn't seem to allow the creation of new workspaces.

If you want to do that, install a standalone copy of Eclipse 3.6 and install the MQExplorer plugins into that.

M'agradaria tenir a la dreta :

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

Les seves icones s'han de poder moure per el canvas, i haurien de mostrar el seu estat (canal/listener) o fondaria (cues).

See GMT, graphic monit tool (own)

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

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 !

Another procedure is here:

1. Open the WMQ Explorer instance exhibiting the issue (queue manager names are not listed under the Queue Managers folder)
2. Right click on the top-level "IBM WebSphere MQ" tree not in the navigator panel, and select "Export MQ Explorer Settings..."
3. Ensure all checkboxes are selected, and select a target filename to perform the export to.
4. Re-exporting the configuration in this way will ensure that only valid metadata is written out to the resulting XML file.
5. Exit WebSphere MQ Explorer
6. Delete or rename the "workspace" folder that was supplied. This will cause the workspace to be recreated when WMQ Explorer is next started.
7. Import the configuration file generated in step 3.

The full list of queue managers should now be visible under the MQ Explorer - Navigator tab for queue managers.

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 these 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.

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

Edit MQExplorer.ini in <MQ75_Install>/bin and include:

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 - homepage by Mark E Taylor
This SupportPac provides a mechanism to format Event messages and to aggregate the Statistics and Accounting reports generated by MQ.

Download the zip file and unzip it to a new directory. Edit the MS0P.link file to point to this directory, and move it into the "links" directory under your Eclipse installation. {\\MQ\MQExplorer\eclipse\plugins}

Or

1. Download or copy the zip file into the eclipse directory under which the other WMQ plugins are located. If you have installed WebSphere MQ in the default location, this will be "C:\Program Files\IBM\WebSphere MQ\eclipse"
2. Unzip the file "in place". This will create the plugins\<events.stats> subdirectory.
3. Restart MQ Explorer with "strmqcfg -c".

MQ v7.5 :

1. download tool into \\$_MQ_SupportPacks\MS0P-events_and_statistics_plugins\ms0p
2. go to c:\MQ\MQExplorer\eclipse\dropins and create "MS0P" directory
3. unzip tool into "c:\MQ\MQExplorer\eclipse\dropins\MS0P"
4. restart Eclipse and you shall see a new folder labeled "Administered Servers"
5. see video
6. right-click on SYSTEM.ADMIN.TRACE.ACTIVITY.QUEUE object, and select "Format Activity Records"

Extends the ability of the WebSphere MQ Explorer to examine the MQ configuration and look for potential problems and make recommendations.

Code here : "\\T430\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'

• general tests
  • qmgr names are different enough
  • DLQ : must exist, must be empty, max msg length, persistent
  • FFST : must not exist
  • all qmgrs must be running
  • default Tx queue : must exist
• cluster tests
  • cluster can resolve qmgr names
  • cluster-sender in "retrying" state
  • cluster-sender or cluster-receiver has "cluster" attribute
  • duplicated queue manager
  • two full repositories
  • different instances of a cluster queue must have same attributes
• queue tests
  • queue names are different enough
  • any queue has reached Max_Depth
  • "base" attribute in "alias" queue does exist
  • all queueus are get-enabled
  • all queueus are put-enabled
  • remote queue : verify rmt_qmgr, rmt_queue, xmit_queue
• channel tests
  • channel names are different enough
  • any channel is "in doubt"
  • match channel pairs
  • ping non-running channel IP's
  • resolve and ping hosts in "Connection Name"
  • disconnect interval must be > heartbeat interval
  • "MCA User ID" must exist in SVRCONN channels
  • Xmit queues : must be used and must be used only once
• listener tests
  • listener names are different enough
  • a port number must be used only once by multiple qmgrs
• triggering tests
  • initiation queue must exist and be local, a process must have it open for input
  • process names are different enough
  • process must have an absolute path
  • process must exist
  • verify "Trigger data" ; channel must be found ;
• SSL tests
  • highlight any channels which have a last-started time earlier than the last modification time of the SSL key repository, and which could therefore need refreshing
  • highlight any channels that have not got the CipherSpec attribute set
  • highlight any channels that have not got the Authetnication of Parties Initiating Connections (SSLCAUTH) attribute set to Required.
  • checks the SSL Key Repository attribute of queue managers to see if a file can be found at that location.
  • verify the SSL peer attributes used in channel definitions

Supplied tests

{mqjeff} Writing Eclipse Plugins is an advanced topic not for the average MQ administrator. The current trend with MQ Explorer is to make it more friendly to the average MQ administrator, and less friendly to the average Eclipse programmer. For example, it's not possible to run MQ Explorer 7.1 in an Eclipse workbench without installing an Eclipse workbench. There are a lot of complicated factors that contribute to this - including such basic things as the size of the default install! It's assumed you a) know what you want to test, b) know how to write a program to test it.
First rule of dealing with MQExplorer plugins is that everything you want to do with a queue manager has to be done using Java code that sends PCF messages. So if you can't write Java code that sends the PCF messages you want to send, and processes the responses you get back, then you can't write an MQExplorer plugin - and consequently can't write an MQexplorer Test - since Tests are MQ Explorer plugins.
For the less experienced PCF programmer, I highly recommend PCF Escape messages.

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

The purpose of WebSphere MQ programmable command format (PCF) commands is to allow administration tasks to be programmed into an administration program. In this way, from a program you can manipulate queue manager objects (queues, process definitions, namelists, channels, client connection channels, listeners, services, and authentication information objects), and even manipulate the queue managers themselves.

PCF commands cover the same range of functions provided by MQSC commands.

Each PCF command is a data structure that is embedded in the application data part of a WebSphere MQ message.

Briefly, these are some of the things needed to create a PCF command message:

• Message descriptor
  This is a standard WebSphere MQ message descriptor, in which:
  • Message type (MsqType) is MQMT_REQUEST.
  • Message format (Format) is MQFMT_ADMIN.
• Application data
  Contains the PCF message including the PCF header, in which:
  • The PCF message type (Type) specifies MQCFT_COMMAND.
  • The command identifier specifies the command, for example, Change Queue (MQCMD_CHANGE_Q).

For a complete description of the PCF data structures and how to implement them, see "WebSphere MQ Programmable Command Formats and Administration Interface", amqzac06.pdf or csqzac07.pdf

MQ v7 System Admin Guide, amqzag10.pdf, pg 54 o pg 67/605

MQCFH, the PCF header is described on page 474, amqzac06.pdf

Try to inquire a queue depth :

• \\MQ\Eines\PCF_Inquiry_qmgr_Queues\

  pPCFHeader->Type = MQCFT_COMMAND ; pPCFHeader->Command = MQCMD_INQUIRE_Q ;

• \\CPP\MQI\Monit_Queue_Depth\

  Perd memoria : timersag.pas @gedas uses MQAI and bags. amqsailq.c uses MQExecute(MQCMD_INQUIRE_Q).

Command server is listening at this queue :

Lets see the handle :

We can stop the command server to see the message format using ENDMQCSV command

What is the format of the message to put ?
See MQ_v7_PCF_and_AI_csqzac06.pdf, PCF and AI

C sample to inquiry command server
\\MQ\Eines\PCF_Inquiry_qmgr_Queues

Ask for any value, as MQIACH_BYTES_SENT and/or MQIACH_BYTES_RCVD
\\MQ\Eines\PCF_Inquiry_channel

Commands and responses have the form:

• PCF header (MQCFH) structure followed by
• zero or more parameter structures

  Each of these is one of the following:

  • PCF byte string filter parameter (MQCFBF : 20 fixed + Type + length
  • PCF byte string parameter (MQCFBS : 16 fixed + Type + length
  • PCF integer filter parameter (MQCFIF : 20 fixed + Type + length
  • PCF integer list parameter (MQCFIL : 16 fixed + Type + length
  • PCF integer parameter (MQCFIN : 16 fixed + Type + length
  • PCF string filter parameter (MQCFSF : 24 fixed + Type + length
  • PCF string list parameter (MQCFSL : 24 fixed + Type + length
  • PCF string parameter (MQCFST : 20 fixed + Type + length

You can look for "Command" in CMQCFC.H file

The types are

And some values are

Accessing the MQCFH header and the MQCFH parser

See response decoding

Top

Use "SYSTEM.ADMIN.COMMAND.QUEUE" to send commands to Command Server.

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, and an output is written to a status file, the syntax is :
RUNMQSC QmgrName { < InputFile } { > OutputFile }

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

Each command is sent as an Escape PCF to the command queue (SYSTEM.ADMIN.COMMAND.QUEUE) of the target queue manager.

The replies are received on queue SYSTEM.MQSC.REPLY.QUEUE and the outcome is added to the report. This can be defined as either a local queue or a model queue.

[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

runmqsc is the command-line tool typically used to adminster local queue managers. You can also use runmqsc -w to administer remote queue managers.
You need a (default) queue manager on your local workstation so that runmqsc can use it to collect MQSC commands and send them on to the command queues of your remote queue managers.
This lets you do all of your runmqsc administration work from a single point.
Note that your local queue manager will need channels going to and from the remote queue managers that you want to administer, to allow the commands to be sent and the replies returned.

boulder

Now runmqsc has -m flag to indicate the local queue manager used to send commands to another queue manager

MO72 allows the use of MQSC commands either directly connected to a queue manager, or via a client connection to the queue manager.

The product-provided replacement for MO72 in MQ V8 is to use runmqsc with the "-n" option. See KC

Install a version control system. At midnight, run a script to do the following:

1. run dmpmqcfg outputting the objects in 1 line
2. run a REXX script to exclude 'SYSTEM.' objects
3. check the resulting file into the version control system

I had a REXX script that separated the objects by type. i.e. QMGR, QLOCAL, QMODEL, etc. I used the file name format of {QMgr}.{ObjectType}.mqsc and these files are what was checked into the version control system.

I'm a developer, so I always looked at the MQSC files as code and runmqsc as the run-time compiler. So, checking the MQSC files into a version control system just made logically sense.

Homepage, MS-03.

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.

We'll have to run MS03 and dmpmqcfg in parallel for now. The dmpmqcfg command will capture the MQ 7.1/7.5 specific things like CHLAUTH records that MS03 does not. MS03 will insure we get all authority records.

Real-time monitoring can be enabled or disabled for individual queues or channels, or for multiple queue or channels. To control individual queues or channels, the queue attribute MONQ, or the channel attribute MONCHL, must be set to enable or disable real-time monitoring. To control many queues or channels together, real-time monitoring can be enabled or disabled at the queue manager level using the queue manager attributes MONQ and MONCHL. For all queue and channel objects whose monitoring attribute is specified with the default value, QMGR, real-time monitoring is controlled at the queue manager level.

Automatically defined cluster-sender channels are not WebSphere MQ objects, so do not have attributes in the same way as channel objects. To control automatically defined cluster-sender channels, use the queue manager attribute, MONACLS. This attribute determines whether automatically defined cluster-sender channels within a queue manager are enabled or disabled for channel monitoring.

To enable both queue and channel monitoring for all queues and channels at the queue manager level, use the following commands:

To control the monitoring capabilities of automatically defined cluster-sender channels use the following command:

To display the monitoring fields collected for this queue, use the following command:

To display the monitoring fields collected for this sender channel, use the following command:

To discover which cluster channel is having problems delivering messages, issue :

MQ v 6 Monitoring, chapter 18. URL

Top

When an event occurs, the queue manager puts an event message on the appropriate event queue, if defined.
The event message contains information about the event.

Event Monitoring, SC34-6069-02.

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

Using MQAI (from AMQSAILQ.C):

Using PCF (from PCFMessageListQueueDepth.java, MS0B) :

From StackOverflow :

From MQseries.net, by Nacho (gracias, campeon) { from \\MQ\tools\pcf\samples\PCF_WalkThroughQueueManagerAttributes.java } :

url

See latest code here.

Let's write a (Delphi) program to display a queue depth every specific period.
Qmgr : \\MQ\CMDs\SMQ
Delphi code : \\Delphi\MQ\Monitor_Cua

Top

Performance Event (Event Tab) Enabled

SYSTEM.ADMIN.PERFM.EVENT

Monitoring, SC34-6593

MQFMT = MQEVENT

MS0P {Mark Taylor, 2012, mq v 7.0.1}

Delphi - monitor q depth uses MQINQ() with "Select [0] := MQIA_CURRENT_Q_DEPTH ;"

Atencio : QDEPTHHI(integer) The threshold against which the queue depth is compared to generate a Queue Depth High event. This parameter is supported only on local and model queues. For more information about the effect that shared queues on z/OS have on this event, see the Monitoring WebSphere MQ book. This event indicates that an application has put a message on a queue, and this has caused the number of messages on the queue to become greater than or equal to the queue depth high threshold. See the QDPHIEV parameter.
The value is expressed as a percentage of the maximum queue depth (MAXDEPTH parameter), and must be greater than or equal to zero, and less than or equal to 100.

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].

Sample code is here : \\T430\MQ\Events\queue_full

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 res"ponses. 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, chapter 7 [71/411].

Top

To get channel events, use SYSTEM.ADMIN.CHANNEL.EVENT

To inquire channel status, use MQCMD_INQUIRE_CHANNEL_STATUS command - see amqsailq.c :

From amqsaicl.c :

Returned if requested: ... BuffersReceived, BuffersSent, BytesReceived, BytesSent, ...

Maybe this sample helps - \\MQ\tools\pcf\samples\PCF_ChannelStatus.java

My code : \\MQ\Eines\PCF_Inquiry_channel\ (pcf), \\MQ\Eines\AMQSAILCH_display_channel_status\ (bags)

Also, the bytes using a channel is an interesting value to monitor, isn't it ?

Top

Statistics messages are delivered to the system queue SYSTEM.ADMIN.STATISTICS.QUEUE at configured intervals, defined by STATINT qmgr attribute

Queue statistics information is controlled by the queue attribute STATQ and the queue attribute manager STATQ.

Channel statistics info is controlled by the channel attribute STATCHL

There is a sample program in source format named amqsmon that shows how to fetch and format the statistics messages {mq v6.0 monitoring, page 264, 286/411}

Read also here

• ACCTQ
• MONQ
• STATQ
• amqsmon

MQ v6 Monitoring, SC34-6593-00

Perque això funcioni ha d'estar activada una propietat de la cua "supervisión de la cola" (MONQ) a la part de estadístiques. Amb el valor "bajo" es suficient perque es poguin obtenir aquestes dades. Segons l'ajuda del Eclipse els atributs on es poden mirar aquest temps son:

• Data i hora de l'últim missatge rebut: LPUTDATE y LPUTTIME
• Data i hora de l'últim missatge lliurat: LGETDATE y LGETTIME

Top

Start the statistics monitoring for queues, channels or both. It creates you a report about all the messages /bytes/puts/gets... that flows through a queue during the time period you plan in the statistics interval.

Reports are placed in the SYSTEM.ADMIN.STATISTICS.QUEUE. You can extract the info with the amqsmon program: "amqsmon -m qmgr -t statistics > output.txt"

The collection of MQI statistics information is controlled by the queue manager attribute STATMQI. Statistics messages are generated only for queues which are opened after statistics collection has been enabled. For example, to enable MQI statistics use the following MQSC command:

Queue statistics information collection can be enabled or disabled for individual queues, or for multiple queues. To control individual queues, set the queue attribute STATQ. Queue statistics information collection can be enabled or disabled at the queue manager level using the queue manager attribute STATQ.

To enable statistics information collection for the queue, Q1, use the following MQSC command:

To enable statistics information collection for all queues that specify the queue attribute STATQ as QMGR, use the following MQSC command:

Channel statistics information collection can be enabled or disabled for individual channels, or for multiple channels, using the attribute STATCHL.

For example, to enable statistics information collection, with a medium level of detail, for the sender channel QM1.TO.QM2, use the following MQSC command:

To enable statistics information collection, at a medium level of detail, for all channels that specify the channel attribute STATCHL as QMGR, use the following MQSC command:

To enable statistics information collection, at a medium level of detail, for all automatically defined cluster-sender channels, use the following MQSC command:

Use amqsmon to display the information contained within accounting and statistics messages in a formatted form.
Accounting messages are read from the accounting queue, SYSTEM.ADMIN.ACCOUNTING.QUEUE.
Statistics messages are read from the statistics queue, SYSTEM.ADMIN.STATISTICS.QUEUE.

v7 MQ Monitoring, chapter 4, statistics info collection

Top

MP7I, des'2008 : W2003 & MQ v7 - xSeries 365, 4 CPU 3.0 GHz Intel Xeon, 4 GB of RAM

(1) Responder program uses "shared" application bindings. Requester program normally uses "trusted" bindings, except in the "non-trusted" scenario where it uses "shared" bindings.

Top

Message monitoring is the process of identifying the route a message has taken through a queue manager network. As a message passes through a queue manager network, various processes perform activities on behalf of the message. By identifying the types of activities, and the sequence of activities performed on behalf of a message, the message route can be determined.

The following techniques are available for determining a message route:

• The MQ display route application (dspmqrte), see MQ display route application
• Trace-route messaging, see Trace-route messaging
• Activity recording, see Activity recording

These techniques all generate special messages that contain information about the activities performed on the message as it passed through a queue manager network. The information returned in these special messages can be used to do the following:

• Record message activity.
• Determine the last known location of a message.
• Detect routing problems in your queue manager network.
• Assist in determining the causes of routing problems in your queue manager network.
• Confirm that your queue manager network is running correctly.
• Familiarize yourself with the running of your queue manager network.

url

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

Top

Permite comprobar el ritmo al que se lee y se escribe en las colas, entre otras cosas.

MO71 has a web interface. New homepage MQGEM {need license key}

7.5.1 (free)

Old support pack (gone), v 6.0.1, Paul Clarke

See Chapter 13 : You can start the API Exerciser from the main MO71 window, via the Action menu, or by pressing F9.

If your phone has a browser, it is now possible to use the HTTP support in supportpac MO71 to view your MQ queues, messages and more.

1. install MO71 v 7.5.1
2. start mqmonntp.exe
3. File -> Add location & enter local qmgr name in both "location" and "qmgr" fields, then click "Add".
4. right-click on qmgr name and select "queue list", then "refresh" to verify the access
5. enable HTTP listener :
   1. File->Preferences & select the HTTP tab
   2. ensure that the "Root Path" field is set to the directory which contains the MO71 HTML files.
   3. set the TCP/IP port field to a suitable value as 80
   4. click the "Start" button to start the HTTP listener.
      See message "Listener started", and mqmonntp_751.exe listening on port 80 {using TCPview}.
      Is message is TCP/IP function bind failed RC(10013) means ... "permission denied" => Apache was running !
6. enable our queue manager for HTTP admin :
   1. right click on the queue manager you wish to enable for HTTP admin and choose "Open Location"
   2. from the Location Settings window select the "Options" tab.
   3. ensure that the "HTTP allowed" and "HTTP Default" checkboxes are checked. Scroll to botton to find and use "OK" button.
7. to test the connection, enter the following URL in a browser of your choice on the mobile:
   http://<hostname>/mq/admin/Queues/<qmgr name>

Fun with MQ and gadgets - browsing queues from my phone

URL = "localhost" displays "MO71 Web Administration main page" message

Solutions :

• MS0B
• MO71, mqmonntp, with an interesting API Exercizer
• MQ bridge for HTTP
• Visual Browse, USD 29.

Use the WEB interface and put command messages to the command queue. You need then something like MS0B support pack to interpret the result (or build the request).

Infocenter

Top

Improve \\Delphi\MQ\Monitor_Cua to have a nice graphic output

If I use "mqmonntp" and, on a given qmgr (right click), select "queue statistics", a window comes up with

• max depth
• msgs in
• msgs out

What command is being used to get those data ? "Queue Statistics" are used.

To start with, lets enable statistics on a given queue :

Statistics messages are generated at configured intervals (if there are changes in the counters). The configured interval is controlled by the STATINT queue manager attribute. STATINT specifies the interval, in seconds, between the generation of statistics messages. The default statistics interval is 1800 seconds (30 minutes). Sample (15 minutes = 900 seg) : "ALTER QMGR STATINT(900)"
To write the currently collected statistics data to the statistics queue before the statistics collection interval is due to expire, you can use issue the MQSC command RESET QMGR TYPE(STATISTICS). This causes the collected statistics data to be written to the statistics queue and a new statistics data collection interval to begin.

Statistics messages are read from/written into the statistics queue, SYSTEM.ADMIN.STATISTICS.QUEUE

Statistics messages contents is very large, and the details can be found here : "mq v6.0 Monitorig", page 297, 319/411.

Top

Code into \\Delphi\MQ\Monitor_Channel

runmqsc command is

How are those value reset ? Never.

Top

I want to have a dashboard that turns into a testing tool

Lluis diu que ho faria amb node webkit

simple Request/Response - Jonda, Reno

client to Host - Teat, Jedas

HA cluster - Indy, GNF

Top

If we launch the command "strmqm <qm-name>" and get this error

url

We have to verify that the service shall start with the user ".\MUSR_MQADMIN"

Then we display all MQ services :

Then we display its status

We display all details :

So we can start the service :

Then we can

Top

Aixo és un altre mon ... que parla EBCDIC !

Since MQ v7.1, an "application activity" trace can be started, that writes into SYSTEM.ADMIN.TRACE.ACTIVITY.QUEUE, that later we format using a Support Pack MS0P.

Activity records are written to the new system queue SYSTEM.ADMIN.TRACE.ACTIVITY.QUEUE. They collect information about the MQI operations that an application performs while connected to a queue manager.

To control whether or not application activity trace information is collected, you configure one or more of the following settings:

• The ACTVTRC queue manager attribute - "ALTER QMGR ACTVTRC(ON)" or "Qmgr properties + Online Monitoring + Activity Trace"
• The ACTVCONO settings (in the MQCNO structure passed in MQCONNX)
• The matching stanza for the application in the activity trace configuration file mqat.ini

• stop the queue manager - kill "amqxssvn.exe" or "amqzxma0.exe".
• stop/kill the listener - kill "runmqlsr.exe" or "endmqlsr" : amqsputc still gets rc=0 !?
• 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) - no, obtenim MQRC 2051, MQRC_PUT_INHIBITED
• 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 "sebas" : 1x FDC per minut !
• set general/specific AMQERR01.LOG owner to "root" (chown)
• rename MQS.INI
• rename \qmgr_name\QM.INI
• set S0000000.LOG (active log) to "read-only"
• RFE (request for enhancement) num. 22533 - to disable the "REFRESH CLUSTER" with "REPOS(YES)" on full repositories.
  This option must not be used on full repositories but is still valid and causes a cluster to become corrupted.
• delete "jdbcora10.dll" from "\\MQ\exits\" but code "XAResourceManager:" (SwitchFile=jdbcora) in qm.ini
• (aix) set "hostname" with white spaces in it + create queue manager

Environment :

Config & run :

Top

It is possible to upgrade your trial setup to the full product, without needing to reinstall WMQ or recreate their queue managers. When you normally install the full product, the installer registers your new "production" license as a part of the installation process. But it is possible to manually register the license that you get when pay for the full product.

License files are named amqXcert.lic, (c:\mq\bin) where X identifies the license type:

• amqtcert.lic - trial license
• amqbcert.lic - beta license
• amqpcert.lic - full production license

The command to do this is setmqprd (enroll production license) and is documented in the System Administration Guide. setmqprd installs the license, as well as carrying out a number of checks to confirm that it has been correctly applied.

url

Top

• MQ Admins
• MQ Developers/programmers
• MQ Testers
• MQ Support

Each group above have different needs, hence, require different information from their MQ tools.

• MQ Admins deal with MQ objects and their attributes & monitoring of their MQ environment
• MQ Developers are concerned with message data/payload (sometimes about queue attributes)
• MQ Testers are concerned about plug-and-play message "sets" or message cycles
• MQ Support people need MQ tools to resolve 2AM problems which could be queue attribute issue or message data issue

You need to clearly define who your MQ tool is for, then build the best MQ tool for that particular customer base.

Top

• Business Integration Server Express overview

• MQ v 6 Monitoring

• T. Rob's Good practices of Websphere MQ production deployment

• how migration, failover, and the scaling of queue managers are affected in a SOA context

• Cacti

• use Power Shell

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

  Windows : MO70 = display channel statistics o MS0P = MQ Events and Statistics Plug-in.
  A tool written by Mark Taylor at the Hursley Lab, that integrates with the MQ Explorer. It provides several useful features to generate reports from MQ Statistics as well as monitoring Queues and Channels. It also includes a neat Queue Tuning Tool to adjust the Queue Buffers to improve performance. {Honda Bhyat}

  Start PerfMon and add MQ Queue object and its counters.

• commercial tools

  MQ Monitoring and Tools (see MQSERIES.NET fora) : Nastel, BMC's BMM-PA (formerly known as QPasa), QFlex : url, Wili, Avada Infrared360, (Candle) Tivoli, Patrol, OmegaMon, Autopilot, ISAlite, amqsailq, amqsmon -> CSV -> Excel, MH-04, MQMON tool, MQ PCF commands, etc.

  Que son : QNAMI, Transaction Vision, Cressida ?
  QNAMI = monitoring and management solution. Real-time, end-to-end visibility of the state of business services within the business process.
  Bristol Technology Transaction Vision
  qView

  IBM : Agente Tívoli OmegaMon XE for Business Integration

  Ged.s uses Tivoli OmegaMon.

  Allia.z uses Cacti.

  C.rreus uses "BMC Patrol"

  En Xtreme Leverage se tiene que bajar el Tivoli Monitoring v6.1 y después el Omegamon XE for Messaging (ver MQ versus MB)

  Capitalware list of tools : free, commercial.

  Veure que es "Autopilot TM", monitor de transaccions sobre MQ - http://www.tsg.co.uk/ : with Autopilot TM, you can track each transaction in your MQ network

  Long awaited free enterprise strength MQ monitoring solution is finally here. Netflexity, an IT products and services company from Philadelphia, PA, announced that it will release its version of Qflex at no cost. Qflex sports an impressive array of features. It is 100% J2EE compliant web application with comprehensive MQ monitoring and performance tracking capabilities. Web based message browser is a bonus feature. Downloads and more product details are available at www.netflexity.com/QFlex.shtml 2011/12 : http://www.netflexity.com/qflex/index.shtml.

  Qflex 2.0.0.0 (19 MB)
  Any questions regarding the product can be posted under Monitoring Tools forum.

  ---

  Eina comercial : Patrol for MQ :

  PATROL for MQ provides true end-to-end availability and is unmatched in its depth of capabilities, which include configuration, performance monitoring, operations management, content management, optimization, recovery and automation. PATROL for MQ is easy to use and offers packaged "out-of-the-box" solutions that can be custom-tailored. It is the most flexible management solution available, easily integrating into a customer's existing IT environment and providing fast implementation and ROI.

• MQjExplorer {java}, {sag}
• MO71 = mqmonntp.exe - provides a simple, easy to configure GUI interface to administer WebSphere MQ (MQSeries) Queue Managers, by paulg_clarke@uk.ibm.com
• MQ VE - Visual Edit v1.6.1 application allows users to view, manipulate and manage messages in a queue of a WebSphere MQ (formally MQSeries) queue manager and presents the data in a simplified format similar to a database utility or spreadsheet program.
• a web-based monitoring tool for WebSphere MQ. Download 0.2.1, {\\mq_tools\mega.com 2014-10-22}

  Install on Apache Tomcat:

  • Deploy WMQ Monitoring
    Copy wmq-monitoring.war to apache-tomcat-xxx/webapps directory.
  • Start and stop server
    • cd apache-tomcat-xxx/webapps/bin
    • shutdown (stop the server)
    • startup (start the server)
    • once the server is started, try to access http://localhost:8080/wmq-monitoring with latest Google chrome browser (user/password: mqadmin/mqadmin).
• MQGEM has
  • MO71 = GUI admin and cfg tool
  • MQSCX = RUNMQSC/MO72 on steroids