(ZOS) Modify command

We can issue the modify command from the MVS console to dynamically modify product operations.

Use the modify command to display the status of various server components and activities, including the following components:

• Active controllers
• Trace settings
• Servants
• Sessions
• JVM heap
• Java trace

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.

Parameters

The following parameters are valid for the modify command:

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>'.

The JNDI name input is case sensitive.

CANCEL

Used to cancel the specified server.

We can specify the following options for the CANCEL parameter:

ARMRESTART

Specifies whether we are using the application response management (ARM) agent and want ARM to restart the server after it terminates. If we do not specify the ARMRESTART option on the CANCEL parameter, ARM does not restart the server.

HELP

To see the help information that describes the CANCEL syntax.

We cannot use the CANCEL parameter to cancel a cluster from the MVS console. We must individually cancel each of the servers that make up the cluster.

DPM,[IIOP=nnn | HTTP=nnn | HTTPS=nnn | MDB=nnn | SIP=nnn | CRA=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.

Specify 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 associated with that controller.

JAVACORE

Used to generate a JVM core dump for the controller, and for all the servants associated with that controller.

JAVATDUMP

Used to generate a JVM-initiated TDUMP for all the servant address spaces. We can also use the JAVA_DUMP_TDUMP_PATTERN native environment variable to specify the TDUMP data set name.

JAVAOOM,[INTERVAL=nnn | ACTION=xxx | RESET]

Used to dynamically alter the diagnostic action taken if a JVM out-of-memory condition occurs in this server. It is also used to dynamically alter the time interval within which the diagnostic action is repeated.

Specify 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.

Specify ACTION sets the diagnostic action 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:

NONE

No diagnostic action is performed.

WTO

A BBOO0404E error message is written to hardcopy.

SVCDUMP

An SVCDUMP of the affected address space is taken, with minor code C9C2704B.

Specify RESET Resets the diagnostic action and interval to the values specified for the ras_java_oom_action and ras_java_oom_interval environment variables.

MSGROUTE,{ERRORLOG|HARDCOPY|CONSOLE|COPYERRORLOG|COPYHARDCOPY|COPYCONSOLE|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 we 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 we 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.

Specify ERRORLOG routes the messages to the error log instead of the default location.

Specify HARDCOPY routes the messages to the SYSLOG system log, also known as hardcopy, instead of the default location.

Specify 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.

Specify COPYHARDCOPY copies the messages to the SYSLOG system log, also known as hardcopy, as well as the default location

Specify COPYCONSOLE copies the messages to the MVS operator console as well as the default location.

Specify 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.

Specify RESET with ERRORLOG, HARDCOPY, CONSOLE, COPYERRORLOG,COPYHARDCOPY,COPYCONSOLE or NONE means that the messages that are routed or suppressed come form the was.env file instead of the MSGROUTE modify command.

• Specify RESET with ERRORLOG routes messages specified on the ras_message_routing_errorlog environment variable to the error log instead of the default location.

• Specify 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.

• Specify 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.

• Specify RESET with COPYERRORLOG copies messages specified on the ras_message_routing_copy_errorlog environment variable to the error log as well as the default location.

• Specify RESET with COPYHARDCOPY copies the messages specified on the ras_message_routing_copy_hardcopy environment variable to the SYSLOG system log as well as the default location.

• Specify RESET with COPYCONSOLE copies the messages specified on the ras_message_routing_copy_console environment variable to the MVS operator console as well as the default location.

• Specify RESET with NONE suppresses the routing of messages specified on the ras_message_routing_hardcopy environment variable.

Specify CLEAR with ERRORLOG, HARDCOPY, CONSOLE, COPYERRORLOG,COPYHARDCOPY,COPYCONSOLE or NONE means that the messages are routed to a default location or are no longer suppressed.

• Specify CLEAR with ERRORLOG, HARDCOPY, CONSOLE, COPYERRORLOG, COPYHARDCOPY, COPYCONSOLE or NONE means that the messages are routed to a default location or are no longer suppressed.

• Specify CLEAR with ERRORLOG or COPYERRORLOG routes messages to the default location instead of the error log.

• Specify CLEAR with HARDCOPY or COPYERRORLOG routes the messages to the default location instead of to the SYSLOG system log.

• Specify CLEAR with CONSOLE or COPYCONSOLE routes the messages to the default location instead of to the MVS operator console.

• Specify 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.

Specify RECLASSIFY performs reclassification using the workload classification file specified on the wlm_classification_file variable.

Specify 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.

Specify 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.

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)

ROLL_LOGS

Used to reissue a redirect of servant output logs to the USS file system. A new set of output log files will be created under the same output directory, and older log files will be preserved. Messages will be written to the end of previous logs and to the beginning of new logs, thereby creating a logical link between the files.

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.

Specify ON turns on the creation of SMF 120-9 records.

Specify OFF turns off the creation of SMF 120-9 records.

Specify 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.

Specify ON turns on the collection of the data.

Specify OFF turns off the collection of the data. When this value is specified, records created have zeros for this section in the location triplets at the top of the record.

Specify 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.

Specify ON turns on the collection of the data.

Specify OFF turns off the collection of the data. When this value is specified, records created have zeros for this section in the location triplets at the top of the record.

Specify 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.

Specify ON turns on the collection of the data.

Specify OFF turns off the collection of the data. When this value is specified, records created have zeros for this section in the location triplets at the top of the record.

Specify 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.

Specify ON turns on the collection of the data.

Specify OFF turns off the collection of the data. When this value is specified, records created have zeros for this section in the location triplets at the top of the record.

Specify 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, we 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:

• 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.

  The control_region_timeout_delay property must be configured to a length of time that is long enough for the servant to collect the JAVATDUMP before the controller terminates the servant. The TIMEOUT_DELAY modify command can be used to dynamically change the value of the control_region_timeout_delay property.

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, we 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.

Be careful when using a level of 3 because this level of tracing might yield more data than is practical for you to review.

TRACEBASIC=n

Used to specify the product components for which we want to turn on a basic level of tracing.

This command can override a different tracing level established by TRACEALL for those components.

Do not change this variable unless directed to do so by IBM Support..

The following table includes the values that we can specify for this parameter. We 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 we 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 inTRACEALL. 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.

Do not change this variable unless directed to do so by IBM Support.

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. We 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.

Do not use TRACESPECIFIC unless directed by IBM Support.

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. We 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. 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.

Do not use TRACE_EXCLUDE_SPECIFIC parameter unless we are directed to do so by IBM Support.

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.

Specify 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.

Specify 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.

Specify ON causes trace records to be written based on the current trace specification. Any classification_only_trace attributes are ignored.

Specify 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.

Specify 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 is RESET.

HELP

Used to display a list of all the keywords we can use with the modify command.

We can also use the HELP parameter after the CANCEL, and DISPLAY parameters to display lists of all the keywords we can use with either of these parameters.

PAUSELISTENERS

Used to prevent work from being accepted into the server. Shut down the communication listeners and purge any pending work in the work registry.

The MODIFY server,PAUSELISTENERS command stops the controller from listening on all ports except IIOP (ORB_TCP_SECURE and ORB_TCP_LISTENER). For IIOP, when this modify command is issued, the daemon stops sending requests to the IIOP transport channels. However, if we are running client applications that do caching, such as bean caching, it is possible for requests from these applications to be sent directly to the open IIOP port. This situation might occur because the IIOP listeners start early in the server startup process, thereby possibly opening the IIOP port before this modify command is issued.

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.

The WLM_MIN_MAX command is ignored for a server configured with a single server dynamic application environment, that is the wlm_dynapplenv_single_server property is set to 1.

WORKERTHREADMAX=n

Used to increase the controller region worker thread pool maximum. The value specified on the modify command overrides the value specified for the control_region_thread_pool_maximum_size environment variable. The maximum can only be increased. Requests to decrease the maximum will be rejected. When specifying a maximum ensure that there will be enough resources available to support the specified maximum. An example of a resource to consider is the JVM heap size.

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.

We 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 we issued the display command.
• TRACE displays trace information for a server controller. We 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. We 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 we can use with the modify display trace Java command.

  • HELP displays a list of all the keywords we can use with the modify display trace command.

• JVMHEAP displays the JVM heap information for a server controller. We 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 we 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. We 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 we can use with the modify command.
• ERRLOG displays the last 10 entries in the error log. We 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 we 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 we can use with the modify display SMF command.

• WORK displays the work element counts for the server. We can further modify this option with one of the following options:
  • CRA displays CRA message-driven bean (MDB) request count information. We can further modify this command with one of the following options:
    • SRS displays CRA request count information for all servants, one at a time.
    • HELP displays a list of all the keywords we can use with the modify display work CRA command.

  • 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 we can use with the modify display work asyncservlets command.

  • EJB displays EJB request count information. We 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 we can use with the modify display work EJB command.

  • SERVLET displays servlet request count information. We 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 we can use with the modify display work servlet command.

  • MDB displays message-driven bean (MDB) request count information. We 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 we can use with the modify display work MDB command.

  • SIP displays SIP request count information. We 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 we 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 we 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 we can use with the modify display work all command.

  • CLINFO displays work classification information.
  • HELP displays a list of all the keywords we can use with the modify display work command.
  • OLA displays inbound Optimized Local Adapter (OLA) requests driven by services BBOA1INV and BBOA1SRQ. We 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 we 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.

ASIDX=

Add ASIDX= after the modify command with the appropriate ASID (in hex) of a servant region we want to dump.

For example:

MODIFY server,JAVACORE,ASIDX=F4

In this example, the command takes a JAVACORE of the servant region whose (hex) ASID is 'F4'.

Example: Disabling fail over

Example 1: The following command disables fail over for the primary resource identified by jdbc/MySampleDataSource on the server bbos001:

f bbos001,DISABLEFAILOVER,'jdbc/MySampleDataSource'

Example: Canceling application clusters and servers with the modify command

We cannot cancel a cluster from the MVS console. Instead, we must cancel each of the servers that make up the cluster.

Example 1: The following command cancels the bbo6acr server:

f bbo6acr,cancel

Example 2: The following command cancels the bbo6acr server and instructs ARM to restart the bbo6acr server after the terminate process completes:

f bbo6acr,cancel,armrestart

Example: Establishing a general level of trace using scripting

To establish a general trace level for the server, use the following command:

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).

