[z/OS]

Display command with examples

The display command is useful for obtaining data on a variety of processes.

You can use display commands to perform the following actions:

Display servants

To display servants, use the following command:
f server,display,servants
Example: The following command will display servants for the bbo6acr server:
f bbo6acr,display,servants
Here is a sample display:
F bbo6acr,DISPLAY,SERVANTS
BBOO0185I SERVER BBO5SR4/BBOASR4A HAS 1 SERVANT PROCESS (ASID: 0038x)
BBOO0188I END OF OUTPUT FOR COMMAND DISPLAY,SERVANTS

Display trace settings and Java string trace settings

To display the trace settings for a server instance, use the following command:
f server,display,trace
Example 1: The following command will display trace settings for the bbo6acr server:
f bbo6acr,display,trace
Here is a sample display:
F bbo6acr,DISPLAY,TRACE
BBOO0224I TRACE INFORMATION FOR SERVER BBO5SR4/BBOASR4A/STC00047
BBOO0197I LOCATION = SYSPRINT BUFFER
BBOO0197I AGGREGATE TRACE LEVEL = 1
BBOO0197I EXCEPTION TRACING = RAS(0), Common Utilities(1), COMM(3),
ORB(4), OTS(6), Shasta(7), z/OS Wrappers(9), Daemon(A), Security(E),
Externalization(F), JRAS(J), J2EE(L)
BBOO0197I BASIC TRACING =
BBOO0197I DETAILED TRACING =
BBOO0197I TRACE SPECIFIC = NONE SPECIFIED
BBOO0197I TRACE EXCLUDE SPECIFIC = NONE SPECIFIED
BBOO0225I TRACE INFORMATION FOR SERVER BBO5SR4/BBOASR4A/STC00047 COMPLETE
BBOO0188I END OF OUTPUT FOR COMMAND DISPLAY,TRACE
To display the Java™ trace string settings for a server, use the following command:
f server,display,trace,java
Example 2: The following command will display Java trace settings for the bbo6acr server:
f bbo6acr,display,trace,java
Here is a sample display:
F bbo6acr,DISPLAY,TRACE,JAVA
BBOO0196I TRACE INFORMATION FOR SERVER BBO5SR4/BBOASR4A
BBOJ0050I CTL(STC00047):*=all=disabled
BBOO0188I END OF OUTPUT FOR COMMAND DISPLAY,TRACE,JAVA
To display the Java trace information for all servants, one at a time.
f server,display,trace,java.srs
Example 3: The following command will display Java trace settings for the bbo6acr server:
f bbo6acr,display,trace,java,srs
Here is a sample display:
F bbo6acr,DISPLAY,TRACE,JAVA,SRS
BBOO0196I TRACE INFORMATION FOR SERVER BBO5SR4/BBOASR4A
BBOJ0050I SR(STC00048):*=all=disabled
BBOO0188I END OF OUTPUT FOR COMMAND DISPLAY,TRACE,JAVA,SRS
To display the Java trace information for the controller and all servants, one at a time.
f server,display,trace,java.all
Example 4: The following command will display Java trace settings for the controller and all servants:
f bbo6acr,display,trace,java,all
Here is a sample display:
F bbo6acr,DISPLAY,TRACE,JAVA,ALL
BBOO0196I TRACE INFORMATION FOR SERVER BBO5SR4/BBOASR4A
BBOJ0050I CTL(STC00047):*=all=disabled
BBOJ0050I SR(STC00048):*=all=disabled
BBOO0188I END OF OUTPUT FOR COMMAND DISPLAY,TRACE,JAVA,ALL

Display active replies

Displaying active replies from the MVS™ console allows you to observe system activity and determine if the system requires an operator response.

Issue the following command to display (list) all active replies:
d r,r

Display active address spaces

Use the display command to display active address spaces.

