- DISABLEFAILOVER,'<JNDI Name>'
- Used to manually disable resource failover support for the resource
identified by the supplied JNDI name. The supplied JNDI name identifies
the primary resource, and it must be surrounded by single quotes to
preserve its case.
- ENABLEFAILOVER,'<JNDI Name>'
- Used to manually enable resource failover support for the resource
identified by the supplied JNDI name. The supplied JNDI name identifies
the primary resource, and it must be surrounded by single quotes to
preserve its case.
- FAILOVER,'<JNDI Name>'
- Used to manually route requests that are destined for the primary
resource to its configured alternate resource. The supplied JNDI name
identifies the primary resource, and it must be surrounded by single quotes
to preserve its case. To failback requests to the primary resource,
issue the modify command with the parameter, FAILBACK,'<JNDI
name>'.
- FAILBACK,'<JNDI Name>'
- Used to manually route requests to the configured primary resource
that is identified by the supplied JNDI name. The supplied JNDI name
identifies the primary resource, and it must be surrounded by single quotes
to preserve its case. This command automatically enables automatic
failover. If automatic failover is not wanted after failback, issue
the modify command with the parameter, DISABLEFAILOVER,'<JNDI
Name>'.
Attention: The JNDI name input
is case sensitive.
- CANCEL
- Used to cancel the specified server.
You can specify the following
options for the CANCEL parameter:
- ARMRESTART
- Specifies whether you are using the application response management
(ARM) agent and want ARM to restart the server after it terminates.
If you do not specify the ARMRESTART option on the CANCEL parameter,
ARM does not restart the server.
- HELP
- Specifies that you want to see the help information that describes
the CANCEL syntax.
Avoid trouble: You cannot use
the
CANCEL parameter to cancel a cluster from
the MVS console. You must individually cancel each of the servers
that make up the cluster.
gotcha
- DPM,[IIOP=[nnn] | HTTP=[nnn] | HTTPS=[nnn]
| MDB=[nnn] |SIP=[nnn] | SIPS=nnn] |OLA=nnn] | INTERVAL=[nnn] | dump_action={SVCDUMP|JAVACORE|HEAPDUMP|TRACEBACK|JAVATDUMP|NONE|RESET}
| clear_all | reset_all]
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.
- HEAPDUMP
- Used to generate a JVM heap dump for the controller, and for all
the servants that are associated with that controller.
- JAVACORE
- Used to generate a JVM core dump for the controller, and for all
the servants that are associated with that controller.
- JAVATDUMP
- Used to generate a JVM-initiated TDUMP for all the servant address
spaces. You can also use the JAVA_DUMP_TDUMP_PATTERN native environment
variable to specify the TDUMP data set name.
- MSGROUTE,{ERRORLOG|HARDCOPY|CONSOLE|NONE}{[=xxx][,RESET][,CLEAR]}
- Used to dynamically alter the output location of message IDs.
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 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
RESET with
ERRORLOG,
HARDCOPY, CONSOLE or
NONE means that the
messages that are routed or suppressed come form the
was.env file
instead of the MSGROUTE modify command.
- Specifying RESET with ERRORLOG routes
messages specified on the ras_message_routing_errorlog environment
variable to the error log instead of the default location.
- Specifying RESET with HARDCOPY routes
the messages specified on the ras_message_routing_hardcopy environment
variable to the SYSLOG system log instead of the default location.
- Specifying RESET with CONSOLE routes
the messages specified on the ras_message_routing_console environment
variable to the MVS operator console instead of the default location.
- Specifying RESET with NONE suppresses
the routing of messages specified on the ras_message_routing_hardcopy
environment variable.
Specifying
CLEAR with
ERRORLOG,
HARDCOPY, CONSOLE or
NONE means that the
messages are routed to a default location or are no longer suppressed.
- Specifying CLEAR with ERRORLOG routes
messages to the default location instead of the error log.
- Specifying CLEAR with HARDCOPY routes
the messages to the default location instead of to the SYSLOG system
log.
- Specifying CLEAR with CONSOLE routes
the messages to the default location instead of to the MVS operator
console.
- Specifying CLEAR with NONE cancels
the suppression of messages.
- RECLASSIFY[,FILE=['/path/to/file.xml']]
- Used to dynamically reload the workload classification document
without having to restart the server. The reloaded workload classification
settings take effect immediately.
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.
Attention: If the new workload
classification file cannot be loaded, then the application server
discards the reloaded classification settings. The application server
continues to run with the classification settings in effect before the reclassify
modify command being issued.
Tip: Whenever the workload
classification file loads successfully, the application server issues
to the system log, SYSLOG, a message like the following message. The
message is also displayed on the operator console in response to the DISPLAY,WORK,CLINFO display
command.
BBOJ0129I: The /tmp/wlm4.class.xml workload classification file
was loaded at 2009/07/14 19:33:35.297 (GMT)
- STACKTRACE
- Used to log the Java stack
traceback for all Java threads
in the server to the error log.
- SMF,REQUEST,{ON|OFF|RESET}
- Used to control the creation of SMF 120-9 records.
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.
- SMF,REQUEST,ASYNC,{ON|OFF|RESET}
- Used in the collection of data for the Formatted ASYNC Section
of the SMF 120-9 record whenever that record is created.
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.
- SMF,REQUEST,CPU,{ON|OFF|RESET}
- Used in the collection of data for the CPU Usage Breakdown Section
of the SMF 120-9 record whenever that record is created.
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.
- SMF,REQUEST,SECURITY,{ON|OFF|RESET}
- Used in the collection of data for the Security Data Section of
the SMF 120-9 record whenever that record is created.
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.
- SMF,REQUEST,TIMESTAMPS,{ON|OFF|RESET}
- Used in the collection of data for the Formatted Timestamps Section
of the SMF 120-9 record whenever that record is created.
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.
- SMF,OUTBOUND,ON
- Used to turn on the creation of SMF 120-10 records.
- SMF,OUTBOUND,OFF
- Used to turn off the creation of SMF 120-10 records..
- SMF,OUTBOUND,RESET
- Used to have the creation of SMF 120-10 records controlled by
the value specified on the server_SMF_outbound_enabled environment
variable.
- TIMEOUT_DELAY=n
- Used to dynamically alter the timeout delay option variable, control_region_timeout_delay,
to n seconds. This modify command is used with
the TIMEOUTDUMPACTION modify command to set a timeout
delay that enables the specified dump action, such as JAVACORE, to
complete when a timeout occurs. The dump actions specified on the TIMEOUTDUMPACTION
modify command require a timeout delay that enables the
servant to complete the dump action before the servant terminates.
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.
- TIMEOUTDUMPACTION=n
- Used to indicate which of the following actions is performed whenever
a timeout occurs for work that has been dispatched to a servant when
the control_region_timeout_delay property is set to a non-zero value:
- TIMEOUTDUMPACTIONSESSION=n
- Used to indicate which of the following actions is performed whenever
a timeout occurs for an HTTP, HTTPS, SIP, or SIPS request that has
been dispatched to a servant, and the corresponding recovery property
is set to SESSION:
- If NONE, or none is
specified, no dump is taken.
- If JAVACORE or javacore is
specified, a Java core dump
is taken.
- If SVCDUMP or svcdump is
specified, an SVC dump is taken.
- If JAVATDUMP or javatdump is
specified, a JVM-initiated TDUMP is taken
Following is a list of the corresponding recovery properties:
- protocol_http_timeout_output_recovery
- protocol_https_timeout_output_recovery
- protocol_sip_timeout_output_recovery
- protocol_sips_timeout_output_recovery
- TRACEALL=n
- Used to establish a general trace level for the server.
The following
values are valid trace levels. Typically, you specify a value of
1.
- 0: no tracing is performed
- 1: tracing is performed when an exception
occurs
- 2: basic tracing is performed
- 3: detailed tracing for all components
is performed.
Avoid trouble: Be careful when using a
level of 3 because this level of tracing might yield more data than
is practical for you to review.
gotcha
- TRACEBASIC=n
- Used to specify the product components for which you want to turn
on a basic level of tracing.
This command can override a different
tracing level established by
TRACEALL for those
components.
Avoid trouble: Do not change this
variable unless directed to do so by IBM
® Support.
gotcha
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 |
- TRACEDETAIL=n
- Used to specify the product components for which you want to turn
on a detailed level of tracing.
This command activates the most
detailed tracing for the specified product components and overrides
different settings in
TRACEALL. The selected components
are identified by their component IDs, which are the same IDs as the
ones listed for the
TRACEBASIC parameter. Subcomponents,
specified by numbers, receive detailed traces. Other parts of the
product receive tracing as specified on the
TRACEALL parameter.
Avoid trouble: Do not change this variable unless
directed to do so by IBM Support.
gotcha
- TRACESPECIFIC=xxyyyzzz
- Used to specify tracing overrides for specific product trace points.
Trace
points are specified by eight-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 quotation marks. The value of the environment
variable is processed as if you had specified that value on the
TRACESPECIFIC parameter.
Avoid trouble: Do not use
TRACESPECIFIC unless
directed by IBM Support.
gotcha
- TRACE_EXCLUDE_SPECIFIC=xxyyyzzz
- Used to specify product trace points to exclude.
Trace points
to exclude are specified by eight-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 quotation marks. The value of the environment
variable is processed as if you had specified that value on the TRACE_EXCLUDE_SPECIFIC
parameter. You can use the TRACE_EXCLUDE_SPECIFIC parameter as a mask
to turn off traces that are currently turned on. For example, use
the TRACESPECIFIC parameter to turn on tracing for a whole part of
the product, and then use the TRACE_EXCLUDE_SPECIFIC parameter to
turn off one trace within that part of the product.
Avoid trouble: Do not use TRACE_EXCLUDE_SPECIFIC
parameter unless you are directed to do so by IBM Support.
gotcha
- TRACEINIT
- Used to reset to the initial trace settings.
- TRACENONE
- Used to turn off all trace settings.
- TRACETOSYSPRINT={YES|NO}
- Used to select whether to send the trace to SYSPRINT.
Specifying YES sends
the trace to SYSPRINT, and specifying NO stops the
sending of the trace to SYSPRINT.
- TRACETOTRCFILE={YES|NO}
- Used to specify whether to direct the trace to the TRCFILE DD
card.
Specifying YES sends the trace to the TRCFILE
DD card, and specifying NO stops the sending of the
trace to the TRCFILE DD card.
- TRACEJAVA
- Modify the Java trace string.
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.
- TRACERECORD,{ON|OFF|RESET}
- Used to control the writing of trace records. The parameter is
used with the classification_only_trace attribute defined in the workload
classification file.
Specifying ON causes trace
records to be written based on the current trace specification. Any
classification_only_trace attributes are ignored.
Specifying
OFF prevents
trace records from being written.
CAUTION:
Trace records
based on the current trace specification or produced as part of normal
runtime processing are not written.
Specifying
RESET causes
trace records to be written for the current trace specification as
follows:
- If no classification_only_trace attributes are defined, then trace
records are written for all processing threads. This situation is
functionally equivalent to setting TRACERECORD to ON.
- If one or more classification_only_trace attributes are defined,
then trace records are only written for processing threads whose classification
contains a classification_only_trace attribute of 1.
The default value is RESET.
- HELP
- Used to display a list of all the keywords that you can use with
the modify command.
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.
- PAUSELISTENERS
- Used to prevent work from being accepted into the server. Use
this parameter to shut down the communication listeners and purge
any pending work in the work registry.
- WLM_MIN_MAX=min,max
- Used to dynamically modify the minimum and maximum number of servants
settings (wlm_minimumSRCount and wlm_maximumSRCount). WLM dynamically
adjusts the current number of active servants to fit within the new
constraints. The new settings do not necessarily take effect immediately;
WLM works toward the new minimum and maximum targets as quickly as
possible, considering factors such as resource availability and workload.
Avoid trouble: The
WLM_MIN_MAX command
is ignored for a server that is configured with a single server dynamic
application environment, that is the wlm_dynapplenv_single_server
property is set to 1.
gotcha
- RESUMELISTENERS
- Used to restart the communication listeners after issuing a modify command
that includes the PAUSELISTENERS parameter. This parameter allows
new work to be accepted into the server.
- DISPLAY
- Used to display the name of the server, the system name where
the server is running, and the current code level.
You can specify
the following options for this parameter:
- SERVERS displays the name of the server at which
the command is directed, the system name, and the code level for each
active server in the sysplex that is in the same cell.
- SERVANTS: displays a list of the address space
identifiers (ASIDs) of the servants that are attached to the server
against which you issued the display command.
- TRACE displays trace information for a server
controller. You can further modify this command with one of the following
options:
- SRS displays trace information for all servants,
one at a time.
- ALL displays trace information for the controller
and all servants one at a time.
- JAVA displays the Java trace
string settings for a server controller. You can further modify this
command with one of the following options:
- SRS displays Java trace
information for all servants, one at a time.
- ALL displays Java trace
information for the controller and all servants one at a time.
- HELP displays a list of all the keywords that
you can use with the modify display trace Java command.
- HELP displays a list of all the keywords that
you can use with the modify display trace command.
- JVMHEAP displays the JVM heap information for
a server controller. You can further modify this command with one
of the following options:
- SRS displays the JVM heap information for all
servants, one at a time.
- ALL displays the JVM heap information for the
controller and all servants, one at a time.
- HELP displays a list of all the keywords that
you can use with the modify display Javaheap command.
- LISTENERS displays the connection instance name,
associated IP address, and listening port number. The associated IP
address can display an asterisk (*) as a wildcard.
- CONNECTIONS displays each connection instance
name and a count of the number of connections. Each connection instance
is on a separate line. You can further modify this command with one
of the following options:
- NAME='name' displays the number
of associated connections for the specified connection instance 'name'.
If the connection name is located but has zero connections, the command
returns a count of zero. If the connection name is not found, the
command returns an error message.
- LIST displays the remote host information for
all the connections of each of the connection instances. If a connection
instance name has no connections, the command returns only the connection
instance name.
- LIST, NAME='name' displays
the remote host information for all connections of a specified connection
instance 'name'.
- HELP displays a list of all the keywords that
you can use with the modify command.
- ERRLOG displays the last 10 entries in the error
log. You can further modify this option with one of the following
options:
- SRS displays the last 10 entries in the error
log for all servants, one at a time.
- HELP displays a list of all the keywords you
can use with the modify display error log command.
- MODE displays the run bit mode.
- MSGROUTE displays the list of messages for all
routing locations and for messages to suppress. Routing locations
can be the error log, the system log, or the MVS operator console.
- ERRORLOG displays a list of messages to route
to the error log.
- HARDCOPY displays a list of messages to route
to the SYSLOG system log, also known as hardcopy.
- CONSOLE displays a list of messages to route
to the MVS operator console.
- NONE displays a list of messages to suppress.
- SMF displays the status of SMF 120-9 record creation
for a server.
ASYNC displays the status
of SMF 120-9 record creation for asynchronous work on all servants,
one servant at a time.
HELP displays a list of
all the keywords you can use with the modify display SMF command.
- WORK displays the work element counts for the
server. You can further modify this option with one of the following
options:
ASYNCSERVLET displays the
total number of asynchronous servlet requests and the current number
of asynchronous servlet requests being processed. The total number
of asynchronous servlet requests consists of only requests made since
the latest start or restart of the entire server. However, the total
can decrease if one or more of the servants has been stopped or restarted.
- SRS displays for each servant the total number
of asynchronous servlet requests and the current number of asynchronous
servlet requests being processed. The total number is the number of
asynchronous servlet requests since the last start or restart of the
servant.
- HELP displays a list of all the keywords you
can use with the modify display work asyncservlets command.
- EJB displays Enterprise JavaBeans (EJB) request count information.
You can modify this option with one of the following options:
- SRS displays EJB request count information for
all servants, one at a time.
- HELP displays a list of all the keywords you
can use with the modify display work EJB command.
- SERVLET displays servlet request count information.
You can modify this option with one of the following options:
- SRS displays servlet request count information
for all servants, one at a time.
- HELP displays a list of all the keywords you
can use with the modify display work servlet command.
- MDB displays message-driven bean (MDB) request
count information. You can further modify this command with one of
the following options:
- SRS displays MDB request count information for
all servants, one at a time.
- HELP displays a list of all the keywords you
can use with the modify display work MDB command.
- SIP displays Session Initiation Protocol (SIP)
request count information. You can modify this option with one of
the following options:
- SRS displays SIP request count information for
all servants, one at a time.
- HELP displays a list of all the keywords you
can use with the modify display work SIP command.
- SUMMARY displays summary request count information.
- SRS displays summary request count information
for all servants, one at a time.
- HELP displays a list of all the keywords you
can use with the modify display work summary command.
- ALL displays all request count information.
- SRS displays all request count information for
all servants, one at a time.
- STATS displays all detailed statistics.
- HELP displays a list of all the keywords you
can use with the modify display work all command.
- CLINFO displays work classification information.
- HELP displays a list of all the keywords you
can use with the modify display work command.
- OLA displays inbound Optimized Local Adapter
(OLA) requests driven by services BBOA1INV and BBOA1SRQ. You can
further modify this command with one of the following options:
- SRS displays OLA request count information for
all servants, one at a time.
- HELP displays a list of all the keywords you
can use with the modify display work all command.
- Fast Response Cache Accelerator (FRCA). Display FRCA cache statistics
as follows:
- f <servername>,display,frca
- f <servername>,display,frca,content
- f <servername>,display,frca,stats
- ADAPTER
- STATUS
Displays the status of the optimized local
adapters component.
- REGISTRATIONS
Displays a list of optimized local adapters
clients connected to this server.
- DAEMONRGES
Displays a list of optimized local adapters
clients connected to any server in this daemon group.
- SEARCHRGES
Displays a list of optimized local adapters
clients connected to any server in this daemon group, matching search
criteria.