Configuring Tracing

How to: Set Up Tracing Enable All Traces Enable API Trace Levels 1-8 and ODIN Trace Levels 1-5 (Installed Default) Enable Specific API Trace Levels Enable Specific ODIN Trace Levels Disable Tracing

This section describes how to set up tracing, enable and disable tracing, and enable specific API and ODIN trace levels. Configuration of tracing is generic for all platforms. It is important to remember that configuration of what to trace is a separate step from activation of actual tracing.

Procedure: How to Set Up Tracing

1. Depending on you platform, create the file ibitrace.fex in the catalog directory of your EDACONF directory (UNIX, OS/390, z/OS, OpenVMS, OS/400) or allocate the DD name IBITRACE (MVS) to a data set member. For example:

UNIX:

touch /home/admin/catalog/ibitrace.fex

OS/390 and z/OS:

touch /home/.admin/catalog/ibitrace.fex

OS/400:

touch /home/admin/catalog/ibitrace.fex

OpenVMS:

EDIT DISK$DUA0:[admin.IBI.CLIENT71.CONF.CATALOG]ibitrace.fex

MVS:

//IBITRACE DD DSN=<qual>.EDACTL.DATA(IBITRACE),DISP=SHR

Alternate ibitrace.fex locations file and names may be specified. Setting the IBITRACE environment variable to the full path name of the file does this. For example,

UNIX: export IBITRACE=/home/admin/mytrace.fex

OS/390 and z/OS: export IBITRACE=/home/admin/mytrace.fex

OS/400: export IBITRACE=/home/admin/mytrace.fex

OpenVMS: DEFINE IBITRACE DISK$DUA0:[ADMIN]MYTRACE.FEX

2. Using any editor, edit and add or change trace commands in the IBITRACE file as needed based upon the available setting below.

3. By default, for RDAAPP tracing output is written to rdaapp.trc on UNIX, OS/390, z/OS, OpenVMS, and Windows and the FSTRACE DD name on MVS. You may allocate FSTRACE to redirect trace output in the same way as IBITRACE.

Customer written applications using EDACALLBACK will depend on where the application decides to write traces. However, the iWay supplied EDAAPP C sample uses edaapp.trc.

Syntax: How to Enable All Traces

SET TRACEON = ALL

Syntax: How to Enable API Trace Levels 1-8 and ODIN Trace Levels 1-5 (Installed Default)

SET TRACEON = DEFAULT

Syntax: How to Enable Specific API Trace Levels

SET TRACEON = EDAAPI[/nnnnnnnn]

where:

nnnnnnnn

Represents trace levels 1 - 8. Possible values are:

Levels

1 - (1nn) API Calls Entry/Exit and User Log (399).

2 - (2nn) Locking and Internal Flow.

3 - (3nn) Errors.

4 - (4nn) Messages from EDASETS.

5 - (5nn) Data to Server.

6 - (6nn) Data from Server.

7 - (7nn) Internal Logic including memory allocations.

8 - (8nn) API use of communications.

For example, SET TRACEON = EDAAPI/123456 would enable trace levels 1 through 6.

Syntax: How to Enable Specific ODIN Trace Levels

SET TRACEON = ODIN[/nnnnn]

where:

nnnnn

Represents the ODIN trace level 1-5. Possible values are:

Levels

1 - (901) Errors.

2 - (902) Warnings.

3 - (903) Informational.

4 - (904) Reserved for future use.

5 - (905) Buffer Dump.

(9nn) ODIN communications (where nn=ODIN trace level).

Syntax: How to Disable Tracing

SET TRACEOFF = ALL 
SET TRACEOFF = EDAAPI
SET TRACEOFF = ODIN