For example, use the display command to determine if the location service daemon is up:
Table 1. display command descriptions . The following table describes the display command.
Parameter Description
d a,l Displays a list of all address spaces.
d a,a Displays a list of all active address spaces.
d a,address-space-name Displays only the address space in which you are interested. This command is recommended over the first two because it does not yield such a lengthy list on a production system. Of course, you need to know the name of the address space for which you are looking.

Example: d a,bboasr1
d a,bbo* Displays a list of all active address spaces that start with BBO.

Display the status of address spaces registered for automatic restart management (ARM)

You can display the status of addresses registered with automatic restart management.

Complete the following steps to use automatic restart management (ARM) to display the status of ARM registered address spaces (including the address spaces of server instances) in the WebSphere® Application Server for z/OS® environment:

  1. Initialize all servers.
  2. Issue one or both of the following commands:
    • To display all registered address spaces (including the address spaces of server instances), issue the command:
      d xcf,armstatus,detail
    • To display the status of a particular server instance, use the display command and identify the job name. For example, to display the status of the Daemon server instance (job BBODMN), issue the following command:
      d  xcf,armstatus,jobname=bbodmn,detail

Display units of work (transactions) for the Information Management System

Complete the following steps to display units of work (transactions) for Information Management System (IMS):

  1. To display the status of a specific transaction, issue this command. The message ID is the replying IMS ready message number.
    message_id/dis tran trans-name
  2. To display the status of a specific program, issue the command:
    /dis prog program-name
  3. To display the number of Message Processing Regions (MPRs) that are currently active, issue the command:
    /display active region

Display JVM heap information

To display the JVM heap information for a server controller, use the following command:
f server,display,jvmheap
Example 1: The following command will display JVM heap information for the bbo6acr server:
f bbo6acr,display,jvmheap
Here is a sample display:
F bbo6acr,DISPLAY,JVMHEAP
BBOO0201I JVM HEAP INFORMATION FOR SERVER BBO5SR4/BBOASR4A/STC00047
BBOO0202I (STC00047) HEAP(MIDDLEWARE), COUNT(00000000), FREE STORAGE(
396FA70), TOTAL STORAGE( 7FFFA00)
BBOO0204I JVM HEAP INFORMATION FOR SERVER BBO5SR4/BBOASR4A/STC00047 COMPLETE
BBOO0188I END OF OUTPUT FOR COMMAND DISPLAY,JVMHEAP
To display the JVM heap information for all servants one at a time, use the following command:
f server,display,jvmheap,srs
Example 2: The following command will display JVM heap information for all servants in the bbo6acr server:
f bbo6acr,display,jvmheap,srs
Here is a sample display: 
F bbo6acr,DISPLAY,JVMHEAP,SRS
+BBOO0201I JVM HEAP INFORMATION FOR SERVER BBO5SR4/BBOASR4A/STC00048
+BBOO0202I (STC00048) HEAP(MIDDLEWARE), COUNT(00000001), FREE STORAGE(
 25F4030), TOTAL STORAGE( 7FFFA00)
+BBOO0204I JVM HEAP INFORMATION FOR SERVER BBO5SR4/BBOASR4A/STC00048 COMPLETE
BBOO0188I END OF OUTPUT FOR COMMAND DISPLAY,JVMHEAP,SRS
To display the JVM heap information for the controller and all servants of a server one at a time, use the following command:
f server,display,jvmheap,all
Example 3: The following command will display JVM heap information for the controller and all servants in the bbo6acr server:
f bbo6acr,display,jvmheap,all
Here is a sample display:
F bbo6acr,DISPLAY,JVMHEAP,ALL
BBOO0201I JVM HEAP INFORMATION FOR SERVER BBO5SR4/BBOASR4A/STC00047
BBOO0202I (STC00047) HEAP(MIDDLEWARE), COUNT(00000000), FREE STORAGE(
396FA70), TOTAL STORAGE( 7FFFA00)
BBOO0204I JVM HEAP INFORMATION FOR SERVER BBO5SR4/BBOASR4A/STC00047 COMPLETE
+BBOO0201I JVM HEAP INFORMATION FOR SERVER BBO5SR4/BBOASR4A/STC00048
+BBOO0202I (STC00048) HEAP(MIDDLEWARE), COUNT(00000001), FREE STORAGE(
 25F4030), TOTAL STORAGE( 7FFFA00)
