You can use the modify command to display status of various server components and activities, including:
Syntax
f <server>, options
The first argument is required. The argument is the name of the server for which the modify command will be directed.
Parameters
The options for the modify command follow:
You can specify the following options:
Note: You cannot use the CANCEL parameter to cancel a cluster from the MVS console. Instead, you must cancel each of the servers that make up the cluster.
Valid trace levels are 0 (none), 1 (exception), 2 (basic), and 3 (detailed tracing). Under normal conditions and in production, use 1 (exception).
Note: Be careful when using a level of 3 (detailed for all components) because it can potentially yield more data than can be handled reasonably.
This command has the ability to override a different tracing level established by TRACEALL for those components.
Note: Do not change this variable unless directed by IBM service personnel.
You can specify one or more of the following options for either TRACEBASIC or TRACEDETAIL:
This command activates the most detailed tracing for the specified WebSphere for z/OS components and overrides different settings inTRACEALL. The selected components (n,...) are identified by their component-ID (valid values are the same as for TRACEBASIC above. Subcomponents, specified by numbers, receive detailed traces. Other parts of WebSphere for z/OS receive tracing as specified on the TRACEALL variable.
Note: Do not change this variable unless directed by IBM service personnel.
Trace points are specified by 8-digit, hexadecimal numbers. To specify more than one trace point, use parentheses and separate the numbers with commas. You can also specify an environment variable name by enclosing the name in single quotes. The value of the environment variable will be handled as if you had specified that value on TRACESPECIFIC.
Note: Do not use TRACESPECIFIC unless directed by IBM service personnel.
Trace points to exclude are specified by 8-digit, hexadecimal numbers. To specify more than one trace point, use parentheses and separate the numbers with commas. You can also specify an environment variable name by enclosing the name in single quotes. The value of the environment variable will be handled as if you had specified that value on TRACE_EXCLUDE_SPECIFIC. You can use TRACE_EXCLUDE_SPECIFIC as a mask to turn off otherwise-on traces. For example, use the TRACESPECIFIC command to turn on tracing for a whole part and then use TRACE_EXCLUDE_SPECIFIC to turn off one trace within that part.
Note: Do not use TRACE_EXCLUDE_SPECIFIC unless directed by IBM service personnel.
YES specifies to send the trace to sysprint and NO stops sending the trace to sysprint.
YES specifies to send the trace to the TRCFILE DD card and NO stops sending the trace to the TRCFILE DD card.
The java trace specification is used to control java tracing and conforms to the java trace specification rules. *=all=enabled means to enable all types of tracing for all registered trace components.
You can also use the HELP parameter after the CANCEL, and DISPLAY parameters to display lists of all the keywords you can use with either of these parameters.
You can specify the following options:
You can further modify this command with one of the following options:
You can further modify this command with one of the following options:
You can further modify this command with one of the following options:
You can further modify this command with one of the following options:
You can further modify this command with one of the following options:
Note: The LIST and HELP parameters are also available with the other session protocol display commands.