Generating a Trace

How to:

If you encounter a server problem, you can run a set of traces that will help you assess the problem, and, if necessary, communicate it to Customer Support Services for further troubleshooting. This topic describes trace options and provides instruction for creating the traces.

There are two types of traces you can run to troubleshoot a problem:

Under normal conditions, most applications are run in a server context. However, if you run your trace in a non-server context (that is, if you run a non-server trace), you can produce the necessary diagnostic information while significantly reducing the amount of material that needs to be reviewed. Running a non-server trace also rules out server communications as a cause of your problem.

If you prefer to use DCL jobs to control tracing and save diagnostics functions, you can take advantage of a number of DCL scripts that are created during installation in theEDACONF [.BIN] directory and can be used to start traces, turn traces off, and perform edastart -savediag functions. The commands are, respectively, ITRCON.COM, ITRCOFF.COM, and ISAVEDIA.COM. An alternate ID parameter is available, under which you can submit the job. For details, see Other DCL Programs.

Top of page
x
Procedure: How to Generate a Server Trace

To generate a server trace:

  1. Turn tracing on by doing one of the following:
    • Go to the Web Console menu bar, select Workspace and then Enable Traces.
    • Start the server by issuing the following command:

      edastart -traceon

      Note: Preface edastart with an @ sign and pathname, unless a symbol has been set up.

  2. Reproduce the problem.
  3. Stop the server.
  4. Issue the following command: 
    edastart -savediag
  5. Respond to the prompts to capture, and optionally archive, diagnostic information.

    For information about sending the diagnostic information to Customer Support Services, see Information You Should Have and Customer Support.

Top of page
x
Procedure: How to Generate a Non-Server Trace

To generate a non-server trace:

  1. Create a directory under APPROOT to reproduce the problem.
  2. Copy any files required for the reproduction to the directory.
  3. Switch to the directory.
  4. Reproduce the problem using edastart -traceon and one of switches -t, -x, or -f.
  5. Switch to a directory other than the problem reproduction directory.
  6. Issue the following command: 
    edastart –savediag

    Note: Preface edastart with an @ sign and pathname, unless a symbol has been set up.

  7. Respond to the prompts to capture, and optionally archive, diagnostic information.

    For information about sending the diagnostic information to Customer Support Services, see Information You Should Have and Customer Support.

iWay Software