+BBOO0204I JVM HEAP INFORMATION FOR SERVER BBO5SR4/BBOASR4A/STC00048 COMPLETE
BBOO0188I END OF OUTPUT FOR COMMAND DISPLAY,JVMHEAP,ALL

Display the status of a server

To display the status of a server, use the following command:
f server,display
Example: The following command will display status for the bbo6acr server:
f bbo6acr,display
Here is a sample display:
F bbo6acr,DISPLAY
BBOO0173I SERVER BBO5SR4/BBOASR4A ACTIVE ON SY1 AT LEVEL wd5xo03.
BBOO0188I END OF OUTPUT FOR COMMAND DISPLAY

Display the status of SMF 120-9 and SMF 120-10 record creation

The SMF display command displays the status of SMF 120-9 and SMF 120-10 record creation and whether the optional CPU usage, security information, or timestamp information for the record is collected.

The display,smf command also displays the following information:
  • When the last SMF 120-9 record was successfully or unsuccessfully created
  • When the last SMF 120-10 record was successfully or unsuccessfully created
  • How many SMF records were successfully and unsuccessfully created since the server started
  • The last non-zero return code from an attempt to write an SMF 120-9 record
  • The last non-zero return code from an attempt to write an SMF 120-10 record
To display the status of SMF 120-9 and SMF 120-10 record creation for a server, use the following command:
f server,display,smf
Example: The following command displays the status of SMF 120-9 and SMF 120-10 record creation for the bbo6acr server:
f bbo6acr,display,smf
Here is a sample display:
BBOO0344If
 SMF 120-9: ON, CPU USAGE: OFF, TIMESTAMPS: OFF, SECURITY INFO: OFF
BBOO0345I SMF 120-9: TIME OF LAST WRITE: 2008/02/20 13:38:44.003116, SUCCESSFUL 
          WRITES: 2, FAILED WRITES: 0
BBOO0346I SMF 120-9: LAST FAILED WRITE TIME: NEVER, RC: 0
BBOO0389I SMF 120-10: FORCED_ON                                      
BBOO0387I SMF 120-10: TIME OF LAST WRITE: 2011/06/06 19:29:03.416432,
          SUCCESSFUL WRITES: 14, FAILED WRITES: 0BBOO0388I 
BBOO0388I SMF 120-10: LAST FAILED WRITE TIME: NEVER, RC: 0BBOO0188I END OF OUTPUT FOR COMMAND DISPLAY,SMF
BBOO0188I END OF OUTPUT FOR COMMAND DISPLAY,SMF

Each of the SubType 9, CPU Usage, Timestamps, or Security Info sections of the message can have a value of ON, OFF, FORCED_ON, or FORCED_OFF. The ON or OFF values for a section indicate the setting of the corresponding server-wide custom property. If any values are FORCED_ON or FORCED_OFF, then an SMF modify command was issued. The SMF modify command overrides the SMF server-wide custom property and the SMF request-level RAS attribute.

Display the status of dispatch thread

You can display the status of each servant thread, on which there is currently a request dispatched, for all of the servants in a controller, or you can display this thread status for a particular servant within the controller. You can also display information about the dispatch thread for a particular request, the dispatch threads that have been handling the same request for a specific amount of time, or the dispatch threads for requests that have timed out.

To display the status of dispatch threads use the following command:
f server,display,threads,<parameters>

server is the short name for the server to which the this command is directed. This argument is required.

If you do not specify any parameters, all is used.

