Preparing for an OLT and IBM Distributed Debugger session on OS/390
OLT enables you to monitor the flow of a distributed application,
and to seamlessly debug client and server code from a single workstation. A typical
Object Level Trace (OLT) session on OS/390 consists of the following steps:
- Compiling OS/390 application code for OLT (CB)
- Preparing a client environment for OLT. Choose one of the following:
- Preparing the OS/390 host environment. Choose one of the following:
- Tracing a distributed application
- Setting method breakpoints on the trace
- Running the Debugger with OLT
Before running a
Java OLT session on OS/390, make sure that you have installed the IBM Distributed Debugger
Java engine on the OS/390 system according to the steps below, depending on the
edition of WebSphere Application Server that you are using.
If you are running WebSphere Application Server V3.5 Standard Edition for
OS/390, do the following:
- From the Windows NT/2000 or the AIX OLT/DD common install CD, copy the extras/
directory and its contents to your workstation and FTP the directory and files to the
OS/390 system.
- Modify the following OS/390 environment variables to point to the Java engine:
- CLASSPATH to point to extras/390/lib/derdebug.jar
- PATH to point to extras/390/bin/
If you are using WebSphere Application Server V4.0 for z/OS and OS/390, do
the following:
- Modify the OS/390 current.env environment variable file to include
JVM_DEBUG_PORT=xxxx where xxxx is the JVM port number
to which your application would be connecting.
- On your Windows NT/2000 workstation,
- The level of JDK must be the same as is in your OS/390 system (JDK 1.3).
- In order to step through the code, you will need to copy the source of your application from
the OS/390 server to your workstation.
- After copying the source to a location on the workstation, modify the DER_DBG_PATH environment
variable to include the directory or directories to which you have
copied the source. For more information about the DER_DBG_PATH environment variable, please
see the debugger DER_DBG_PATH reference topic.

Supported platforms and languages