IBM Support

QMGTOOLS - ECA Identification Tool (Hardware Data Collection)

Troubleshooting


Problem

The QMGTOOLS library provides an efficient way to gather data to debug hardware issues.

Diagnosing The Problem

The QMGTOOLS library provides an efficient way to gather data to debug hardware issues. This document describes the ECA identification tool.

Resolving The Problem

This tool compares a list of serial numbers of hardware on the system that matches an ECA (engineering change announcement) file. This would be used under the direction of IBM support. For more information about ECA, refer to this URL :

Note: This process uses a virtual device to sign onto the system as if it was a user. Once signed on, it goes into SST and runs the necessary commands to dump the data. There may be issues if the system is in restricted a state where no new sessions are allowed. Other issues may occur if the system has a unique sign on method such as two factor authentication.

Step 1

Obtain and install a copy of QMGTOOLS library from IBM. Follow the links below for instructions.

http://www-01.ibm.com/support/docview.wss?uid=nas8N1011297

Step 2

Once installed, add QMGTOOLS to your library list via ADDLIBLE command. Run command GO MG to bring up the QMGTOOLS main menu. In the example, option 19 is the Hardware data collection menu. Take that option.

QMGTOOLS main menu

The Hardware data collection menu has these options (as more menu options are added, this document will reflect the changes).

QMGTOOLS' Hardware Menu

Step 3

Select the menu option titled ECA Indentification Tool or prompt on command QMGTOOLS/CHKECA.

ECA command screen shot

How to collect data for ECA
*AUTO - the tool attempts to collect the data automatically for the tool to compare
*MANUAL - collect the data manually for the tool to compare
A rack configuration is collected for the tool to compare against an ECA.
ECA number An ECA number given by support
 

If *AUTO was selected on the "How To Collect Data For ECA", a screen like below should appear. The tool will try to collect the data to compare against an ECA.

VTM screen

Signon user ID/Pass User ID/Pass to sign on for i5/OS
SST user ID/Pass User ID/Pass for SST
Virtual Device
Virtual device to use for signing on to the system
 
Note: This process uses a virtual device to sign onto the system as if it was a user. Once signed on, it goes into SST and runs the necessary commands to dump the data. There may be issues if the system is in restricted a state where no new sessions are allowed. Other issues may occur if the system has a unique sign on method such as two factor authentication.
 After completing this function, a message will indicate if anything was found from the ECA.
Step 4
If the tool was not able to automatically sign into SST to generate the data for the ECA compare, then go back to Step 3 and put in *MANUAL for the parameter "How To Collect Data For ECA".
The manual steps to use the compare tool (this is if the *AUTO function failed) :
A) Generate a rack configuration
1. Go into SST                                                      
2. Select option 1, 7, and F6 to print configuration                
3. At the "Print Format Options", change "Information Printed" to 3
   and press ENTER to create a spoolfile                           
B) Go back to step 3 and put in *MANUAL and continue (example screen shot).
ECA Identifiction tool screen shot

[{"Product":{"code":"SWG60","label":"IBM i"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"General","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"Version Independent","Edition":"Standard","Line of Business":{"code":"LOB57","label":"Power"}}]

Document Information

Modified date:
18 December 2019

UID

ibm10870174