This topic applies only on the z/OS operating system.

Modify command

Use the modify command from the MVS console to dynamically modify product operations.

You can use the modify command to display status of various server components and activities, including:
  • Active controllers
  • Trace settings
  • Servants
  • Sessions
  • Java Virtual Machine (JVM) Heap
  • Java trace

Use the following format when entering the modify command.

f <server>, options

The first argument is required. server is the short name for the server for which the modify command is directed.

Parameters

The following options are valid for the modify command:

CANCEL
Used to cancel a server.

You can specify the following options:

ARMRESTART
Specify this option if you are using ARM and want an Application Response Management (ARM) agent to restart the server after it terminates. If you do not specify the ARMRESTART option on the CANCEL parameter, then ARM does not restart the server.
HELP
Get help for the CANCEL syntax.
Avoid trouble: You cannot use the CANCEL parameter to cancel a cluster from the MVS console. Instead, you must cancel each of the servers that make up the cluster.gotcha
TRACEALL=n
Used to establish a general trace level for the server.
The following are valid trace levels. Typically, you should 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 can be handled reasonably. gotcha
TRACEBASIC=n
Used to specify the product components for which you want to switch on a basic level of tracing.
This command has the ability to override a different tracing level established by TRACEALL for those components.
Note: Do not change this variable unless directed by IBM service personnel.

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 OS/390 Wrappers
A Daemon
E Security
F Externalization
J JRAS (internal tracing that should only be used under direction from IBM support)
L J2EE
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 inTRACEALL. The selected components are identified by their component IDs, which are the same IDs as are 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 by IBM service personnel.gotcha
TRACESPECIFIC=xxyyyzzz
Used to specify tracing overrides for specific product trace points.
Trace points are specified by 8-digit, hexadecimal numbers. To specify more than one trace point, use parentheses and separate the numbers with commas. You can also specify an environment variable name by enclosing the name in single quotes. The value of the environment variable will be handled as if you had specified that value on the TRACESPECIFIC parameter.
Avoid trouble: Do not use TRACESPECIFIC unless directed by IBM service personnel.gotcha
TRACE_EXCLUDE_SPECIFIC=xxyyyzzz
Used to specify product trace points to exclude.
Trace points to exclude are specified by 8-digit, hexadecimal numbers. To specify more than one trace point, use parentheses and separate the numbers with commas. You can also specify an environment variable name by enclosing the name in single quotes. The value of the environment variable is handled as if you specify that value on the TRACE_EXCLUDE_SPECIFIC parameter. You can use the TRACE_EXCLUDE_SPECIFIC parameter as a mask to turn off otherwise-on traces. For example, use the TRACESPECIFIC command 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 unless directed by IBM service personnel.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 Select whether or not 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
Used to modify the Java trace string.

The product tracing of registered trace components conforms to the tracing rules as specified in the Sun Java Trace Specification. Specifiying *=all=enabled enables all types of tracing for all registered trace components.

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 command if you want to shut down the communication listeners and purge any pending work in the work registry.
RESUMELISTENERS
Used to restart the communication listeners after issuing a PAUSELISTENERS parameter. This parameter also allows work to be accepted into the server.
DISPLAY | 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 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 you may use with the modify display trace Java command.
    • HELP displays a list of all the keywords you may 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 you may use with the modify display Javaheap command.
  • SESSIONS displays session information for the server. You can further modify this command with one of the following options:
    • LISTENERS displays the listening port numbers for each protocol. This is the default, so the f server,sessions and the f server,sessions,listeners commands would have the same outcome.
    • SERVER displays the number of sessions in use for each protocol on the server. You can further modify this command with one of the following options:
      • TCPIIOP displays the number of TCP/IP IIOP sessions active on the server. You can further modify this command with one of the following options:
        • LIST List the server session information for the TCP/IP IIOP protocol. The LIST parameter is also available with the other session protocol display commands.
        • HELP displays a list of all the keywords you may use with the modify display session server tcpipiiop command. The HELP option is also available with the other session protocol display commands.
      • LOCALIIOP displays the number of LOCALIIOP sessions that are active on the server.
      • SSLIIOP displays the number of SSLIIOP sessions that are active on the server.
      • HTTP displays the number of HTTP sessions that are active on the server.
      • HTTPS displays the number of HTTPS sessions that are active on the server.
      • HELP displays a list of all of the keywords that you can use with the modify display session server command.
    • HELP displays help for the modify display sessions command.
  • HELP displays a list of all the keywords you may use with the modify command.

Example

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

Example 1: The following command will cancel the bbo6acr server:
f bbo6acr,cancel
Example 2: The following command will cancel the bbo6acr server and instruct ARM to restart it after it terminates:
f bbo6acr,cancel,armrestart



Subtopics
Example: Establishing a general level of trace
Example: Setting basic and detailed trace levels
Example: Setting specific trace points
Example: Excluding specific trace points
Example: Resetting to the initial trace settings
Example: Turning off tracing
Example: Sending the trace to sysprint
Example: Getting help for the modify command
Example: Modifying the Java trace string
Related tasks
Using MVS console commands
Related reference
[z/OS] SVC dumps
Reference topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 10:43:27 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v602web&product=was-nd-mp&topic=rxml_mvsmodify
File name: rxml_mvsmodify.html