IBM Support

QMGTOOLS: Must Gather Data Collector User's Guide

Technote (troubleshooting)


This document contains a guide to common functions for the QMGTOOLS (Must Gather Data Collector Tool).

Resolving the problem

This document contains a guide to common functions for the QMGTOOLS (Must Gather Data Collector Tool).

Note: As more functions are added, additional guides will be added to this document. Note that this is documenting common functions. Advanced functions are not yet documented.

What is it

QMGTOOLS (MustGather toolset) is a set of tools to assist individual teams collect data for issues concerning their product. For example, the PowerHA menu contains a set of programs that will collect specific items (joblogs, SST macro output, VLOGs, and so on) to assist the technical representative in debugging a problem. A user will install this tool (it is a save library, so restore the library) on his/her iSeries and use the menu to collect data for the specific problem:

Where to get it and how to install

1. Download as a save file at
2. From the same URL, refer to the file qmgtools_readme.txt for installation instructions.

How to get to the main menu

2. GO MG, and press Enter.

Collecting For Performance Issues (Super Collection - Collecting Jobwatcher, PEX, and Collection Services Data)

Collecting For Performance Issues (Jobwatcher only)

Collecting For PowerHA issues

Hide details for Expand to viewExpand to view

1. From the main menu, select HA (High Availability) data collection:

Arrow pointing to option 1 of Must Gather Data Collector

2. You have a choice of collecting on the local node only or collecting from all the nodes in the cluster. In this example, a collection will be performed from all nodes:

Arrow pointing to option 1 of QHASTOOLS menu

3. It will ask for the library to store the data. You can leave the Dump Cluster Trace Only option to default. Press Enter.

Screen of DMPCLU command

4. You will be presented with a list of nodes in the cluster. Note: This will use FTP to access the nodes in the network to perform data collection and retrieval. If the iSeries environment does not allow FTP, this option will fail. Enter the credentials and press F1 to continue:

Screen of node, user profile and password

5. A status screen should appear similar to that shown below. It will also list the steps being peformed:

Screen showing status of data collection

6. When it is finished, a screen will be displayed similar to that below. The library that the data is stored in is listed. You have the option to press F3 to exit or F1 to save the data, then exit:

Arrows pointing to messages indicating data is collected and how to proceed

7. In the screen below, the choice was taken to save the data and exit. A status message should be presented when done to tell the user what the save file is and where it is stored. If the iSeries allows FTP to the Internet, you should refer to the section below called FTP Data to IBM:

Arrows pointing to data location

8. This example shows how to collect data on a local node only. Note: If you cannot collect and retrieve data from multiple nodes, this option is needed. QQQMGTOOLS must be installed on all nodes and the procedure below must be performed on all nodes:

Arrow pointing to option 2 of QHASTOOLS menu

9. Select the option as shown below. You can leave as default or change some parameters. Press Enter to start the collection:

Screen of DMPCLUINF command

10. Because the Save Into Save File was left as default 'Y', a screen should appear below once the collection is done. It should state the name of the save file. The library was already specified in Step 9. If the iSeries allows FTP to the Internet, refer to the section called FTP Data to IBM:

Screen showing data collection completed

Cluster Debug Tool

Hide details for Expand to viewExpand to view

