Displaying status of z/OS UNIX System Services (OMVS)

Use the DISPLAY command to obtain information about z/OS® UNIX System Services (z/OS UNIX). information. For example:
  • z/OS UNIX information status, such as active or terminating, shutting down or restarting).
  • File system information.
  • z/OS UNIX processes for address spaces, including an indication of which processes are registered as permanent or blocking.
  • The current setting for all statements in the BPXPRMxx member (or members) of SYS1.PARMLIB that are used by z/OS UNIX. This includes system-wide and process limits, their high-water marks, and current usage.
  • Information about multiple parmlib members.
  • Information about each physical file system that is part of the z/OS UNIX System Services configuration.
  • Routing information from the common INET (CINET) prerouter tables.
  • Thread-level information for any thread that is in a byte-range lock wait.
  • z/OS UNIX kernel private storage below the bar (<2G) usage.

Use this command to display address space information for a user who has a process that is hung or that is waiting to become a process. You can also use the information that is returned from this command to determine how many address spaces a given TSO/E user ID is using, whether an address space is using too many resources, and whether a user's process is waiting for a z/OS UNIX kernel function to complete.

The syntax for the DISPLAY OMVS command is:

D OMVS[{,SUMMARY|S}]
       |,ACTIVATE=SERVICE       
       |,{ASID|A}=ALL
       |,{ASID|A}=asid
       |,{ASID|A}=DUBW
       |,{CINET|CI}=All|TPname
       |,{FILE|F[,{NAME|N}=filesystem][,CAPS|C]}
                |,{,EXCEPTION|E}  
                |,{,OWNER|O}=systemname 
                |,{,TYPE|T}=type
                |,{,UID|U}={USER|PRIV|uid}  
       |,{LIMITS|L[,PID=ProcessId][,RESET]}
       |,{PID}=processid[,BRL]
       |,PIPES[,ALL]|[,RESET]|[,{UID|U}=uid]
       |,MF[{=ALL|A}]
       |,MF={PURGE|P}]
       |,{PFS|P}
       |,{OPTIONS|O}
       |,{SER}
       |,{SOCKETS|SO}
       |,{STORAGE|ST[,RESET]}  
       |,U=userid
       |,USERMOUNTS  
       |,{VSERVER|V}
       |,{WAITERS|W [,
                |{AGE|A}
                |{LATCHES|L}
                |{MESSAGES|M}
                |{OTHER|O}
                |{SPECIAL|S}]
SUMMARY or S
Displays status of z/OS UNIX processes, file systems, and servers (for example, active or terminating) and the BPXPRMxx parmlib member that is specified during initialization or specified by the SET OMVS= system command.
ASID or A=ALL
Displays process information for all z/OS UNIX System Services address spaces.
ASID or A=asid
Displays process information for the specified hexadecimal address space ID (ASID). If the specified ASID is not a z/OS UNIX System Services address space, an error message is issued.
ASID or A=DUBW
Displays process information for all address spaces that are waiting to be dubbed a z/OS UNIX process. After message BPXP022E is issued to indicate one or more jobs are waiting for z/OS UNIX availability, you can issue D OMVS,A=DUBW to display all jobs waiting to be dubbed.
U=userid
Displays process information for all processes that are associated with the specified TSO/E user ID. Use this operand when a user requests that a hung process be canceled. You can display all processes that are owned by the user and find the address space ID (ASID) of the process that needs to be canceled. Then, use the CANCEL command to cancel the address space.
PID=processid
Displays thread information for the processid that is specified in decimal numbers. In a sysplex environment, you must issue the D OMVS,PID= command from the system on which the specified process is running. Refer to the following examples.
BRL
Displays thread-level information for any thread that is in a byte-range lock wait. You can specify this operand with the PID operand. Refer to the following examples.
PIPES
Displays summary information about the z/OS UNIX pipe usage. The default output is to list the two UIDs with the highest pipe create count. If ALL is specified, then all UIDs with a pipe create count are displayed. Use the RESET option to reset the user HIGHWATER USAGE and the HIGHWATER USER information and display the two UIDs with the highest pipe create count.
ALL
Displays all UIDs with a pipe create count.
RESET
Resets the HIGHWATER USER information and displays the two UIDs with the highest pipe create count.
UID=uid
Displays the current pipe usage for the high-use processes for the specified UID. At most, the top 10 high-use processes are displayed.
FILE or F
Displays a list of file systems that z/isUNIX is using, including the following:
  • The status of each file system.
  • The date and time that the file system was mounted.
  • The latch number for the file system.
  • The quiesce latch number for the file system, or 0 if the file system has never been quiesced by z/OS UNIX System Services.

If you are using z/OS File System (zFS) and need to determine the file system owner, see z/OS File System Administration.

You can limit the amount of information displayed by specifying one of the following keywords:
NAME or N=filesystem
Displays information about the specified file system or file systems. You can use one wildcard character (*) in the file system specified. For example, ZOS18.*.HFS or ZOS.L*.HFS. Specifying D OMVS,F,NAME=* results in the system displaying all file systems, which is the same output as if you specified D OMVS,F. Also, single quotation marks (') can be used to specify lowercase characters.
OWNER or O=systemname
Displays information for the file systems that are owned by the specified system name. Specifying D OMVS,F,OWNER displays all the file systems that are owned by this system.
EXCEPTION or E
Displays file systems in an exception state, such as a file system that is quiesced, unowned, or in recovery.
TYPE or T=type
Displays all file systems of the specified PFS type.
CAPS or C
Displays variable data that contains lowercase letters in uppercase.
VSERVER or V
Displays process information for all processes that have been defined as servers that use the virtual file system (VFS) callable services API.
CINET or CI = ALL|tpname
Displays the Common Inet routing information for all of the active transport providers in use by the common inet prerouter. The transport providers were specified with the SUBFILESYSTYPE statements in the BPXPRMxx profile or specified with the SETOMVS command. The network routing information was specified in the appropriate data set for the transport provider. When the name (tpname) of an active transport provider is specified, the command displays the Common Inet routing information for that specific transport provider. The Common Inet routing information includes home routes, implicit NON-DVIPA host routes, active host routes, and active network routes with route type, route metric, and net mask information. These displayed routes participate in the CINET prerouter route selection during request routing.
OPTIONS or O
Displays the current settings of the options that
  • (a) were set during initialization in the parmlib member BPXPRMxx or by a SET OMVS or SETOMVS command after initialization, and that
  • (b) can be altered dynamically via a SET OMVS or SETOMVS command.

If you issue the D OMVS,O command while OMVS is shut down, the system will attempt to display the OMVS parmlib options that were last in effect when OMVS was active. However, it is possible that some option values are unavailable and the values cannot be displayed.

PFS or P = Physical File System
Displays information about each physical file system that is currently part of the z/OS UNIX configuration. The physical file systems were specified in the BPXPRMxx profile, or with the SETOMVS command, or are an internal part of z/OS UNIX.
UID or U=USER|PRIV|uid
Displays information for the file systems that were mounted by the specified user.

Specify one of the following UID options:

USER
Displays all the file systems that were mounted by the nonprivileged users.
PRIV
Displays all the file systems that were mounted by the privileged users.
uid
Displays all the file systems that were mounted by the user whose effective UID is uid. If the specified uid is 0, it is equivalent to PRIV.
LIMITS or L
Displays information about current z/OS UNIX System Services parmlib limits, their high-water marks, and current system usage. When the PID= keyword is specified, LIMITS displays high-water marks and current usage for an individual process.
RESET
Resets the high-water mark for a system limit to 0.
SER
Reports serialization for all in-use, shared memory mutexes (mutual exclusion locks) and condition variables. Each mutex and condition variable is identified by the shared memory ID and the location of the shared memory object.

If the object is in an above-the-bar shared-memory segment, the location information indicates the address of the mutex or condition variable. If it is in a below-the-bar segment, the location information indicates the offset within the shared-memory segment. The offset is displayed, in this case, because each address space sharing a below-the-bar segment can map it at a different virtual address. For each mutex, the output shows the owner's TCB address, process ID, and ASID and the same for those waiting for access, if the system can determine that information.

For each condition variable, the output shows the same information for the waiting task of the condition variable and additionally identifies the associated mutex. User data is displayed for each owner and waiting task of a mutex or condition variable. In the case where Language Environment is the caller of BPX1SMC, the user data represents the address of the Language Environment DSA data area for the waiting or owning task.

ACTIVATE=SERVICE
Specifies that all the dynamically activated service items are to be displayed. Dynamically activated service consists of SMP/E installable service for the z/OS UNIX kernel and logical file system (LFS) components that was activated with the F OMVS,ACTIVATE=SERVICE command. (See Recycling (z/OS).

The service items are displayed in the order they were activated, with the most recent set of activated service items being displayed first. The most recent set of service items, which are shown as the highest numbered set of service items, are the highest level of service items that are activated for z/OS UNIX.

The display includes the following information:
  • The library and volume from which each set of service was activated.
  • The amount of ECSA and OMVS address space storage that is consumed by all dynamically activated service items. Note that the amount of storage consumed will not decrease if you deactivate service items (F OMVS,DEACTIVATE=SERVICE), because the modules containing the deactivated service items remain in storage. Refer to the following examples.
This command will not display deactivated service items.
USERMOUNTS
Displays summary information for nonprivileged user mounts.
WAITERS or W
Displays information about delays caused by the following conditions:
  • Mount latch contention
  • Outstanding unprocessed sysplex messages
  • File system latch contention
  • File latch contention
  • Other reasons

You can use the information displayed to figure out which tasks are hung, and why they are waiting. Refer to the following examples.

A set of filtering options limits the information that is displayed. If a section of the display is filtered out, the display does not show the section instead of displaying NONE. You can combine options in order to display certain sections. For example, specify D OMVS,W,xxx where xxx is one more of the following options, separated by commas:
LATCHES | L
Displays only the latch activity tables, including the mount, file system, and the file latch activity tables. The cross-system messages and other waiters tables are suppressed.
MESSAGES | M
Displays only the sent and received cross-system messages table. The mount latch, file system latch, file latch, and other waiters tables are suppressed. This option is valid only in a shared file system environment.
OTHER | O
Displays only the other waiters table. The mount latch, the file system latch, file latch, and cross-system messages table are suppressed.
AGE | A
Displays only the waiters that have been waiting for more than five minutes. A table is displayed if there are waiters that meet the criteria.
SPECIAL | S
Displays special files in the other waiters table that are otherwise filtered out. These are character special files, pipes, and sockets. This option is allowed by itself, with the A option, or when the O option has also been specified. For example: D OMVS,W,S and D OMVS W,O,S.
MF
MF=ALL | A
Displays information about move or mount failures:
  • Enter MF to display information about the last 10 or less move or mount failures.
  • Enter MF=ALL or MF=A to display information about the last 50 or less move or mount failures.
The system issues message BPXO058I to display the information about mount failures. Refer to the following examples.
MF= PURGE | P
Allows you to purge the saved information about mount failures displayed in message BPXO058I.
L=a, name, or name-a
Specifies the display area (a), console name (name), or both (name-a) where the display is to appear.

If you omit this operand, the display is presented in the first available display area or the message area of the console through which you enter the command.

SOCKETS | SO
Displays the following information about each AF_UNIX socket:
  • The owner's userid.
  • The socket name.
  • The name of the peer socket.
STORAGE or ST
Displays storage usage information for the kernel address space used by z/OS UNIX System Services. The display includes a summary of system-wide kernel stack cell pool cell usage, a list of processes using 50 or more stack cells, and private below the bar storage usage.
PROCESSES=xx | P=xx
Start of changeWhen the PROCESSES option is specified, xx displays the number of processes that will be shown in the display. The default is 10. End of change
RESET
Resets the HIGHWATER usage for PRIVATE STORAGE and STACK CELLS to the current usage.
UID=uid
Displays the current pipe usage for the high-use processes for the specified UID. At most, the top 10 high-use processes are displayed.
Example 1: To display process information for all z/OS UNIX address spaces, enter: 
DISPLAY OMVS,A=ALL
Status information for z/OS UNIX (OMVS ACTIVE) appears before the process information. See the appropriate z/OS UNIX documentation for an explanation of the data filled in below the headers, such as a state of MKI.
BPXO070I 14.31.40 DISPLAY OMVS 018
OMVS     000E ACTIVE          OMVS=(93)
USER     JOBNAME  ASID        PID       PPID STATE   START     CT_SECS
IBMUSER  BPXOINIT 0013          1          0 MKI   11.02.40       .037
  LATCHWAITPID=         0 CMD=BPXPINPR
  SERVER=Init Process                     AF=    0 MF=65535 TYPE=FILE
MEGA     MEGA     001A   16777218          1 1RI   11.18.17       .634
  LATCHWAITPID=         0 CMD=OMVS
MEGA     MEGA     001A   16777219   16777218 1CI   11.18.25       .634
  LATCHWAITPID=         0 CMD=sh -L
Example 2: To display z/OS UNIX process information on all z/OS UNIX address spaces owned by user ID MEGA, enter: 
DISPLAY OMVS,U=MEGA
z/OS UNIX status information (OMVS ACTIVE) appears before the process information. 
BPXO070I 14.34.15 DISPLAY OMVS 021
OMVS     000E ACTIVE          OMVS=(93)
USER     JOBNAME  ASID        PID       PPID STATE   START     CT_SECS
MEGA     MEGA     001A   16777218          1 1RI   11.18.17       .634
  LATCHWAITPID=         0 CMD=OMVS
MEGA     MEGA     001A   16777219   16777218 1CI   11.18.25       .634
  LATCHWAITPID=         0 CMD=sh -L
Example 3: To display z/OS UNIX process information for the address space with ASID equal to 001A, enter: 
DISPLAY OMVS,ASID=1A
z/OS UNIX status information (OMVS ACTIVE) appears before the process information. 
BPXO070I 14.36.04 DISPLAY OMVS 024
OMVS     000E ACTIVE          OMVS=(93)
USER     JOBNAME  ASID        PID       PPID STATE   START     CT_SECS
MEGA     MEGA     001A   16777218          1 1RI   11.18.17       .634
  LATCHWAITPID=         0 CMD=OMVS
MEGA     MEGA     001A   16777219   16777218 1CI   11.18.25       .634
  LATCHWAITPID=         0 CMD=sh -L
Example 4: To display detailed file system information on currently mounted files, enter: 
DISPLAY OMVS,FILE
z/OS UNIX status information appears before the file system information. 
d omvs,f
  BPXO045I 12.46.36 DISPLAY OMVS 527                                     
  OMVS     000E ACTIVE             OMVS=(Y2)                             
  TYPENAME   DEVICE ----------STATUS----------- MODE  MOUNTED    LATCHES 
  ZFS             2 ACTIVE                      RDWR  05/06/2010  L=15
    NAME=MY.ZFS                                       08.31.43    Q=15
    PATH=/SY1/Z1
    OWNER=SY1      AUTOMOVE=N CLIENT=N
  HFS            13 ACTIVE                      RDWR  05/11/2010  L=27   
    NAME=MY.HFS                                       21.40.45    Q=0    
    PATH=/SY1/H1                                                       
    UID=25
    OWNER=SY1      AUTOMOVE=Y CLIENT=Y

If AUTOMOVE was specified with a system list in the SETOMVS or chmount command, the list of candidates to take ownership of the file system is displayed under the file system owner.

For zFS file systems, the display includes an aggregate file system name indicating membership in a data set containing multiple file systems. Aggregates provide member file systems with a common pool of disk space.

Note: File systems can have a status of NOT ACTIVE if they were mounted under a physical file system (PFS) that has terminated, such as is possible with zFS, TFS, or NFS Client. These file systems cannot be made active again without unmounting and remounting them after the PFS is restarted. If the file systems are remounted, they will appear active with a new device number.

For the nonprivileged user-mounted file systems, the display includes the effective UID of the nonprivileged user who mounted the file system.

Example 5: To display process information for all processes that have been defined as a server, enter: 
DISPLAY OMVS,V
z/OS UNIX status information (OMVS ACTIVE) appears before the file system information. 
BPXO070I 14.38.46 DISPLAY OMVS 030
OMVS     000E ACTIVE          OMVS=(93)
USER     JOBNAME  ASID        PID       PPID STATE   START    CT_SECSS
IBMUSER  BPXOINIT 0013          1          0 MKI   11.02.40      .0373
  LATCHWAITPID=         0 CMD=BPXPINPR
  SERVER=Init Process                     AF=    0 MF=65535 TYPE=FILE
Example 6: To display all options set during initialization by the parmlib member BPXPRMxx or with the SET command, enter: 
DISPLAY OMVS,O
The SYSPLEX (YES) option indicates the system is in a sysplex and is using the shared file system capability. You cannot dynamically change the SYSPLEX parameter through SETOMVS or SET OMVS. For more information, see the section on shared file systems in z/OS UNIX System Services Planning.
You will see output that is similar to the following one:
d omvs,o
BPXO043I 13.10.16 DISPLAY OMVS 066                              
OMVS     000D ETC/INIT WAIT   OMVS=(M7)                         
CURRENT UNIX CONFIGURATION SETTINGS:                            
MAXPROCSYS      =        256    MAXPROCUSER     =         16    
MAXFILEPROC     =        256    MAXFILESIZE     = NOLIMIT       
MAXCPUTIME      =       1000    MAXUIDS         =        200    
MAXPTYS         =        256                                    
MAXMMAPAREA     =        256    MAXASSIZE       =  209715200    
MAXTHREADS      =        200    MAXTHREADTASKS  =       1000    
MAXCORESIZE     =    4194304    MAXSHAREPAGES   =       4096    
IPCMSGQBYTES    = 2147483647    IPCMSGQMNUM     =      10000    
IPCMSGNIDS      =        500    IPCSEMNIDS      =        500    
IPCSEMNOPS      =         25    IPCSEMNSEMS     =       1000    
IPCSHMMPAGES    =      25600    IPCSHMNIDS      =        500    
IPCSHMNSEGS     =        500    IPCSHMSPAGES    =     262144    
SUPERUSER       = BPXROOT       FORKCOPY        = Start of changeCOPYEnd of change           
STEPLIBLIST     =                                               
USERIDALIASTABLE=   
SERV_LINKLIB    = POSIX.DYNSERV.LOADLIB   BPXLK1
SERV_LPALIB     = POSIX.DYNSERV.LOADLIB   BPXLK1
PRIORITYPG VALUES: NONE                                         
PRIORITYGOAL VALUES: NONE                                       
MAXQUEUEDSIGS   =       1000    SHRLIBRGNSIZE   =   67108864    
SHRLIBMAXPAGES  =       4096    VERSION         = /             
SYSCALL COUNTS  = NO            TTYGROUP        = TTY           
SYSPLEX         = NO            BRLM SERVER     = N/A           
LIMMSG          = NONE          AUTOCVT         = OFF           
RESOLVER PROC   = DEFAULT       LOSTMSG=ON   
AUTHPGMLIST     = NONE                                          
SWA             = BELOW         NONEMPTYMOUNTPT = NOWARN
   SERV_LINKLIB   =
   SERV_LPALIB    =
MAXUSERMOUNTSYS = 0             MAXUSERMOUNTUSER = 0
MAXPIPEUSER     = 8730
SC_EXITTABLE    =
To display the current setting of the options that were set during initialization by the parmlib member BPXPRM93 or with the SET OMVS or SETOMVS command and that can be altered dynamically by either of those commands, enter: 
DISPLAY OMVS,O
You will see output that is similar to the following one:
BPXO043I 11.08.44 DISPLAY OMVS 962
OMVS     000E ACTIVE          OMVS=(93)
z/OS UNIX CURRENT CONFIGURATION SETTINGS:
MAXPROCSYS      =        256    MAXPROCUSER     =         16
MAXFILEPROC     =        256    MAXFILESIZE     = NOLIMIT
MAXCPUTIME      =       1000    MAXUIDS         =         32
MAXRTYS         =        256    MAXPTYS         =        256
MAXMMAPAREA     =       4096    MAXASSIZE       =   41943040
MAXTHREADS      =        200    MAXTHREADTASKS  =         50
MAXCORESIZE     =    4194304    MAXSHAREPAGES   =     131072
IPCMSGQBYTES    =     262144    IPCMSGQMNUM     =      10000
IPCMSGNIDS      =        500    IPCSEMNIDS      =        500
IPCSEMNOPS      =         25    IPCSEMNSEMS     =         25
IPCSHMMPAGES    =        256    IPCSHMNIDS      =        500
IPCSHMNSEGS     =         10    IPCSHMSPAGES    =     262144
SUPERUSER       = BPXROOT       FORKCOPY        = COPY
STEPLIBLIST     =
USERIDALIASTABLE=
PRIORITYGOAL VALUES: NONE
MAXQUEUEDSIGS   =       1000
SYSCALL COUNTS  = NO            TTYGROUP        = TTY
AUTHPGMLIST	    =/etc/authfile
SWA             = ABOVE         NONEMPTYMOUNTPT = DENY
SERV_LINKLIB    =
SERV_LPALIB     =
MAXUSERMOUNTSYS = 4             MAXUSERMOUNTUSER = 2
MAXPIPEUSER     = 8730
SC_EXITTABLE    =
Example 7: To display the thread information for process ID 1, enter: 
DISPLAY OMVS,PID=1
You will see a display similar to the following one:
BPXO070I 11.13.40 DISPLAY OMVS 971
OMVS     000E ACTIVE          OMVS=(93)
USER     JOBNAME  ASID        PID       PPID STATE   START     CT_SECS
IBMUSER  BPXOINIT 0013          1          0 MKI   11.02.40       .037
  LATCHWAITPID=         0 CMD=BPXPINPR
SERVER=Init Process                     AF=    0 MF=65535 TYPE=FILE
THREAD_ID        TCB@     PRI_JOB  USERNAME   ACC_TIME SC  STATE
04B9267800000000 009DEA70 OMVS                    .028 WAT  W
04B92F2000000001 009DE8D8                         .003 VRT  Y
04B937C800000002 009DE278 OMVS                    .002 KIN  K
Example 8: To display information about each physical file system that is part of the z/OS UNIX configuration when the physical file systems are specified in the BPXPRMxx profile, enter: 
D OMVS,P
You will see a display similar to the following one:
BPXO068I 10.59.48 DISPLAY OMVS 741                                  
OMVS     000E ACTIVE             OMVS=(33)                          
PFS CONFIGURATION INFORMATION                                       
 PFS TYPE   ENTRY      ASNAME    DESC      ST    START/EXIT TIME    
  CINET     BPXTCINT             SOCKETS   A     2010/06/17 14.16.52
  NFS       GFSCINIT   MVSNFSCL  REMOTE    A     2010/06/17 10.58.31
  TFS       BPXTFS     COLONY1   LOCAL     A     2010/06/17 10.58.29
  INET      EZBPFINI             SOCKETS   A     2010/06/17 10.59.36
  UDS       BPXTUINT             SOCKETS   A     2010/06/17 10.58.29
  ZFS       IOEFSCM    ZFSON2    LOCAL     A     2010/06/17 10.58.23
  AUTOMNT   BPXTAMD              LOCAL     A     2010/06/17 10.58.23
  HFS       GFUAINIT             LOCAL     A     2010/06/17 10.58.23
                                                                    
 PFS TYPE  DOMAIN        MAXSOCK  OPNSOCK  HIGHUSED                 
  CINET    AF_INET           400        0         0  
  INET     AF_INET         50000      244      8146 
  UDS      AF_UNIX            64        6        10 

SUBTYPES OF COMMON INET                                  
PFS NAME   ENTRY      START/EXIT TIME       STATUS  FLAGS
 TCPIP      EZBPFINI                         INACT       
 TCP2       EZBPFINI                         INACT                       
                                                                    
 PFS TYPE     FILESYSTYPE PARAMETER INFORMATION                     
  NFS          INITD,biod(2)                                        
  HFS          CURRENT VALUES: FIXED(0) VIRTUAL(56)
The information displayed is:
PFS TYPE
For each FILESYSTYPE statement, the data specified with the TYPE operand is displayed.
PFS DESC
A brief description of the physical file system.
ENTRY
The name of the load module specified with the ENTRYPOINT operand on the FILESYSTYPE or SUBFILESYSTYPE statements.
MAXSOCK
This is the MAXSOCKETS operand of a NETWORK statement for a sockets physical file system. It specifies the maximum number of sockets that can be open at one time for the address family.
OPNSOCK
OPEN SOCKETS: The number of sockets that are currently opened for this sockets physical file system.
HIGHUSED
The highest number of sockets that have been in use at one time for each of the configured address families.
PFS NAME
For each SUBFILESYSTYPE statement, the transport provider specified with the NAME operand is displayed.
FILESYSTYPE PARAMETER INFORMATION
Data specified with the PARM operand on the FILESYSTYPE or SUBFILESYSTYPE statements is displayed. For the file system, in addition to the IPL settings specified with PARM, the current settings for the FIXED and VIRTUAL PARMs are displayed.
ST
The state of each PFS. A = ACTIVE, I = INACTIVE, S = STOPPED, U = UNAVAILABLE.
START/EXIT TIME
The start or exit time of the PFS.
STATUS
The status of each PFS specified with the SUBFILESYSTYPE statement: ACT = ACTIVE, INACT = INACTIVE.
FLAGS
Additional information for each PFS that was defined with the SUBFILESYSTYPE statement:
CD
Current® Default transport provider. The system is currently using this PFS as the default transport provider although it wasn't specified as the default with the SUBFILESYSTYPE statement.
SD
Specified Default transport provider. This PFS was specified as the default transport provider with the SUBFILESYSTYPE statement. Currently, however, it is not being used as the default.
SC
Specified Current default transport provider. This PFS was specified as the default transport provider with the SUBFILESYSTYPE statement and the system is currently using it as the default.
Note:
  1. Although you can specify up to 1024 bytes of parameter information in the BPXPRMxx profile, only the first 165 bytes of parameter information is displayed.
  2. If a dash (-) appears as the first character for any PFS name, it means that the PFS is dead.
Example 9: To display the Common Inet routing information when there are three active transport providers, enter:
D OMVS,CINET
You will see a display similar to the following one. If Internet Protocol version 6 (IPv6) is in use, 16–byte IP addresses will display where appropriate. IPv6 data is displayed after IPv4 data.
BPXO047I 12.01.33 DISPLAY OMVS 285     
OMVS     000E ACTIVE          OMVS=(QY)
IPV4 HOME INTERFACE INFORMATION        
 TP NAME  HOME ADDRESS        FLAGS    
  TCPIPZ1   001.001.001.001            
  TCP1      003.003.003.003            
  TCPIPZ1   006.007.008.009            
  TCP1      044.044.044.044            
                                       
IPV4 HOST ROUTE INFORMATION            
 TP NAME   HOST DESTINATION     METRIC 
  TCPIPZ1   001.001.001.001        0   
  TCP1      003.003.003.003        0   
  TCP1      127.000.000.001        0   
  TCPIPZ1   127.000.000.001        0   
                                       
IPV4 NETWORK ROUTE INFORMATION                             
 TP NAME   NET DESTINATION     NET MASK          METRIC    
  TCPIPZ1   001.000.000.000     255.000.000.000     0      
  TCP1      003.000.000.000     255.000.000.000     0      
                                                           
IPV6 HOME INTERFACE INFORMATION                            
 TP NAME  HOME ADDRESS                                FLAGS
  TCP1      0022:0022:0022:0022:0022:0022:0022:0022     
  TCPIPZ1   0000:0000:0000:0000:0000:0000:0000:0009     
  TCP1      0021:0021:0021:0021:0021:0021:0021:0021     

IPV6 HOST ROUTE INFORMATION                                 
 TP NAME  HOST DESTINATION                            METRIC
  TCP1      0022:0022:0022:0022:0022:0022:0022:0022      0  
  TCP1      0001:0000:0000:0000:0000:0000:0000:0005      0  
  TCPIPZ1   0000:0000:0000:0000:0000:0000:0000:0008      0  
  TCP1      0000:0000:0000:0000:0000:0000:0000:0001      0  
  TCPIPZ1   0000:0000:0000:0000:0000:0000:0000:0001      0  
  TCPIPZ1   0000:0000:0000:0000:0000:0000:0000:0009      0  
  TCP1      0001:0000:0000:0000:0000:0000:0000:0007      0  
  TCP1      0021:0021:0021:0021:0021:0021:0021:0021      0  

IPV6 NETWORK ROUTE INFORMATION                                 
 TP NAME   NET DESTINATION                               METRIC
  TCPIPZ1   432B:0055:0066:0099:0099:0033:0000:0000/090     0  
  TCPIPZ1   0000:0000:0099:0044:0055:0077:0099:0066/060     0  
  TCP1      0000:0000:002E:002E:002E:002E:002E:002E/056     0  
  TCPIPZ1   0000:0000:0011:0014:0014:0013:0013:0013/090     0  
  TCPIPZ1   0000:0000:0031:0031:0031:0031:0043:0044/056     0  
  TCP1      0000:0000:002B:002B:002B:002B:002B:002B/090     0  
  TCP1      0000:0000:002D:002D:002D:002D:002D:002D/060     0  
  TCP1      0000:0000:002C:002C:002C:002C:002C:002C/090     0  
  TCP1      0000:0000:002F:002F:002F:002F:002F:002F/100     0  
  TCPIPZ1   0000:0000:0033:0033:0033:0033:0033:0033/100     0
The information displayed is:
TP NAME
The name of the transport provider for which the information is being displayed.
HOME ADDRESS
The Internet Protocol (IP) address of the transport provider. 16–bytes display for IPv6.
HOST DESTINATION
When a transport provider is connected to a host, the host IP address is displayed. 16–bytes display for IPv6.
NET DESTINATION
When a transport provider supplies network routing information to the Common Inet Pre-Router, the network destination address is the IP address of a network that can be accessed through the transport provider. 16–bytes display for IPv6. For IPv6, a PREFIX LENGTH follows a slash at the end of the net destination IP address. This value specifies how many of the leftmost contiguous bits comprise the prefix.
NET MASK
A mask that is applied to destination IP addresses to separate the network number from the host number.
METRIC
When selecting a route, if two transport providers can access the same route, the Common INET (CINET) Prerouter selects the route with the best metric. The lower the number, the better the metric. The metric 0 = a direct connection.
FLAGS
None.
Notes:
  1. When CINET is not installed, similar routing information can be obtained by using the netstat TC tpname gate command or the onetstat -p tpname -r command.
  2. When the CINET prerouter cannot find a specified IP address in its routing tables, it passes the request to a transport provider that has an active default route with the best route type and metric. The active default routes are now displayed along with other network routes for each TCPIP stacks. If no transport provider has an active default routes, then the request is routed to the default TCPIP stack.
Example 10:

To display information about current system-wide parmlib limits, enter: 

DISPLAY OMVS,L
You will see a display similar to the following one:
BPXO051I 14.05.52 DISPLAY OMVS 904
 OMVS     0042 ACTIVE          OMVS=(69)
 SYSTEM WIDE LIMITS:         LIMMSG=SYSTEM
                   CURRENT  HIGHWATER     SYSTEM
                     USAGE      USAGE      LIMIT
 MAXPROCSYS              1          4        256
 MAXUIDS                 0          0        200
 MAXPTYS                 0          0        256
 MAXMMAPAREA             0          0        256
 MAXSHAREPAGES           0         10       4096
 IPCMSGNIDS              0          0        500
 IPCSEMNIDS              0          0        500
 IPCSHMNIDS              0          0        500
 IPCSHMSPAGES            0          0     262144 *
 IPCMSGQBYTES          ---          0     262144
 IPCMSGQMNUM           ---          0      10000
 IPCSHMMPAGES          ---          0        256
 SHRLIBRGNSIZE           0          0   67108864
 SHRLIBMAXPAGES          0          0       4096
 MAXUSERMOUNTSYS        15         20        100
 MAXUSERMOUNTUSER        7          8         10 
 MAXPIPES               23        521      15360

An * displayed after a system limit indicates that the system limit was changed via a SETOMVS or SET OMVS= command. For the sysplex-wide limits, the command can be issued from any of the systems in the shared file system configuration environment, and the change can also be caused by the subsequent OMVS initialization on the other systems.

Example 11: To display information about current parmlib limits for a process with a PID of 33554434, enter:
DISPLAY OMVS,L,PID=33554434
You will see a display similar to the following one:
d omvs,l,pid=33554434
 BPXO051I 14.06.49 DISPLAY OMVS 907
 OMVS     0042 ACTIVE          OMVS=(69)
 USER     JOBNAME  ASID        PID       PPID STATE   START     CT_SECS
 WELLIE1  WELLIE1  001C    33554434         1 IRI   14.04.38       .015
   LATCHWAITPID=         0  CMD=EXEC
 PROCESS LIMITS:         LIMMSG=SYSTEM
                   CURRENT  HIGHWATER    PROCESS
                     USAGE      USAGE      LIMIT
 MAXFILEPROC             0          1        256,1000
 MAXFILESIZE           ---        ---    NOLIMIT
 MAXPROCUSER             1          4         16
 MAXQUEUEDSIGS           0          0       1000
 MAXTHREADS              0          0        200
 MAXTHREADTASKS          0          0         50
 IPCSHMNSEGS             0          0         10
 MAXCORESIZE           ---        ---    4194304,NOLIMIT

An * displayed after a process limit indicates that the limit was changed, either directly, with a SETOMVS,PID= command; or indirectly, by a global change of this value with a SETOMVS command.

The values displayed are in the same units as the values used in the SETOMVS command. For example, MAXFILESIZE is displayed in units of 4 KB.

Notes:
  1. Although MAXFILESIZE and MAXCORESIZE are displayed in the output, their current and high-water usage are not monitored, and no resource messages are issued for these resources.
  2. The MAXPROCUSER limit is based on UID, as opposed to PID, value. The current and high-water usage values reflect all values for all processes that have the same UID as the UID for the specified PID.
  3. For UID=0, there is no limit on MAXPROCUSER. When the PID= value in the DISPLAY command is for a process with UID=0, the process limit appears as unlimited. For example:
    MAXPROCUSER             4         11         NOLIMIT
  4. MAXCORESIZE, MAXFILESIZE, and MAXFILEPROC each have hard and soft limits. (See the documentation for the C-RTL function setrlimit() in z/OS XL C/C++ Runtime Library Reference.) When the hard and soft limits are the same, only one value is displayed. When the limits are different, both values are displayed: first the soft limit and then the hard limit, separated by a comma.

    In the preceding example, MAXFILEPROC has a hard limit of 1000 and a soft limit of 256. For MAXFILESIZE, the soft limit is equal to the hard limit and is unlimited. For MAXCORESIZE, the soft limit is 4,194,304 and the hard limit is unlimited.

Example 12: If the SETOMVS command is issued to change the value of MAXFILEPROC to 256, the information displayed is:
                  CURRENT  HIGHWATER    PROCESS
                    USAGE      USAGE      LIMIT
MAXFILEPROC             0          0        100,256
    .
    .
    .

If the process changes its soft limit for MAXFILEPROC to 100 (using the setrlimit() function), the information displayed is:

Example 13: To display thread-level information for any thread that is in a byte-range lock wait. enter:
D OMVS,PID=16777219,BRL
You will see a display similar to the following one:
BPXO070I 13.50.54 DISPLAY OMVS 042
OMVS     000E ACTIVE          OMVS=(99)
USER     JOBNAME  ASID        PID       PPID STATE   START     CT_SECS
WELLIE0  WELLIE0  0015   16777219   16777218 1CI   14.11.53       .703
  LATCHWAITPID=         0 CMD=sh -L
 THREAD_ID        TCB@     PRI_JOB  USERNAME   ACC_TIME SC  STATE
 250640E000000002 009C8550 OMVS                    .124 RED  C
 BRLWAIT DEV=00000001 INO=0000002E FILE=PoughkeepsiePho+ PID=12345678
 The blocking process is on system: SY2
The information displayed in BRLWAIT DEV=00000001 INO=0000002E FILE=PoughkeepsiePho+ PID=12345678 is:
DEV
The device number of the file's mounted file system.
INO
The inode number of the file, as shown by ls -i.
FILE
Up to 16 characters of the filename of the file that is being locked. If the filename has more than 16 characters, the first 15 are displayed, followed by a plus sign (+).
PID
The process ID of another process that is blocking this process from obtaining the lock. Usually this is the owner (or one of the owners) of a lock on the same range, but sometimes it is another process that is also waiting.
The system also displays the name of the system for where the blocking process is, when the following conditions occur:
  • The command is issued in a sysplex configuration.
  • The blocking process is from a system in the sysplex that is different from the system where the command is issued.
Example 14: To display a report of serialized, in-use, shared memory mutexes and condition variables, enter:
D OMVS,SER
You will see a display similar to the following one:
BPXO057I 08.51.42 DISPLAY OMVS 284
OMVS     000E ACTIVE          OMVS=(6D)
                  UNIX SERIALIZATION REPORT
NO RESOURCE CONTENTION EXISTS
The output from D OMVS,SER will be as follows when there is contention:
BPXO057I 08.51.42 DISPLAY OMVS 284
OMVS     000E ACTIVE          OMVS=(6D)
                  UNIX SERIALIZATION REPORT
RESOURCE     #1

  NAME=SHARED MUTEX   DATA:  SHMID=00000648 OFFS/ADDR=0000000000002428
 JOBNAME  ASID TCB        PID     USER DATA        EXC/SHR  OWN/WAIT
 DOMINO1 013A 008EF190 16777220 0000000024780148 EXC      OWN
 DOMINO2 02B2 008FA190 16908357 0000000024825220 EXC      WAIT
 DOMINO3 0206 008FF458 16973924 0000000024824778 EXC      WAIT
RESOURCE     #2

  NAME=SHARED CONDVAR   DATA:  SHMID=00000648 OFFS/ADDR=0000000000002458  
 JOBNAME ASID TCB   PID
 DOMINO2 02B6 008FA190 16908357 0000000024825220 EXC      WAIT
 DOMINO3 0206 008FF458 16973924 0000000024824778 EXC      WAIT
 RESOURCE #0002 IS LOCKED BY:
  NAME=SHARED MUTEX   DATA:  SHMID=00000648 OFFS/ADDR=0000000000002428
The information displayed is:
NAME= SHARED MUTEX / CONDVAR
An indication of whether the object is a mutex (MUTEX) or condition variable (CONDVAR).
Example 15: To display information about all the dynamically activated service items, enter:
D OMVS,ACTIVATE=SERVICE
You will see a display similar to the following one:
BPXO059I 08.51.42 DISPLAY OMVS 284              
OMVS     000E ACTIVE          OMVS=(6D)
            DYNAMIC SERVICE ACTIVATION REPORT
 SET  #3: 											   
   LINKLIB=SYS1.DYNLIB.PVT                      VOL=BPXLK1 
    LPALIB=SYS1.DYNLIB.LPA                      VOL=BPXLK1
     OA12345  OA23456  OA34567  OA45678  ANLATC1        
 SET  #2:
   LINKLIB=SYS1.DYNLIB.PVT                      VOL=BPXLK1
    LPALIB=SYS1.DYNLIB.LPA                      VOL=BPXLK1
    OA02001  OA02002  OA02003  OA02004  OA02004  OA02005
    OA02007  OA02008  OA02009    
 SET  #1:
   LINKLIB=SYS2.DYNLIB.PVT                      VOL=BPXLK1
    LPALIB=SYS1.DYNLIB.LPA                      VOL=BPXLK1
    OA01001  OA01002  OA01003
ECSA STORAGE: 1268496       OMVS  STORAGE:  4768248
This display output shows that the service items (such as OA12345) are listed in groups based on when they were activated. The displayed information includes the library and volume from which each set of service was activated. At the end of the report, the output shows the amount of ECSA and OMVS address space storage consumed by all dynamically activated service items.The amount of storage that is consumed will not decrease if you deactivate service items because the modules containing the deactivated service items remain in storage. For example, let us say you back off the most recently dynamically activated service (Set 3) shown in the preceding output with the following command:
F OMVS,DEACTIVATE=SERVICE
Next, you enter the display command again, to see the following output:
D OMVS,ACTIVATE SERVICE
You will see a display similar to the following one:
BPXO059I 08.58.26 DISPLAY OMVS 296              
OMVS     000E ACTIVE          OMVS=(6D)   
             DYNAMIC SERVICE ACTIVATION REPORT 
 SET  #2:
   LINKLIB=SYS1.DYNLIB.PVT                      VOL=BPXLK1
    LPALIB=SYS1.DYNLIB.LPA                      VOL=BPXLK1
    OA02001  OA02002  OA02003  OA02004  OA02005  OA02006
    OA02007  OA02008  OA02009    
 SET  #1:
   LINKLIB=SYS2.DYNLIB.PVT                      VOL=BPXLK1
    LPALIB=SYS1.DYNLIB.LPA                      VOL=BPXLK1
    OA01001  OA01002  OA01003
 ECSA STORAGE: 1268496         OMVS  STORAGE:  4768248TT
The service items in Set #3 are no longer shown because they have been deactivated, but the total ECSA and OMVS storage consumed has not decreased.
Example 16: To display information about waiters caused by mount latch contention, outstanding sysplex messages, file system contention or other conditions, enter:
D OMVS,W
You will see a display similar to the following one: 
SY1  D OMVS,W                                                         
SY1  BPXO063I 12.39.07 DISPLAY OMVS 426                               
OMVS     000E ACTIVE          OMVS=(QY)                               

MOUNT LATCH ACTIVITY:                                                 
    USER   ASID     TCB           REASON                        AGE   
----------------------------------------------------------------------
 HOLDER:                                                              
  OMVS     000E  008E9828     Inact Cycle                     00.01.18
     IS DOING: XPFS VfsInactCall / XSYS Message To: SY2               
     FILE SYSTEM: ZOS17.SY2.ETC.HFS                                   
     HOLDING: File System Latch 123  EXCL
WAITER(S):                                                           
  OMVS     000E  008D97C8     FileSys Quiesce                 00.00.05
  OMVS     000E  008E9B58     FileSys Sync                    00.01.10

OUTSTANDING CROSS SYSTEM MESSAGES:                                    
 SENT SYSPLEX MESSAGES:                                               
    USER   ASID   TCB    FCODE  MEMBER   REQID     MSG TYPE     AGE   
----------------------------------------------------------------------
  MEGA     0025 008DD218  0008 SY2      01000038 LookupCall   00.03.08
      FILE: somedirname                     (12,456)
      HOLDING: File System Latch 333  SHR 
  TC0      0026 008E6E88  1011 SY1      0100003A Quiesce      00.00.05
      HOLDING: File System Latch 456  EXCL
  OMVS     000E 008E9828  0804 SY2      01000039 VfsInactCall 00.01.18
      HOLDING: File System Latch 27  EXCL

RECEIVED SYSPLEX MESSAGES:                                           
           FROM   FROM           FROM                                 
   ON TCB  ASID   TCB    FCODE  MEMBER   REQID     MSG TYPE     AGE   
----------------------------------------------------------------------
  008D97C8 0026 008E6E88  1011 SY1      0100003A Quiesce      00.00.05
     IS DOING: Mount Latch Wait             
  008D1238 0022 008E6E00  0003 SY3      01000123 Read         00.07.25
     IS DOING: ZFS      Read
     FILE: thefilename                      (44,1234)
     FILE SYSTEM: ZOS17.SY2.VAR.HFS   
     HOLDING: File System Latch 33  SHR

FILE SYSTEM LATCH ACTIVITY:            
    USER   ASID     TCB            SHR/EXCL                     AGE   
----------------------------------------------------------------------
Latch 432 FILE SYSTEM:  THE.FILESYS.NAME
 HOLDER(S):                  
   User10  0044  00880460            SHR                     00:12:08
        IS DOING: NFS ReadCall              
        FILE: somefilename                 (88,1234)
   User11  0045  00880460            SHR                     00:15:58
        IS DOING: NFS ReadCall              
        FILE: somefilename                 (88,1234)
    WAITER(S):                                                          
   OMVS    000E  008E9B58            EXCL                    00.01.10
Latch 678 FILE SYSTEM:  ANOTHER.FILESYS.NAME
 HOLDER(S):                  
   OMVS    000E  00820420            EXCL                    00:12:08
     IS DOING: ZFS SyncCall / Osi_Wait
    WAITER(S):                                                           
   User12  0022  008D97C8            SHR                     00.00.05
   User15  0072  008E9B58            SHR                     00.01.10
FILE LATCH ACTIVITY:                                                  
    USER   ASID     TCB             SHR/EXCL                    AGE   
----------------------------------------------------------------------
LATCH 66    LSET 01 TYPE REGFILE    DEVNO 2 INO 204        
FILE: myfile
FILE SYSTEM: ZOS112.ETC.ZFS
 HOLDER(S):                                                           
  TC0      0026  008E6D90             EXCL                    00.00.56
     TIME: 2009/10/08 16.21.36                                        
     IS DOING: Running
     FILE: myfile                             (2,204)                                                
 WAITER(S):                                                           
TC0      0027  008E6D90               SHR                     00.00.53
     TIME: 2009/10/08 16.21.38                                        

OTHER WAITING THREADS: 
  USER     ASID   TCB         PID           AGE
--------------------------------------------------
  USER01   0021 00908070     1234         00:12:41    
    IS DOING: NFS Readdir / Running             
    FILE: nfsdirname                    (33,5432)
    FILE SYSTEM: HOST12.AJAX.DIRECTORY                          
    HOLDING: File System Latch #123 SHR
  USER03   0041 00908070   786534         00:12:41    
    IS DOING: BRLM Wait 
    FILE: FileNameIsHere                (22,845)    
    FILE SYSTEM: AJAX.DS88.ZFS                           
  USER04   0051 00908070       15         00:00:49    
    IS DOING: File Latch Wait-Latch 1379              
    FILE: somefilename                  (88,1234)
    FILE SYSTEM: HOST12.AJAX.DIRECTORY                          
    HOLDING: File System Latch #123 SHR
  USER05   0071 00908070   378992         00:08:51    
    IS DOING: ZFS Write / OSI_WAIT 
    FILE: zfsfilename                       
    FILE SYSTEM: AJAX.DS23.ZFS
Example 17: To display information about the last 10 or less mount or move failures, enter:
D OMVS,MF
You will see a display similar to the following one:
SY1  d omvs,mf                                                         
      SY1  BPXO058I 11.22.20 DISPLAY OMVS 480                                
      OMVS     000D ACTIVE          OMVS=(MN,ZS)                             
      SHORT LIST OF FAILURES:
      TIME=16.24.40  DATE=2003/11/18        MOVE   RC=0489  RSN=1278054D 
        NAME=ZOS16.SY1.HFS                                               
        PATH=/SY1                                                        
        SYSNAME=SY3                                                      
      TIME=11.22.07  DATE=2003/11/18        MOUNT  RC=0099  RSN=C5C7082A     
        NAME=MY.HFS                                                          
        TYPE=HFS                                                             
        PATH=/SY1/tmp                                                        
      TIME=21.58.17  DATE=2003/11/17        MOVE   RC=0079  RSN=119E04B7     
        NAME=*                                                               
        SYSNAME=SY9  
      TIME=11.54.04  DATE=2003/11/25        MOVE   RC=0079  RSN=119E04B7
        PATH=/SY2                                                       
        SYSNAME=CAT                                                     
      TIME=11.52.15  DATE=2003/11/25        MOVE   RC=0079  RSN=119E04B7
        NAME=ZOS16.SY2.HFS                                              
        SYSNAME=DOG
Example 18: To display information about each AF_UNIX socket, enter:
D OMVS,SOCKETS
You will see a display similar to the following one:
BPXO060I 17.12.57 DISPLAY OMVS                          
OMVS     000D ACTIVE          OMVS=(6F,JB)                 
         AF_UNIX Domain Sockets            
JOBNAME    ID     PEER ID  STATE    READ     WRITTEN   
-------- -------- -------- ------   -------- --------
TCPCS    00000003 00000000 LISTEN   00000345  
 Socket name: /var/sock/SYSTCPCN.TCPCS
TCPCS    0000002A 00000022 ACP      000012AB 00054C2A
 Socket name: /var/sock/SYSTCPCN.TCPCS
   Peer name: /tmp/sock1
NETVIEW  00000022 0000002A CONN     00054C2A 000012AB
 Socket name: /tmp/sock1
   Peer name: /var/sock/SYSTCPCN.TCPCS
USER14   00000006 00000000 DGRAM    00000480 00000ABC
 Socket name: /tmp/test.sock
TCPCS    00000037 00000034 ACP      00000012 0000034C
 Socket name: /var/sock/SYSTCPCN.TCPCS
JLB      00000034 00000037 CONN     0000034C 00000022
   Peer name: /var/sock/SYSTCPCN.TCPCS
Example 19: To display information about the nonprivileged user mounts, enter: 
D OMVS,USERMOUNTS

691 D OMVS,USERMOUNTS                                   
692   BPXO072I 13.28.20 DISPLAY OMVS 544                 
693   OMVS     000E ACTIVE             OMVS=(3Z)      
694   NONPRIVILEGED USER MOUNTS SUMMARY   
695             UID   CURRENT MOUNTS                      
696             295           1                          
697             647           2                          
698              25           1
Example 20: To display the default output, which will list the top two high-use UIDs, enter:
D OMVS,PIPES
You will see a display similar to the following one:
BPXO073I 15.40.20 DISPLAY OMVS 645
OMVS     000F ACTIVE             OMVS=(2E)
PIPE OWNER SUMMARY           MAXPIPEUSER=8730
                         CURRENT  HIGHWATER
USERID              UID   USAGE     USAGE
WELLIE2              12    3000      3000
WELLIE1              11    2100      2100
HIGHWATER USER:
  USERID=WELLIE2  UID=12 HIGHWATER USAGE=3000
Example 21: To display all the open pipe creators, enter: 
D OMVS,PIPES,ALL
You will see a display similar to the following one:
BPXO073I 15.41.58 DISPLAY OMVS 648
OMVS     000F ACTIVE             OMVS=(2E)
PIPE OWNER SUMMARY          MAXPIPEUSER=8730
                         CURRENT   HIGHWATER
USERID             UID    USAGE      USAGE
MEGA                 0     1000       1000
WELLIE1             11     2100       2100
WELLIE2             12     3000       3000
HIGHWATER USER:
  USERID=WELLIE2  UID=12 HIGHWATER  USAGE=3000
Example 22: To display the processes that created active pipes for UID(11), enter: 
D OMVS,PIPES,u=11
You will see a display similar to the following one:
BPXO074I 15.43.31 DISPLAY OMVS 651
OMVS     000F ACTIVE             OMVS=(2E)
TOTAL CURRENT USAGE=2100
                CURRENT    SYSTEM
      PID        USAGE      NAME
    50331678       600     SY1
          24       500     SY1
    50331674       500     SY1
    50331676       500     SY1
Example 23: Start of changeTo display the z/OS UNIX kernel private below-the-bar usage, issue D OMVS,ST.End of change
BPXO075I 11.01.17 DISPLAY OMVS 678                                
OMVS     000F ACTIVE             OMVS=(D3,DN,D4)                  
                      KERNEL STORAGE USAGE                        
PRIVATE STORAGE:                                                  
CURRENT USAGE     MAXIMUM AVAILABLE     HIGH WATER     REGION SIZE
     32501759          302244659          32501759      1525653504
THREADS:                                                          
CURRENT USAGE     MAXIMUM THREADS       HIGH WATER                
           64            500000                 64                
                    PROCESS THREAD USAGE                          
USER     JOBNAME  ASID        PID       PPID STATE    THREADS     
WELLIE0  WELLIE01 0026          7   33554438 HK------      51
If no processes have more than 50 threads, you will get the following output instead of a list:
NO PROCESSES FOUND USING 50 OR MORE THREADS