Example: The following command turns on exception level tracing for the bbo6acr server:

f bbo6acr,traceall=1

Here is a sample display:

f bbo6acr,traceall=1
BBOO0211I MODIFY COMMAND TRACEALL=1 COMPLETED SUCCESSFULLY

Example: Setting basic and detailed trace levels for the WebSphere z/OS components

Use the following command:

f server,tracebasic=(n,...)

Example 1: The following command turns on a basic level of tracing for the Daemon component on server bbo6acr:

f bbo6acr,tracebasic=a

Here is a sample display:

f bbo6acr,TRACEBASIC=A
BBOO0211I MODIFY COMMAND TRACEBASIC=A COMPLETED SUCCESSFULLY

To specify the WebSphere for z/OS components for which we want to switch on a detailed level of tracing use the following command:

f server,tracedetail=(n,...)

Example 2: The following command turns on a detailed level of tracing for security on server bbo6acr:

f bbo6acr,tracedetail=e

Here is a sample display:

f bbo6acr,TRACEDETAIL=E
BBOO0211I MODIFY COMMAND TRACEDETAIL=E COMPLETED SUCCESSFULLY

Example: Setting specific trace points using scripting

To set specific trace points.

f server,tracespecific=n | (n,...)

Example 1: The following command turns on the specific trace point 04006001:

