CICS Transaction Gateway V5 The WebSphere ... - IBM Redbooks

To activate J2EE Server tracing, we also added the following variables:
► TRACEALL=1
► TRACEBUFFLOC=SYSPRINT
This causes level 1 trace entries to be written to the SYSPRINT of the J2EE
Server.
Note: Tracing in the J2EE Server takes effect as soon as the server is
restarted. Since this means that the startup process itself will be traced, you
will notice that startup will take a longer time to complete than normal.
You may have noticed the operand we chose to open the variable list for input
was JVM_LOGFILE. This operand indicates where output from the trace will be
sent. The value we specified was /tmp/WAS.jvm.log. A sample view of the trace
data sent to this file is shown in Example 10-10.
Example 10-10 Sample output from JVM trace
Opened /usr/lpp/java/IBM/J1.3/lib/rt.jar in 134 ms¨
Opened /usr/lpp/java/IBM/J1.3/lib/i18n.jar in 6 ms¨
Loaded java.lang.NoClassDefFoundError from /usr/lpp/java/IBM/J1.3/lib/rt.jar¨
Loaded java.lang.Class from /usr/lpp/java/IBM/J1.3/lib/rt.jar¨
Loaded java.lang.Object from /usr/lpp/java/IBM/J1.3/lib/rt.jar¨
Loading superclasses of java/lang/Object¨
Loaded java.lang.Throwable from /usr/lpp/java/IBM/J1.3/lib/rt.jar¨
Loading superclasses of java/lang/Throwable¨
Loaded java.io.Serializable from /usr/lpp/java/IBM/J1.3/lib/rt.jar¨
Loading superclasses of java/io/Serializable¨
Preparing java/lang/Object¨
Initializing java/lang/Object¨
HTTP Server tracing
If you are using the HTTP Server as the HTTP protocol catcher, trace can be
activated by setting the -v or -vv parameters in the startup procedure. To activate
trace in a running server, you can use the SDSF command:
F SCSWEBC6,APPL=-VV
Chapter 10. CICS TG and WebSphere Application Server for z/OS 287