IBM Support

Web Query 2.x Tracing

Troubleshooting


Problem

This document provides instructions for WebQuery tracing. 

There is two 'sections' within this TechNote. 
The first is for WebQuery 2.2.1 and later (Session Viewer Trace)
The second section is a "table view" that has to be used for WebQuery releases before WebQuery 2.2.1 and is also used for WebQuery 2.2.1 when more detail is needed than the Session Viewer Trace provides.

If you are at WebQuery 2.2.1 or later - your IBM i Global Support Representative will likely start with the Session View Trace.
The Session Viewer Trace will be sufficient for a major of situations.

Resolving The Problem

Section 1:  Session Viewer Trace  (WebQuery 2.2.1 and later releases)

1. From the BI portal, select 'Session Viewer' from the Tools menu (top right hand side)
If you don't have that option, you'll need to find a WebQuery Admin, etc.
WebQuery 2.2.1
image-20190403123935-1   
WebQuery 2.3.x
  WebQuery23_SessionViewer
This will pop up the Session Viewer
2. Unless told otherwise, change the 'Tracing Level" to Debug and Fex Echo Setting to All
Do this step just before the recreate (i.e one click away from recreate)
Here's an example:
image-20190403124534-2
3. Run the recreate
4. Use the 'ZIP Session Traces' on the right side
5. Upload the resulting .zip file to your WebQuery Salesforce Case
 

Section 2:  "Table view" on Web Query 2.x traces.

Also consider recording your actions via a "movie" - http://www.ibm.com/support/docview.wss?uid=nas8N1020974

Client Tracing and/or Server Tracing  (Session View Trace below)

Note: There will be three different Web pages going during tracing. Steps 1, 2 and 3 each have a separate Web browser page/tab.
 

Recreate Client Tracing Server Tracing
Internet Explorer or Firefox Firefox or Internet Explorer

Note: Use a different browser than the "Recreate" column, but can be the same as the "Server Tracing" browser		 Firefox or Internet Explorer

Note: Use a different browser than the "Recreate" column, but can be the same as the "Client Tracing" browser
1. Position one click away from creating the error (in other words, open the procedure that errors, run it to confirm it still errors, and be ready to click one time to reproduce the error).
2.

a. Log in as an administrator (for example, QWQADMIN) to the BI Portal.

BI Portal example URL


b. On the top right side, select Administration, and then select Administration Console. This will bring up the Web Query Administration Console in a separate window.

WebQuery 2.2.0:

c. On left hand side, you will see a function tree. Click Diagnostics, and then click WFServlet (under Traces).

d. Delete all old traces by clicking Select all, and then click Delete. (Both are at the bottom of the screen.)

e. Click Trace On (which is at the top).

WebQuery 2.2.1:

f. On the top tool bar, select Diagnostics

g. Select Session Monitor from left hand tree view

h. Find the session to trace by either the PC's IP address or the Client User

i. Select "Details" for the Trace Control pulldown (the default is Off)


Note: Do not close this browser session because it will be used again.

 

Note for step c: Usually we will want WFServlet.
However sometimes we may need something different - for example Web Services for RAX issues or Report Broker for scheduling issues
3.
a. Log in as an administrator (for example, QWQADMIN) to the Server Web Console

Server Web Console example URL


- this is the Server Web Console. Also referred to as Web Console and Reporting Server Console

b. After signing on as an administrator, you will see a tool bar across the top. Click "Workspace"
WebQuery 2.2.0:

c. On the left hand side, you will see a function tree. Expand Logs and Traces. Right click Traces and then right click Enable Traces.

WebQuery 2.2.1:

c. On the top right hand side, you will see the userid you signed in as with a pull down option (it's between 'Scalability' and 'Help') - select Enable Traces


Note: Do not close this browser session because it will be used again.
4. Reproduce the error by clicking the 1-click reproduction set up by Step 1.

Note: If you receive an Access Denied error, sign in again.
5.

WebQuery 2.2.0:

Under diagnostics, WFServlet, click Trace Off.

WebQuery 2.2.1:

Change Trace Control back to "Off"

WebQuery 2.2.0:

Under Workspace, click Disable Traces.
WebQuery 2.2.1:
On the top right hand side, you will see the userid you signed in as with a pull down option (it's between 'Scalability' and 'Help') - select Disable Traces
6.

WebQuery 2.2.0:

The WFServlet (Client) traces will be located in the following:

/QIBM/UserData/qwebqry/base80/logs

There may be multiple files.

Using iNavigator is the easiest method, using File Systems -> Integrated File System -> Root -> QIBM.

Copy all the files with the same date and time as when the trace was run to your PC

Zip this set of files.

WebQuery 2.2.1:

Select the 'i' under Trace for the session  you've traced

image-20180821091734-1

This will bring up a separate window

Select the ZIP Session Traces link

image-20180821091956-2
You can bundle the Server traces using the savediag feature. Return to the browser window from Step 3.

WebQuery 2.2.0:

i. Under Workspace, Logs and Traces, right click Workspace Logs, and select Savediag - Report a Bug.
WebQuery 2.2.1:
i. Under Workspace right click on Workspace Logs and select 'Savediag - Report a Bug'
Both WebQuery 2.2.0 and  2.2.1:
ii. Change Diagnostics Options to Save Diagnostics (savediag).
iii. Leave Copy files from catalog to savediag as Yes.
iv. Note the directory provided for Savediag Directory.
v. Update List of Applications to include all the Top Level Folders that were involved in the recreate.  
vi. Press Submit. This will do the bundling. After a few seconds/minutes, you will see a Savediag log.
vii. Scroll to the bottom, and you will see a message similar to the following:

.... Diagnostic directory has been compressed as ...

Then you will be able to use iNavigator to find it using File Systems -> Integrated File System -> Root -> QIBM and copy to your PC.
7

1. In addition to the data collected in step 6, zip all files that start with "event" in /qibm/userdata/qwebqry/base80/logs


2. Upload http://www.ecurep.ibm.com/app/upload .

Note: Upload is for: OS/400.

If you do not have a Salesforce Case yet, you should wait on this step until you have one.

 1. Zip the files. (might already be a .tar or .zip file)
2. http://www.ecurep.ibm.com/app/upload .

Note: Upload is for: OS/400.

If you do not have a PMR number yet, you should wait on this step until you have one.

 

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

Historical Number

N1010503

Document Information

Modified date:
23 December 2020

UID

nas8N1010503

Page Feedback