The cluster debug tool will scan the library where data from QMGTOOLS PowerHA data collection is stored. All node data collected using QMGTOOLS must be in a single library. If you collected data from individual nodes via Dump Cluster Data On Local Node Only option, place all data into a single library. Note: This library should only contain the collected data (for example, don't put this into QGPL library).

You can try to run this on the system being serviced; however, it is more generally used when the data is sent back to the Support Center for analysis.

1. In the PowerHA menu (Go QMGTOOLS/MG, Option 1), select Option 5:

Arrow pointing to option 5 of QHASTOOLS menu

2. Type the library name where all the data is stored, and press Enter. It will be analyzing at that point:

Screen showing CLUDBGALT command

3. When completed, a QSYSPRT spooled file is created with the results:

Screen showing analysis complete, what the output file is  and to press Enter


Hide details for Expand to viewExpand to view

This option basically performs the same procedures as published in the following IBM Rochester Support Center Knowledegebase documents:

o MustGather: High Availability - CLUSTERINFO Advanced Analysis (AA) Macro:

o Documentation Collection -- DSMINFO Advanced Analysis (AA) Macro:

o Documentation Collection -- GEOSTAT Advanced Analysis (AA) Macro:

o Documentation Collection -- ASMINFO Advanced Analysis (AA) Macro:

1. In the PowerHA menu (Go QMGTOOLS/MG, Option 1), select Option 7:

Arrow pointing to option 7 of QHASTOOLS menu

2. If the function is successful, there will be several spooled files created and are labeled: DSMINFO, CLUSTERINF, GEOSTAT, and ASMINFO:

Screen showing spoolfiles generated

PowerHA PTF Comparison

Hide details for Expand to viewExpand to view

If the iSeries allows FTP to the Internet, QMGTOOLS can compare the current PTFs for PowerHA to the system.

1. From the main menu (Go QMGTOOLS/MG), select Option 1 for PowerHA, and select Option 12:

Arrow pointing to option 12 of QHASTOOLS menu

2. When complete, a spooled file named QSYSPRT will be generated to provide the results:

Screen showing comparison is done and file that contains results

CTA/EWS menu

Hide details for Expand to viewExpand to view

LDAP data collection

LDAP Trace for R610 and R710:

Retrieve SSL Certificate


Misc Tools Menu

Hide details for Expand to viewExpand to view

Miscellaneous tools menu contains miscellaneous tools that do not belong to a certain group.

System Snapshot

Extract VLOG from a file

Extract VLOG from a file is when a user dumps VLOGs from a system using the below command:

QSYS/PRTINTDTA TYPE(*DMP) DMPID(*ALL) PERIOD(('xx:xx:xx' 'xx/xx/xxxx') ('xx:xx:xx' 'xx/xx/xxxx'))

This command will dump the entire VLOGs for the specified period into a single spooled file.

This function will separate the VLOGs into separate members for easier viewing versus viewing the single spooled file:

Arrow pointing to option 2 of Misc Menu

1. The spooled file must be copied into a physical file. Copy a spooled file as follows:
a) Create a physical file with these parameters: CRTPF FILE(my_library/my_file) RCDLEN(200) MAXMBRS(*NOMAX) SIZE(*NOMAX)
b) Copy the spooled file into the file CPYSPLF FILE(spoolfile name) TOFILE(my_lib/my_file) JOB(jobnumber/jobuser/jobname) SPLNBR(spoolfile number) TOMBR(my_member)

where jobnumber/jobuser/jobname is the job that create the spooled file (this can be viewed by displaying the attributes of the spooled file - WRKSPLF, option 8)

where my_member is a member name that you choose.

2. From Step 1, input the file name, library name, and member name. Change output file name and output library name if you want to place the output elsewhere.

Screen of EXTVLOG command

3. When finished, use command WRKMBRPDM FILE(my_lib/my_file) to view the results. Notice that members VLOGxxxxxx are individual VLOGs separated from the file. The text description provides the major/minor code. There is also a VLOGLIST that gives a summary of all the VLOGs detected in the file:

Screen of WRKMBRPDM for file containing results

QVLOGTOOL3 Interface

Run AA macros

Copy outq to PF

Copies the contents of an output queue to a physical file.

FTP Data to IBM

Cross reference information
Segment Product Component Platform Version Edition
Operating System IBM i 6.1
Operating System IBM i 7.1
Operating System IBM i 7.3
Operating System IBM i 7.2

Historical Number


Document information

More support for: IBM i
High Availability

Software version: 7.1, 7.1.0, 7.2, 7.2.0, 7.3

Operating system(s): IBM i

Reference #: N1010441

Modified date: 25 June 2013

Translate this page: