Problem Determination for WebSphere for z/OS

Chapter 18. Commands 201

18.2.2 Basic TRACE commands

Because trace or diagnostic data is not documented and is only useful to the IBM support

team, you should only use these traces at the request of IBM. For this reason, we only list a

few commands here and do not cover them in detail:

 To turn tracing to SYSPRINT on and off:

MODIFY <server_name>,TRACETOSYSPRINT=YES | NO

 To change the overall trace level (F is short for MODIFY):

F <server_name>,TRACEALL=0 | 1 | 2 | 3

 To turn on basic or detailed tracing for specified components (non-Java):

F <server_name>,TRACEBASIC=(0,1,2...)

F <server_name>,TRACEDETAIL=(0,1,2..)

Explanations of the codes are in Table 18-2.

Table 18-2 TRACEBASIC/TRACEDETAIL codes

 To turn off all tracing:

F <server_name>,TRACENONE

Other useful trace commands are:

F <control_region_JOBNAME>,TRACESPECIFIC

F <control_region_JOBNAME>,TRACE_EXCLUDE_SPECIFIC

F <control_region_JOBNAME>,TRACETOTRCFILE

F <control_region_JOBNAME>,MDBSTATS

18.2.3 Dynamic Java TRACE

One of the most important tools is the MVS Modify command that dynamically turns Java

tracing on and off. It is well documented at the WebSphere for z/OS Information Center, but

can be overlooked among all the other tracing tools.

d trace[,comp=cname] Trace settings

d xcf,cpl | str XCF parameters and couple data sets | structures

$dspl JES2 spool utilization

Command Explanation

Code Explanation Code Explanation

0RAS ADaemon

1 Common utilities E Security

3 COMM F Externalization

4ORB JJRAS

6OTS LJ2EE

7 Shastat

9 z/OS wrappers