IBM Support

MustGather - Web Query

How To


Summary

This TechNote provides a list of data to gather when you need to open a Case to IBM for WebQuery.
Examples:
WebQuery report encounters an error.
WebQuery report runs but never finishes.
Scheduled WebQuery report doesn't generate requested output.

Objective

WebQuery issues usually require a re-create and tracing. 
This TechNote provides those steps.

Steps

Use steps 1 - 4 for most situations. 
Steps 5 and 6 are usually not required initially.
Step 7 (Complete re-create environment) will be needed in some situations.
1) WebQuery Collector   - provides basic information about the WebQuery installation, logs, etc.
2) Change Management (ChgMgmt) Package    - provides your report and underlying file details.
  - If your metadata (synonyms) is complicated, that is you have WebQuery created joins, metadata referencing other metadata, etc., you can use QMGTOOLS to gather your entire metadata infrastructure.  No user data is collected.  Use the ChgMgmt package to collect the report (.fex) and the first level of metadata (.acx, .mas) and step 7 (Complete re-create environment) to gather the rest of your metadata.
3) Client tracing
  - Session Viewer Trace for 2.2.1 and later
  - Section 2: Client Tracing for WebQuery 2.2.0
4) savediag    - saves diagnostic data
    4a) Logon to the system using the QWQADMIN *USRPRF
    4b) qsh        (from an IBM i command line, this puts you in QSH Command Entry instead of Command Entry)
    4c - WebQuery 2.2.1) cd /qibm/userdata/qwebqry/ibi/srv77/wfs/bin
    4c - WebQuery 2.3.x) cd /qibm/userdata/qwebqry/ibi/srv/wfs/bin
    4d) edastart -traceon
    4e) re-create issue (this step does not take place within qsh, etc.)
    4f) edastart -savediag
    4g) Select 2 from the menu to Save diagnostic to a directory
    4h) Press ENTER for the directory path for diagnostic information
    4i) Enter  Y to save the catalog files
    4j) Press ENTER for mapped application name
    4k) The collection of the files will begin, send the tar file generated
        in the directory mentioned in the savediag creation to IBM.
      For example the directory containing the tar file is in the message shown on screen:  
      e.g. 04/18/2020 12:35:13.210  Diagnostic Information has been saved
      in /qibm/userdata/qwebqry/ibi/srv77/wfs/savediag
      The file in that directory would be something like this:   sd041820_123513.tar
        - note that the date/time is the ‘name’ of the .tar

    4l) edastart -traceoff
    4m) F3=Exit         (return to Command Entry)
5) Fiddler trace   - collect web traffic data.   (only if requested by IBM i Global Support Center)
  5a) Close any open browser sessions, and Start Fiddler prior to starting any
      new browser session.  
      Confirm that tracing is started by clicking on File, and
      making sure that "Capture Traffic" is checked.
  5b) Start a browser such as Chrome, and only have that one browser and one tab active prior
      to collecting the trace
  5c) Logon to WebQuery and run the re-create
  5d) Once the report results are returned, Stop the Fiddler trace by clicking
      on File -> "Capture Traffic" so it become unchecked.
  5e) Save the trace by clicking on File -> Save -> All Sessions, Name the file and click Save.
  5f) Send the saved *.saz file to IBM via ECuRep/Case update
6) Developer WorkBench.      (only if requested by IBM i Global Support Center)
  Developer Workbench is a PC application but we will start with the same steps 1 - 4.
7) Complete re-create environment.     (only if you have a complex WebQuery metadata structure (from step 2) or if requested by IBM i Global Support Center)
    7a) Use QMGTOOLS
    7b) ADDLIBLE QMGTOOLS
    7c) GO MG
    7d) 12. Display build date
    7e) If not 02/15/22 or later go back to step 7a
    7f) 6. Database menu
    7g) 16. WebQuery Recreates
              Set 'WebQuery data to save' to *BOTH
    7h) follow the prompts to save your reports and metadata and upload to IBM. 
             - No data in any customer file is saved.
    7i) Use SQL to generate a list of WebQuery users. 
      From an IBM i command line:
      ===> crtdir '/tmp/DB2_WEBQUERY'  
             <ENTER>
      ===> QSH CMD('db2 -t -S -f /QSYS.LIB/QMGTOOLS.LIB/QMGDBSQL.FILE/WEBQ_USERS.MBR > /tmp/DB2_WEBQUERY/WEBQ_USERS.sql')
             <ENTER>
      - Upload /tmp/qmgdb/WEBQ_USERS.sql to your Case
      You can also use Run SQL Scripts if you'd like for step 7i
QMGTOOLS_Step_7i
             
  or   (instead of steps 7a -> 7i)
   MIGWEBQRY TYPE(*DIFSYS) LEVEL(*SAME) PHASE(*SAVE) (WebQuery ended first)
       Resulting IBM i save file is QGPL/QWQMIGWQX.
 
8) Data Management Console (DataMigrator)
image 5056
image 5057

Document Location

Worldwide

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m500000008jrjAAA","label":"IBM i WebQuery-\u003EDebug"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB57","label":"Power"}}]

Historical Number

N1010690

Document Information

Modified date:
28 July 2022

UID

ibm16190233