Compiling OS/390 application code for OLT and distributed debugging (CB)

In order to trace or debug with OLT, you must compile your code with specific environment variables set.

To compile your Java EJBs, servlets, or client application for WebSphere Advanced Single Server Edition on the OS/390 system, use the following command:

javac -g *.java

Then set a property in the was.conf file to add the source code path:

objectleveltrace.enabled=true
objectleveltrace.host=<Hostname>
objectleveltrace.port=2102

To compile your Component Broker server code for OLT:

  1. Generate OLT-enabled code by following the instructions for Compiling Component Broker applications from within Object Builder or Compiling Component Broker applications from the command line. See Compiling application code for OLT for these instructions.
  2. Set the following environment variables:
    export IVB_TRACE_DEBUG=1
    export JAVA_HOME=[path_to_JDK] # where [path_to_JDK] is the full path to your JDK 1.3
    export STEPLIB=none # no compiler override
    export _CEE_PREFIX=SYS1.CEE # default LE
    export _CEE_CBC=SYS1.CBC #default compiler
    export CB390_ROOT=
    <path_to_CB>
    # where <path_to_CB> is the full path to where WebSphere Enterprise Edition for OS/390 is installed.
    export IVB_DRIVER_PATH=
    $CB390_ROOT/usr/lpp/CB390
    export CB390_ENVFILE=
    $IVB_DRIVER_PATH/samples/CB390make.env
    # this file is needed by the Object Builder-generated makefile
    export NOHFSLNKOUT=1
  3. Compile your files:
    make -f all.mak
    Where all.mak is the Object Builder-generated makefile.

Your C++ code should be compiled with -g flag to create debug information. Java code should be compiled using the javac -g command.

Copy your source files to the Windows workstation where you plan to debug and set the DER_DBG_PATH environment variable to point to that directory.


Compiling application code for OLT and the IBM Distributed Debugger
Preparing for an OLT and IBM Distributed Debugger session on OS/390