Debugging Barbara Unverferth 1 Techniques March 2002

Debugging

Barbara Unverferth

1

Techniques

March 2002

2

Agenda

Debugging difficulties with today’s technology

How to break a problem apart

What tools are available to you?

Problem Isolation System

Demo of Problem Isolation System and Support Site search capabilities

3

Debugging Difficulties with Today’s Technology

The “olden days”: COBOL to VSAM on MVS

Today:

Multi-tiered

Multi-vendor

Multi-products

Communications

DBMS’s

Security

Different people supporting different aspects

4

How to Break a Problem Apart

-12 data receive error, Error in transferring data, ODIN_10, or ODIN_4….”Where do I start?”

Identify the components and pull them apart

What is on each platform?

If existing application, what changed?

5

What Tools are Available for You?

Rdaapp, API Query Tool

Edastart –t, Interactive Agent, TSCOM3 in batch on MVS

Tracing

Turning retrieval off

6


Rdaapp, API Query Tool – NT:

7


Rdaapp, API Query Tool – UNIX, MVS, VM:<<< RDAAPP : Initializing EDA/API SQL, Version 5, Release 1 >>>

Default communications config file : /u2/css/ibi/srv51/ffs/etc/odin.cfg

Override? (Press enter for default) :

<<< Initialization Successful >>>

Enter User Name : Enter Password :

Enter server name, number, SELF, URL or ? (Hit return for 'LOOPBACK') :

<<< Successfully connected to synchronous server LOOPBACK >>>

Enter Command (? for command help):

8


RDAAPP commands: A Attach(Bind) paramters to prepared

statement B Browse... C Commit D Describe <table> E Execute <prepared statement handle> F Issue FOCUS REQUEST <request>; I Set EDAINFO display <ON or OFF> M Set fetch mode to A[lpha] or B[inary] O Set fetch mode to one row at a time P Prepare SQL <statement>; Q Disconnect R Rollback S Execute SQL <statement> or ? for help; T Set trace display <ON or OFF> U Unprepare <prepared statement handle> V Inspect/Set <EDA variable number> [<new

setting>] X Execute RPC <name> [<parameters>] or ? for

help

9



10



Allows you to test without using any communications or workload management

FOCUS-like environment

Dialogue manager commands must be in a FOCEXEC

11



Any errors generated from profiles should be shown here

Not full screen mode so cannot use TED or CRTFORM

FIN to exit

12


Tracing Tool on NT:

13


Tracing Components SET TRACEON=component Can be placed in global or user profiles, Remote

Procecure Call More detail at: http://techsupport.ibi.com/app/css_web_tool/Trace_General.htm

To trace at a user level: SET TRACEUSER=ON

How to get just the SQL SET TRACEON=STMTRACE Extract the SQL generated and running in native

SQL tool How to turn off other components:

SET TRACEOFF=ALL

14


Tracing Hub and Sub

Trace commands can be put in profile at each server

If using –REMOTE BEGIN:

-REMOTE BEGIN

SET TRACEOFF=ALL

SET TRACEON=STMTRACE

SET TRACEUSER=ON

TABLE FILE …..

15


Turning retrieval off:

SET XRETRIEVAL = OFF

Good for testing problems that occur prior to or after (and not related to) data retrieval

Do not need to have DBMS table created

16

An Example

-12 from an application when running a Remote Procedure Call (RPC)

First, remove application (MS Acccess, etc)

Test with API Query Tool (rdaapp) from client and at server level

Does the problem still occur?

If yes, then test with Interactive Agent

(edastart –t)

You will sometimes get a more descriptive error here

17

Another Example

Here is our configuration:

Windows NT Microsoft Access ODBC Hub TCP/IP HP-UX Sub Oracle

18

Let’s remove these pieces one by one:

Remove components one at a time

19

First we take out Microsoft Access, test using ODBC Query Tool:

Remove Microsoft Access

20

ODBC Test Tool

21

If the problem still occurs, we can remove ODBC and test

using the API client query tool to access the hub directly

Remove ODBC

22

API Test Tool

23

If problem still exists, we can remove the hub and

test directly on the sub, using the EDA client query tool

Remove Hub, go directly to Sub

24

<<< RDAAPP : Initializing EDA/API SQL, Version 5, Release 1 >>>

Default communications config file : /u2/css/ibi/srv51/ffs/etc/odin.cfg

Override? (Press enter for default) :

<<< Initialization Successful >>>

Enter User Name :

Enter Password :

Enter server name, number, SELF, URL or ? (Hit return for 'LOOPBACK') :

<<< Successfully connected to synchronous server LOOPBACK >>>

Enter Command (? for command help):

RDAAPP on HP-UX Sub

25

If problem still exits, we can remove the

communications and test the agent directly using the Interactive Agent

Remove Communications

26

RELEASE = R720510B

GEN_NUM = 12.05

SOURCE_DATE = 10/30/2001 17:04:49

BUILD_DATE = 10/31/2001 01:26:14

INSTALLATION_DATE= 10/31/2001 01:54:29

>>

Edastart –t on HP-UX

27

Using the Interactive Agent, we are able to see the

underlying error:

Problem found!

28

Problem Isolation System

Web-based application

Walks you through the components

Provides information on how to test at each level

Shows how to run test tools

Explains how to turn on tracing

Located on support site at:

http://techsupport.ibi.com/app/css_web_tool/default.htm

29

Demonstration of Problem Isolation System and Support Site Search Capabilities

Live demo but in case that doesn’t work…

30


31


32


33


34


35


36


37


38


39


40


41


42


43


44


45


46


47


Support site

48


Support site

49


50


51


52


53


54


55


56


57


58


59


60


61


62


63


64


65


Documents

Debugging Barbara Unverferth 1 Techniques March 2002