f bbo6acr,tracespecific=04006001

Example 2: The following command turns on the specific trace points 04006001 and 04006027:

f bbo6acr,tracespecific=(04006001,04006027)

Example 3: The following command turns on the specific trace points set in the environment variable tracepoints:

f bbo6acr,tracespecific='tracepoints'

Example: Excluding specific trace points using scripting

To exclude specific trace points.

f server,trace_exclude_specific=n | (n,...)

Example: The tracespecific command turns on tracing for a whole part and then the trace_exclude_specific turns off tracing for the point 04006031 within that part:

f bbo6acr,tracespecific=04006000

f bbo6acr,trace_exclude_specific=04006031

Example: Resetting to the initial trace settings using scripting

To reset to the initial trace settings use the following command:

f server,traceinit

Example: Command to turn off tracing using a command line

To turn off tracing.

f server,tracenone

Example: Sending the trace to SYSPRINT using scripting

To send the trace to SYSPRINT use the following command:

f server,tracetosysprint=yes

To stop sending the trace to SYSPRINT.

f server,tracetosysprint=no

Example: Canceling application clusters and servers with the modify command

This example demonstrates how to cancel application clusters and servers with the modify command.

Before you begin: We cannot cancel a cluster from the MVS console. Instead, we must cancel each of the servers that make up the cluster.

Example 1: The following command cancels the bbo6acr server:

f bbo6acr,cancel

Example 2: The following command cancels the bbo6acr server and instructs ARM to restart it after it terminates:

f bbo6acr,cancel,armrestart

Example: Getting help for the modify command

We can get syntax help for the various levels of the modify command.

Example 1: Enter the following command to display a list of all the keywords we can use with the modify command:

f bbo6acr,help

The resulting output is like the following example:

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 

Example 2: Enter the following command to display a list of all the keywords we can use with the modify display command:

f bbo6acr,display,help

The resulting output is similar to the following example:

 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

Example 3: Enter the following command to display a list of all the keywords we can use with the modify timeoutdumpaction or modify timeoutdumpactionsession command:

f bbos001,timeoutdumpactionsession=help

The resulting output is like the following example:

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                   

Example 4: Enter the following command to display a list of all the keywords we can use with the modify display dpm command:

f bbos001,dpm,help                                                  

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 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 we 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        

Example: Modifying the Java trace string

This example shows how to use a console command to modify a Java trace string.

To modify the Java trace string.

f server, tracejava='trace specification'

Example: The following command enables all types of tracing for all registered trace components:

f bbo6acr,tracejava='*=all'

The quotation marks are a required part of the syntax.

Example: Modifying the diagnostic action taken if a JVM out-of-memory condition occurs

This example shows how to use a console command to modify the diagnostic action taken if a JVM out-of-memory condition occurs, use the following command:

f server,javaoom,[interval=xxx | action=xxx]

Example: The following command causes an SVCDUMP of the affected address space to be taken, with minor code C9C2704B, if a JVM out-of-memory condition occurs. This command also prevents additional diagnostic actions from occurring until a time interval of 1200 seconds ( 20 minutes) elapses.

f bbo6acr,,javaoom,[interval=1200 | action=svcdump]

The quotation marks are a required part of the syntax.

(ZOS) Use MVS console commands

(ZOS) Enable request-level Reliability Availability and Serviceability (RAS) granularity

(ZOS) SVC dumps