ALL
Used to display information about all of the requests that are currently dispatched in each servant that is associated with this controller.

You can specify the following options on the DISPLAY,THREADS,ALL command. If no option is specified, summary is used.

DETAILS
Specifies that you want to see the full details about each request.
SUMMARY
Specifies that, for each request, you only want to see the request ID, the ASID of the servant where the request was dispatched, the time the request was dispatched, and whether the request timed out.

Here is a sample display of the messages that are issued if you enter this command:

Example: The following command displays the summary status of all of the dispatch threads for the BBOS001 server:
f BBOS001,display,threads,all

The following messages display in response to this command. In this output, the requests that have a Y in the JW column were in a Java wait state when the command was issued. Similarly, the requests that have a Y in the TO column were considered unresponsive.

As part of its request processing, the product uses several techniques in attempts to make an unresponsive thread responsive, and enable a request to complete. However, these attempts are not always successful. After the product exhausts the maximum number of attempts that it can make to get a request to complete, it notifies the controller that the request should be terminated. In the preceding example, the requests with a Y in the RE column are the requests for which the product has exhausted attempts to get the request to finish.
BBOJ0111I:  REQUEST   ASID JW TO RE DISPATCH TIME             
BBOJ0112I: ffffb41d 0X0176  N  N  N 2008/03/24 20:03:28.212400
BBOJ0112I: ffffb420 0X0176  Y  Y  Y 2008/03/24 19:59:16.910228
BBOJ0112I: ffffb421 0X0176  Y  Y  Y 2008/03/24 19:59:14.982621
BBOJ0112I: ffffb422 0X0176  Y  Y  Y 2008/03/24 19:59:12.805119
BBOJ0112I: ffffb423 0X0176  Y  Y  Y 2008/03/24 19:59:08.936107
BBOO0188I END OF OUTPUT FOR COMMAND DISPLAY,THREADS,ALL
Example: The following command displays the detailed status of all of the dispatch threads for the BBOS001 server. For this command, the ALL parameter is implied.
f BBOS001,display,threads,details
The following messages display in response to this command:
BBOJ0106I: REQUEST fffff2a9 ASID 0X0064 TCB 0X008D0438 
BBOJ0119I: CONTROLLER RECEIVED REQUEST AT 2008/06/05 14:24:51.508941
BBOJ0120I: CONTROLLER QUEUED REQUEST TO WLM AT 2008/06/05           
14:24:51.509147  
BBOJ0107I: SERVANT DISPATCHED REQUEST AT 2008/06/05 14:24:51.509242    
BBOJ0108I: JVM THD IS NOT HUNG: ITI INACTIVE  
BBOJ0110I: DETAILS FOR GIOP Outbound: Target Operation =sayHelloTwo    
BBOJ0110I: DETAILS FOR JVM INTERRUPTIBLE THREAD: Monitor ACTIVE        
BBOJ0106I: REQUEST fffff2a3 ASID 0X0064 TCB 0X008CB2D8                   
BBOJ0119I: CONTROLLER RECEIVED REQUEST AT 2008/06/05 14:24:54.981645
BBOJ0120I: CONTROLLER QUEUED REQUEST TO WLM AT 2008/06/05           
14:24:54.982324
BBOJ0107I: SERVANT DISPATCHED REQUEST AT 2008/06/05 14:24:55.522788    
BBOJ0108I: JVM THD IS NOT HUNG: ITI INACTIVE                           
BBOJ0110I: DETAILS FOR JVM INTERRUPTIBLE THREAD: Monitor ACTIVE        
BBOO0188I END OF OUTPUT FOR COMMAND DISPLAY,THREADS,DETAILS
TIMEDOUT
Used to display information about the requests that are currently considered timed out.

You can specify the following options for the DISPLAY,THREADS,TIMEDOUT command. If no option is specified, summary is used.

