You can issue the modify command from the MVS console to dynamically modify product operations.
Use the following format when entering the modify command.
f <server>, parameters
server is the short name for the server to which the modify command is directed. This argument is required.
The following parameters are valid for the modify command:
You can specify the following options for the CANCEL parameter:
Specifying INTERVAL sets the amount of time, in seconds, during which a diagnostic action is not repeated. This attribute overrides the value specified for the ras_java_oom_interval environment variable.
Specifying ACTION sets the diagnostic action that is taken when a JVM out-of-memory condition occurs in this server. This attribute overrides the value specified for the ras_java_oom_action environment variable. One of the following values can be specified as the value for xxx:
Specifying RESET Resets the diagnostic action and interval to the values specified for the ras_java_oom_action and ras_java_oom_interval environment variables.
After the specified dump is processed, you can reissue this command to change the value of the control_region_timeout_delay variable back to its previous setting without recycling the server.
The following table shows the values you can specify for this parameter. You can specify one or more of these values for either TRACEBASIC or TRACEDETAIL:
Value | Product component |
---|---|
0 | RAS |
1 | Common Utilities |
3 | COMM |
4 | ORB |
6 | OTS |
7 | Shasta |
9 | z/OS® Wrappers |
A | Daemon |
E | Security |
F | Externalization |
J (Should only be used under the direction of IBM Support) | JRas |
L | Java EE |
Specifying YES sends the trace to SYSPRINT, and specifying NO stops the sending of the trace to SYSPRINT.
Specifying YES sends the trace to the TRCFILE DD card, and specifying NO stops the sending of 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 for this parameter:
OLATRACE is a keyword with a parameter that
Formats and displays optimized local adapter trace records to the WebSphere Application Server SYSOUT, if tracing is enabled. To enable adapter tracing for specific registrations or for broad situations, see the topic, Using optimized local adapters diagnostic information.
Syntax
F <server>, DISPLAY, OLATRACE=jobname
F BBOS001, DISPLAY, OLATRACE=WOLAJOB1
F BBOS001, DISPLAY, OLATRACE=*
******** OLATRACE modify command output start ****************************\n"; ******** Trace records for jobname: <jjjjjjjjj> < formatted trace records > ******** End of OLATRACE modify command output ***************************
You cannot cancel a cluster from the MVS console. Instead, you must cancel each of the servers that make up the cluster.
f bbo6acr,cancel
f bbo6acr,cancel,armrestart
f server,traceall=n
Valid trace levels are 0 (none), 1 (exception), 2 (basic), and 3 (detailed tracing). Under normal conditions and in production, use 1 (exception).
f bbo6acr,traceall=1
f bbo6acr,traceall=1 BBOO0211I MODIFY COMMAND TRACEALL=1 COMPLETED SUCCESSFULLY
This example demonstrates how to specify the WebSphere® for z/OS® components for which you want to switch on a basic level of tracing.
f server,tracebasic=(n,...)
f bbo6acr,tracebasic=a
f bbo6acr,TRACEBASIC=A BBOO0211I MODIFY COMMAND TRACEBASIC=A COMPLETED SUCCESSFULLY
f server,tracedetail=(n,...)
f bbo6acr,tracedetail=e
f bbo6acr,TRACEDETAIL=E BBOO0211I MODIFY COMMAND TRACEDETAIL=E COMPLETED SUCCESSFULLY
f server,tracespecific=n | (n,...)
f bbo6acr,tracespecific=04006001
f bbo6acr,tracespecific=(04006001,04006027)
f bbo6acr,tracespecific='tracepoints'
f server,trace_exclude_specific=n | (n,...)
f bbo6acr,tracespecific=04006000 f bbo6acr,trace_exclude_specific=04006031
f server,traceinit
f server,tracenone
f server,tracetosysprint=yes
f server,tracetosysprint=no
This example demonstrates how to cancel application clusters and servers with the modify command.
Before you begin: You cannot cancel a cluster from the MVS console. Instead, you must cancel each of the servers that make up the cluster.
f bbo6acr,cancel
f bbo6acr,cancel,armrestart
You can get syntax help for the various levels of the modify command.
f bbo6acr,help
F bbo6acr,HELP BBOO0178I THE COMMAND MODIFY MAY BE FOLLOWED BY ONE OF THE FOLLOWING KEYWORDS: BBOO0179I CANCEL - CANCEL THIS CONTROL REGION BBOO0179I TRACEALL - SET OVERALL TRACE LEVEL BBOO0179I TRACEBASIC - SET BASIC TRACE COMPONENTS BBOO0179I TRACEDETAIL - SET DETAILED TRACE COMPONENTS BBOO0179I TRACESPECIFIC - SET SPECIFIC TRACE POINTS BBOO0179I TRACEINIT - RESET TO INITIAL TRACE SETTINGS BBOO0179I TRACENONE - TURN OFF ALL TRACING BBOO0179I TRACETOSYSPRINT - SEND TRACE OUTPUT TO SYSPRINT (YES/NO) BBOO0179I TRACETOTRCFILE - SEND TRACE OUTPUT TO TRCFILE DD CARD (YES/NO) BBOO0179I DISPLAY - DISPLAY STATUS BBOO0179I TRACE_EXCLUDE_SPECIFIC - EXCLUDE SPECIFIC TRACE POINTS BBOO0179I TRACEJAVA - SET JAVA TRACE OPTIONS BBOO0179I TRACETOTRCFILE - SEND TRACE OUTPUT TO TRCFILE (YES/NO) BBOO0179I MDBSTATS - MDB DETAILED STATISTICS BBOO0179I PAUSELISTENERS - PAUSE THE COMMUNICATION LISTENERS BBOO0179I RESUMELISTENERS - RESUME THE COMMUNICATION LISTENERS BBOO0179I STACKTRACE - LOG JAVA THREAD STACK TRACEBACKS BBOO0179I TIMEOUTDUMPACTION - SET TIMEOUT DUMP ACTION BBOO0179I TIMEOUTDUMPACTIONSESSION - SET TIMEOUT DUMP ACTION SESSION BBOO0179I WLM_MIN_MAX - RESET WLM MIN/MAX SERVANT SETTINGS
f bbo6acr,display,help
F BBOS001,DISPLAY,HELP BBOO0178I THE COMMAND DISPLAY, MAY BE FOLLOWED BY ONE OF THE FOLLOWING 124 KEYWORDS: BBOO0179I SERVERS - DISPLAY ACTIVE CONTROL PROCESSES BBOO0179I SERVANTS - DISPLAY SERVANT PROCESSES OWNED BY THIS CONTROL 126 PROCESS BBOO0179I LISTENERS - DISPLAY LISTENERS BBOO0179I CONNECTIONS - DISPLAY CONNECTION INFORMATION BBOO0179I TRACE - DISPLAY INFORMATION ABOUT TRACE SETTINGS BBOO0179I JVMHEAP - DISPLAY JVM HEAP STATISTICS BBOO0179I WORK - DISPLAY WORK ELEMENTS BBOO0179I ERRLOG - DISPLAY THE LAST 10 ENTRIES IN THE ERROR LOG BBOO0179I MODE - DISPLAY THE EXECUTION BITMODE BBOO0188I END OF OUTPUT FOR COMMAND DISPLAY,HELP
f bbos001,timeoutdumpactionsession=help
BBOO0178I THE COMMAND MODIFY TIMEOUTDUMPACTIONSESSION= MAY BE FOLLOWED BY ONE OF the FOLLOWING KEYWORDS: BBOO0179I SVCDUMP - SVC DUMP BBOO0179I JAVACORE - JAVA CORE DUMP BBOO0179I NONE - NO DUMP
f bbos001,dpm,help
BBOO0178I THE COMMAND MODIFY DPM, MAY BE FOLLOWED BY ONE OF THE FOLLOWING KEYWORDS: BBOO0179I IIOP - IIOP DISPATCH PROGRESS MONITOR INTERVAL BOO0179I HTTP - HTTP DISPATCH PROGRESS MONITOR INTERVAL BOO0179I HTTPS - HTTPS DISPATCH PROGRESS MONITOR INTERVAL BOO0179I MDB - MDB DISPATCH PROGRESS MONITOR INTERVAL BOO0179I SIP - SIP DISPATCH PROGRESS MONITOR INTERVAL BOO0179I SIPS - SIPS DISPATCH PROGRESS MONITOR INTERVAL BOO0179I CLEAR_ALL - CLEAR ALL DISPATCH PROGRESS MONITOR SETTINGS BOO0179I DUMP_ACTION - DISPATCH PROGRESS MONITOR DUMP ACTION BOO0211I MODIFY COMMAND DPM, COMPLETED SUCCESSFULLY
This example shows how to use a console command to modify a Java trace string.
f server, tracejava='trace specification'
f bbo6acr,tracejava='*=all'
This example shows how to use a console command to modify the diagnostic action that is taken if a Java Virtual Machine (JVM) out-of-memory condition occurs, use the following command:
f server,javaoom,[interval=xxx | action=xxx]
f bbo6acr,,javaoom,[interval=1200 | action=svcdump]