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:
The nnn placeholder specifies, in seconds, the length of the time interval for a specific protocol type. The value for the nnn placeholder must be an integer 0 - 255, or reset. A value of 0 illustrates that the protocol has no interval and that DPM is disabled for requests that use that protocol. A value of reset illustrates that the control of the DPM interval is returned to the dpm_interval classification attribute in the workload classification file.
The DPM INTERVAL modify command overrides the dpm_interval classification attribute. The DPM dump_action modify command overrides the dpm_dump_action classification attribute and the server_region_dpm_dump_action server-wide property.
Specifying RESET on the dump action deactivates the dump action for the modify command. The settings for the dpm_dump_action classification attribute and the server_region_dpm_dump_action server-wide property are again in effect.
A value specified on the INTERVAL parameter sets the DPM interval for all six protocols to the same value.
The clear_all value sets the time intervals for all related request protocols to 0 and the dump action to None.
The reset_all value resets all the DPM intervals and the dump_action parameter. Control of the DPM intervals and the dump action is returned to the WLM classification file.
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.
The xxx placeholder is a comma delimited list of product message IDs for the application server to route. Messages can be routed to more than one location.
The first time that you issue the command for a location and a set of messages, the message list for the location is the message list of the first command. If the environment variable for the location has messages defined, those messages are appended to the message list of the location. When you later issue the command for the same location and another set of messages, the application server appends the messages of the subsequent command to the existing list of messages.
Specifying ERRORLOG routes the messages to the error log instead of the default location.
Specifying HARDCOPY routes the messages to the SYSLOG system log, also known as hardcopy, instead of the default location.
Specifying CONSOLE routes the messages to the MVS operator console instead of the default location.
Specifying COPYERRORLOG copies the messages to the error log as well as the default location.
Specifying COPYHARDCOPY copies the messages to the SYSLOG system log, also known as hardcopy, as well as the default location
Specifying COPYCONSOLE copies the messages to the MVS operator console as well as the default location.
Specifying NONE suppresses the routing of the messages. A value of NONE takes precedence over routing of messages to the error log, the system log, or the MVS operator console.
Specifying RECLASSIFY performs reclassification using the workload classification file specified on the wlm_classification_file variable.
Specifying a file name with the reclassify parameter such as RECLASSIFY,FILE='/path/to/newfile.xml' performs reclassification using the classification file specified. The value for the wlm_classification_file variable changes to the file specified on the FILE option. Any subsequent reclassify modify commands that use the wlm_classification_file variable reload the new file specified on the variable, not the original file.
Specifying RECLASSIFY,FILE= disables classification. The wlm_classification_file variable is set to null. Any subsequent reclassify modify commands that use the wlm_classification_file variable do not affect the server since the wlm_classification_file variable has no value.
BBOJ0129I: The /tmp/wlm4.class.xml workload classification file was loaded at 2009/07/14 19:33:35.297 (GMT)
The SMF,REQUEST modify command overrides the SMF_request_activity_enabled classification attribute and the server_SMF_request_activity_enabled server-wide property.
Specifying ON turns on the creation of SMF 120-9 records.
Specifying OFF turns off the creation of SMF 120-9 records.
Specifying RESET deactivates the modify command setting for the creation of SMF 120-9 records. The settings for the SMF_request_activity_enabled classification attribute and the server_SMF_request_activity_enabled server-wide property at the time of the reset are in effect.
The SMF,REQUEST,ASYNC modify command overrides the server_SMF_request_activity_async server-wide property.
Specifying ON turns on the collection of the data.
Specifying OFF turns off the collection of the data. When this value is specified, records that are created have zeros for this section in the location triplets at the top of the record.
Specifying RESET deactivates the modify command setting for the collection of the data. The settings for the the server_SMF_request_activity_async server-wide property at the time of the reset are in effect.
The SMF,REQUEST,CPU modify command overrides the SMF_request_activity_CPU_detail classification attribute and the server_SMF_request_activity_CPU_detail server-wide property.
Specifying ON turns on the collection of the data.
Specifying OFF turns off the collection of the data. When this value is specified, records that are created have zeros for this section in the location triplets at the top of the record.
Specifying RESET deactivates the modify command setting for the collection of the data. The settings for the SMF_request_activity_CPU_detail classification attribute and the server_SMF_request_activity_CPU_detail server-wide property at the time of the reset are in effect.
The SMF,REQUEST,SECURITY modify command overrides the SMF_request_activity_security classification attribute and the server_SMF_request_activity_security server-wide property.
Specifying ON turns on the collection of the data.
Specifying OFF turns off the collection of the data. When this value is specified, records that are created have zeros for this section in the location triplets at the top of the record.
Specifying RESET deactivates the modify command setting for the collection of the data. The settings for the SMF_request_activity_security classification attribute and the server_SMF_request_activity_security server-wide property at the time of the reset are in effect.
The SMF,REQUEST,TIMESTAMPS modify command overrides the SMF_request_activity_timestamps classification attribute and the server_SMF_request_activity_timestamps server-wide property.
Specifying ON turns on the collection of the data.
Specifying OFF turns off the collection of the data. When this value is specified, records that are created have zeros for this section in the location triplets at the top of the record.
Specifying RESET deactivates the modify command setting for the collection of the data. The settings for the SMF_request_activity_timestamps classification attribute and the server_SMF_request_activity_timestamps server-wide property at the time of the reset are in effect.
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 includes the values that 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 be used only 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.
Specifying ON causes trace records to be written based on the current trace specification. Any classification_only_trace attributes are ignored.
The default value is RESET.
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:
MODIFY server,JAVACORE,ASIDX=F4
In this example, the command takes a JAVACORE of the
servant region whose (hex) ASID is 'F4'.f bbos001,DISABLEFAILOVER,'jdbc/MySampleDataSource'
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
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
BBOO0179I HTTP - HTTP DISPATCH PROGRESS MONITOR INTERVAL
BBOO0179I HTTPS - HTTPS DISPATCH PROGRESS MONITOR INTERVAL
BBOO0179I MDB - MDB DISPATCH PROGRESS MONITOR INTERVAL
BBOO0179I SIP - SIP DISPATCH PROGRESS MONITOR INTERVAL
BBOO0179I SIPS - SIPS DISPATCH PROGRESS MONITOR INTERVAL
BBOO0179I INTERVAL - ALL DISPATCH PROGRESS MONITOR INTERVALS
BBOO0179I OLA - OLA DISPATCH PROGRESS MONITOR INTERVAL
BBOO0179I DUMP_ACTION - DISPATCH PROGRESS MONITOR DUMP ACTION
BBOO0179I CLEAR_ALL - CLEAR ALL DISPATCH PROGRESS MONITOR SETTINGS
BBOO0179I RESET_ALL - RESET ALL DISPATCH PROGRESS MONITOR SETTINGS
BBOO0211I MODIFY COMMAND DPM, COMPLETED SUCCESSFULLY
If
you have Fix Pack 8.5.5.1 or higher installed, the resulting output
is like the following example:BBOO0178I THE COMMAND MODIFY DPM, MAY BE FOLLOWED BY ONE OF THE
FOLLOWING KEYWORDS:
BBOO0179I IIOP - IIOP DISPATCH PROGRESS MONITOR INTERVAL
BBOO0179I HTTP - HTTP DISPATCH PROGRESS MONITOR INTERVAL
BBOO0179I HTTPS - HTTPS DISPATCH PROGRESS MONITOR INTERVAL
BBOO0179I MDB - MDB DISPATCH PROGRESS MONITOR INTERVAL
BBOO0179I SIP - SIP DISPATCH PROGRESS MONITOR INTERVAL
BBOO0179I SIPS - SIPS DISPATCH PROGRESS MONITOR INTERVAL
BBOO0179I OLA - OLA DISPATCH PROGRESS MONITOR INTERVAL
BBOO0179I INTERVAL - ALL DISPATCH PROGRESS MONITOR INTERVALS
BBOO0179I DUMP_ACTION - DISPATCH PROGRESS MONITOR DUMP ACTION
BBOO0179I CLEAR_ALL - CLEAR ALL DISPATCH PROGRESS MONITOR SETTINGS
BBOO0179I RESET_ALL - RESET ALL DISPATCH PROGRESS MONITOR SETTINGS
BBOO0179I CRA - MDB CRA DISPATCH PROGRESS MONITOR INTERVAL
BBOO0211I 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]