DETAILS
Specifies that you want the full details about the requests that timed out.
SUMMARY
Specifies that, for each request that timed out, you only want to see the request ID, the ASID of the servant where the request was dispatched, and the time that the request was dispatched
Example: The following command displays a summary of the requests, that are running on the BBOS001 server, that are currently considered timed out.
f BBOS001,display,threads,timedout,summary
REQUEST=<value>
Used to display information about the request that has the specified ID.

You can specify the following options on the DISPLAY,THREADS,REQUEST command. If no option is specified, details is used.

DETAILS
Specifies that you want to see the full details about this request
SUMMARY
Specifies that, for this request, you only want to see the ASID of the servant where the specified request was dispatched, the time the request was dispatched, and whether the request timed out.
Example: The following command displays a summary of the request FFFFF2A9. For this command, the DETAILS option is implied.
f BBOS001,display,threads,request=FFFFF2A9
BBOJ0106I: REQUEST fffff2a9 ASID 0X0064 TCB 0X008D0438  
BBOJ0119I: CONTROLLER RECEIVED REQUEST AT 2008/03/27 16:51:36.981645
BBOJ0120I: CONTROLLER QUEUED REQUEST TO WLM AT 2008/03/27           
16:51:36.982324                
BBOJ0107I: SERVANT DISPATCHED REQUEST AT 2008/03/27 16:51:36.987541   
BBOJ0108I: JVM THD IS NOT HUNG: ITI INACTIVE                          
BBOJ0110I: DETAILS FOR GIOP Outbound: Target Operation = sayHelloTwo   
BBOJ0110I: DETAILS FOR JVM INTERRUPTIBLE THREAD: Monitor ACTIVE       
BBOO0188I END OF OUTPUT FOR COMMAND DISPLAY,THREADS,REQUEST=FFFFF2A9
ASID=<value>
Used to display information about the request, with the specified ASID, that is currently dispatched in the servant. The ASID must be specified as a hexidecimal value.

You can specify the following options on the DISPLAY,THREADS,ASID command. If no option is specified, summary is used.

DETAILS
Specifies that you want to see the full details about these requests.
SUMMARY
Specifies that you only want to see the request IDs, the time that each request was dispatched, and whether the requests timed out.
Example: The following command displays a summary of the dispatch threads for the servant that has the ASID 0038x.
f BBOS001,display,threads,ASID=0038x
AGE=<value>
Used to display information about the requests, for which the amount of time that has elapsed since the request was placed in dispatch is equal to or greater than the specified amount of time. Specify the length of time in seconds.

You can specify the following options on the DISPLAY,THREADS,AGE command. If no option is specified, summary is used.

DETAILS
Specifies that you want to see the full details about these requests.
SUMMARY
Specifies that, for each request, you only want to see the request ID, ASID where the request was dispatched, the time the request was dispatched, and whether the request timed out.
Example: The following command displays a summary of the dispatch threads for the requests for which the amount of time, that has elapsed since the request was placed in dispatch, is equal to or greater than 30 seconds
f BBOS001,display,threads,age=30

Display the status of clusters

To display the status of clusters in the active controller, use the following command:
f server,display,servers
Example: The following command will display status for the bbo6acr server:
f bbo6acr,display,servers
Here is a sample display:
F bbo6acr,DISPLAY,SERVERS
BBOO0182I SERVER             ASID   SYSTEM    LEVEL
BBOO0183I CBDAEMON/DAEMON01    31x  SY1       wd5xo03
BBOO0183I BBO5SR4 /BBOASR4A   1F6x  SY1       wd5xo03
BBOO0188I END OF OUTPUT FOR COMMAND DISPLAY,SERVERS

Display the diagnostic action for a JVM out-of-memory condition

To display the diagnostic action that is taken if a Java Virtual Machine (JVM) out-of-memory condition occurs in this server, along with the interval within which the diagnostic action is not repeated, use the following command:
f server,display,javaoom

One of the following values displays:

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.