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:

  1. Compiling OS/390 application code for OLT (CB)
  2. Preparing a client environment for OLT. Choose one of the following:
  3. Preparing the OS/390 host environment. Choose one of the following:
  4. Tracing a distributed application
  5. Setting method breakpoints on the trace
  6. 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:

  1. 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.
  2. Modify the following OS/390 environment variables to point to the Java engine:

If you are using WebSphere Application Server V4.0 for z/OS and OS/390, do the following:

  1. 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.
  2. On your Windows NT/2000 workstation,


Supported platforms and languages