BPXO063I

file_name

Explanation
 In the message, text is as
follows:   
procname kernalasid  status   parmmemberlist
MOUNT LATCH ACTIVITY:    
  USER     ASID   TCB        REASON         AGE    
-----------------------------------------------
HOLDER: 
  user     asid tcb      reason           age 
    TIME: yyyy/mm/dd hh.mm.ss
    IS DOING:          activity  / [pfs_qualifier]

    FILE SYSTEM: file_system_name             
    HOLDING: File System Latch latchno SHR|EXCL
WAITER(S):                                    
  user     asid tcb      reason           age 
  TIME: yyyy/mm/dd hh.mm.ss
  user     asid tcb      reason           age 
  TIME: yyyy/mm/dd hh.mm.ss
                      .
                      .
                      .
  user     asid tcb      reason           age
 FILE SYSTEM LATCH ACTIVITY:            
     USER   ASID     TCB            SHR/EXCL                  AGE   
-----------------------------------------------------------------
LATCH latchno    FILE SYSTEM: file_system_name
  HOLDER(S):
    user   asid      tcb           SHR|EXCL                    age
    TIME: yyyy/mm/dd hh.mm.ss
    IS DOING: activity / [pfs_qualifier]
    FILE: file_name (devno,ino)
  WAITER(S):
    user   asid      tcb           SHR|EXCL                    age
                      .
                      .
                      .
FILE LATCH ACTIVITY:                                                  
    USER   ASID     TCB             SHR/EXCL                 AGE   
-------------------------------------------------------------------
LATCH latchno LSET lset TYPE file_type   DEVNO devno INO ino        
FILE: file_name 
FILE SYSTEM: file_system_name
 HOLDER(S):                                                           
  user   asid      tcb           SHR|EXCL                    age
     TIME: yyyy/mm/dd hh.mm.ss                                       
     IS DOING: activity / [pfs_qualifier]
     FILE: file_name (devno,ino)

 WAITER(S):   
  user   asid      tcb           SHR|EXCL                    age
     TIME: yyyy/mm/dd hh.mm.ss                                       
                      .
                      .
                      .                                                   

OUTSTANDING CROSS SYSTEM MESSAGES:                                    
 SENT SYSPLEX MESSAGES:                                               
    USER   ASID   TCB    FCODE  MEMBER   REQID/SEQ     MSG TYPE   AGE   
---------------------------------------------------------------------------
  user     asid tcb      fcode member   reqid   msg_type    age
     TIME: yyyy/mm/dd hh.mm.ss seqno
     FILE: file_name (devno,ino)
    HOLDING: File System Latch latchno SHR|EXCL
  user     asid tcb      fcode member   reqid   msg_type    age
                      .
                      .
                      .
  user     asid tcb      fcode member   reqid   msg_type    age

 RECEIVED SYSPLEX MESSAGES:                                           
           FROM   FROM           FROM                                 
   ON TCB  ASID   TCB    FCODE  MEMBER   REQID/SEQ     MSG TYPE     AGE   
----------------------------------------------------------------------------
  on_tcb   asid   tcb     fcode member   requid   msg_type   age 
  TIME: yyyy/mm/dd hh.mm.ss seqno
  IS DOING:          activity  / [pfs_qualifier]
  FILE: file_name (devno,ino)
  FILE SYSTEM: file_system_name             
  HOLDING: File System Latch latchno SHR|EXCL

 OTHER WAITING THREADS:
    USER   ASID     TCB                PID                       AGE
--------------------------------------------------------------------
    user   asid     tcb               pid                       age 
      TIME: yyyy/mm/dd hh.mm.ss
      IS DOING: activity / [pfs_qualifier]
      FILE: file_name (devno,ino)
      FILE SYSTEM: file_system_name             
    HOLDING: File System Latch latchno SHR|EXCL
                      .
                      .
                      .

 In response to
a DISPLAY OMVS,WAITERS (D OMVS,W) operator command, this message displays
information about delays caused by: Mount latch contention.
Outstanding sysplex messages. When a system sends a sysplex messages
to another sysplex member, the sending system then waits for the outstanding
reply message. If the reply is not sent, the user or system task on
the sending system hangs.
File system contention.
File latch contention
Other reasons.

You can use the information displayed to figure out what tasks
are hung, and what they are waiting for.
 In the message text:
 hh.mm.ss
The time in hours (00–23), minutes (00–59), and seconds
(00–59) for the DISPLAY OMVS command.
procname
The name of the z/OS UNIX cataloged
procedure.
status
One of the following:  ACTIVE
z/OS UNIX is
currently active.
NOT STARTED
z/OS UNIX was
not started.
INITIALIZING
z/OS UNIX is
initializing.
TERMINATING
z/OS UNIX is
terminating.
TERMINATED
z/OS UNIX has
terminated.
ETC/INIT WAIT
z/OS UNIX is
waiting for the /etc/init or /usr/sbin/init program
to complete initialization.
FORK SHUTDOWN
 FORK Service has been shutdown.
SHUTTING DOWN
z/OS UNIX is
shutting down.
SHUTDOWN BLOCKED
z/OS UNIX shutdown
processing is blocked by one or more jobs, and it waits for all of
the blockers to unblock or terminate.
SHUTDOWN
z/OS UNIX is
shut down.
RESTARTING
z/OS UNIX is
restarting after a shut down.

parmmemberlist
The parmlib member name list specified on the SET OMVS command
or on the initialization of OMVS. 
MOUNT LATCH ACTIVITY:
USER     ASID   TCB        REASON         AGE
This section shows what user and task is holding the mount latch
(HOLDERS:), and what users are waiting for it (WAITERS).
user
The user ID of the address space.
asid
The address space ID.
tcb
The task.
reason
A short description of what the end user action that the user
or task is doing. reason is one of the following: Accessing CDS
FileSys Quiesce
Module Cleanup
AutoMnt vnLookup
FileSys UnQuiesce
Mount Catchup
BHR Async Mount
FileSys Export
Move Filesystem
Blocking Utility
FileSys UnExport
PFS Termination
Check FS Latches
FlSys Diag & Fix
Post MXRH Waiter
Couple DS Switch
FileSys Re-Init
ReMount Filesys
Diag & Fix CDS

Get BRLM locks
Sysplex Scheduler
FileSys Mount
Inact Cycle
Unknown
FileSys Unmount
Init PFS Control
Update Client VFS
FileSys Sync yes
MemberGone Rcvry
VerifyServiceLvl

age
The amount of time the user has held the mount latch for HOLDERS,
or the amount of time users have waited for the mount latch for waiters. If the time exceeds 99 hours, two asterisks (**) appear
in the hour position. 
TIME: yyyy/mm/dd hh.mm.ss
The date and time when the activity started.
IS DOING: activity / [pfs_qualifier] 
 activity
Description of what the holding task is doing. activity is
displayed as either:  A wait, such as a Latch Wait
The type of physical file system (PFS) and the operation that
the task was  called to do, such as READ, WRITE, MOUNT, or FSYNCH 

pfs_qualifier
If the activity field shows a PFS,
the pfs_qualifier field shows what the PFS is doing.
For example, pfs_qualifier might show: Running - If the pfs_qualifier field
shows Running for very long, it probably indicates
that the thread is in a PFS wait that cannot be detected by DISPLAY
OMVS.
Osi Wait
XSYS Message to: sysname

FILE SYSTEM: file_system_name
The name of the file system involved, if any.
HOLDING: File System Latch latchno SHR|EXCL
 A file system latch is held by this thread. latchno
The latch number that corresponds to the latch shown by DISPLAY
GRS.
 SHR|EXCL
Whether the latch is held in shared or exclusive mode.

FILE SYSTEM LATCH ACTIVITY:  
USER   ASID     TCB       SHR/EXCL     AGE
This section shows information for file system latches.
It shows what user and task is holding the latch (HOLDERS), and what
users are waiting for it (WAITERS).
LATCH latchno 
A file system latch is held by this thread. latchno
The latch number that corresponds to the latch shown by Display
GRS.

FILE SYSTEM: file_system_name
The name of the file system involved, when available.
HOLDER(S): user   asid tcb SHR|EXCL age
The file system holding the latch: user
The user ID of the address space.
asid
The address space ID.
tcb
The task.
 SHR|EXCL
Whether the latch is held in shared or exclusive mode.
age
The amount of time the user has held the file system latch for
HOLDERS. If the time exceeds 99 hours, two asterisks (**) appear
in the hour position. 

TIME: yyyy/mm/dd hh.mm.ss
The date and time when the activity started.
IS DOING: activity / [pfs_qualifier] 
 activity
Description of what the holding task is doing. activity is
displayed as either:  A wait, such as a Latch Wait
The type of physical file system (PFS) and the operation that
the task was  called to do, such as READ, WRITE, MOUNT, or FSYNCH 

pfs_qualifier
If the activity field shows a PFS, the pfs_qualifier field
shows what the PFS is doing. For example, pfs_qualifier might
show: Running - If the pfs_qualifier field
shows Running for very long, it probably indicates
that the thread is in a PFS wait that cannot be detected by DISPLAY
OMVS.
Osi Wait
XSYS Message to: sysname

FILE: file_name (devno,ino)
For operations on a specific file, this line shows the following
information: file_name
 Up to 16 characters of the file name when this
information is available.
devno
The device number of the file.
ino
The inode number of the file.

WAITER(S): user   asid tcb SHR|EXCL age
The file system holding the latch: user
The user ID of the address space.
asid
The address space ID.
tcb
The task.
 SHR|EXCL
Whether the latch is held in shared or exclusive mode.
age
The amount of time users have waited for the file system latch
for waiters. If the time exceeds 99 hours, two asterisks (**)
appear in the hour position.

TIME: yyyy/mm/dd hh.mm.ss
The date and time when the activity started.
IS DOING: activity / [pfs_qualifier] 
 activity
Description of what the holding task is doing. activity is
displayed as either:  A wait, such as HSM recall when the task is waiting on an HSM
recall
The type of physical file system (PFS) and the operation that
the task was  called to do, such as READ, WRITE, MOUNT, or FSYNCH 

pfs_qualifier
If the activity field shows a PFS, the pfs_qualifier field
shows what the PFS is doing. For example, pfs_qualifier might
show: Running - If the pfs_qualifier field
shows Running for very long, it probably indicates
that the thread is in a PFS wait that cannot be detected by DISPLAY
OMVS.
Osi Wait
XSYS Message to: sysname

FILE: file_name (devno,ino)
For operations on a specific file, this line shows the following
information: file_name
 Up to 16 characters of the file name when this
information is available. 
devno
The device number of the file.
ino
The inode number of the file.
When the waiter is waiting on an HSM recall,
the file_name will show the directory created by automount,
but the devno and ino  are unavailable because these
numbers are not known until the file system is mounted.

FILE SYSTEM: file_system_name
The name of the file system involved, when available.
HOLDING: File System Latch latchno SHR|EXCL
 A file system latch is held by this thread. latchno
The latch number that corresponds to the latch shown by DISPLAY
GRS.
 SHR|EXCL
Whether the latch is held in shared or exclusive mode.

FILE LATCH ACTIVITY:  
USER   ASID     TCB       SHR/EXCL     AGE
This section shows information for file latches. It shows what
user and task is holding the latch (HOLDERS), and what users are waiting
for it (WAITERS).
LATCH latchno 
A file latch is held by this thread. latchno
The latch number that corresponds to the latch shown by Display
GRS.

LSET lset 
Indicates the identifier of the latch set.  lset
The identifier that corresponds to the latch. File latches are
created in the SYS.BPX.A000.FSLIT.FILESYS.LSN.xx latch
set where xx corresponds to LSET.

devno devno 
Indicates the device number of the file.  devno
The device number that corresponds to the file. 

ino ino 
Indicates the inode number of the file.  ino
The inode number that corresponds to the file. 

TYPE filetype 
Indicates the file type.  file_type
Indicates the file type (DIR, CHARSPEC, REGFILE, FIFO) 

FILE: file_name 
The name of the file (if known) involved in the operation.  file_name
 Up to 16 characters of the file name when this
information is available.

FILE SYSTEM: file_system_name
The name of the file system that owns the file involved in the
operation. 
HOLDER(S): user   asid tcb SHR|EXCL age
The file system holding the latch: user
The user ID of the address space.
asid
The address space ID.
tcb
The task.
 SHR|EXCL
Whether the latch is held in shared or exclusive mode.
age
The amount of time the user has held the file system latch for
HOLDERS. If the time exceeds 99 hours, two asterisks (**) appear
in the hour position. 

TIME: yyyy/mm/dd hh.mm.ss
The date and time when the activity started.
IS DOING: activity / [pfs_qualifier] 
 activity
Description of what the holding task is doing. activity is
displayed as either:  A wait, such as a Latch Wait
The type of physical file system (PFS) and the operation that
the task was  called to do, such as READ, WRITE, MOUNT, or FSYNCH 

pfs_qualifier
If the activity field shows a PFS, the pfs_qualifier field
shows what the PFS is doing. For example, pfs_qualifier might
show: Running - If the pfs_qualifier field
shows Running for very long, it probably indicates
that the thread is in a PFS wait that cannot be detected by DISPLAY
OMVS.
Osi Wait
XSYS Message to: sysname

FILE: file_name (devno,ino)
For operations on a specific file, this line shows the following
information: file_name
 Up to 16 characters of the file name when this
information is available. 
devno
The device number of the file.
ino
The inode number of the file.
When the waiter is waiting on an HSM recall,
the file_name will show the directory created by automount,
but the devno and ino  are unavailable because these
numbers are not known until the file system is mounted.

WAITER(S): user   asid tcb SHR|EXCL age
The file system holding the latch: user
The user ID of the address space.
asid
The address space ID.
tcb
The task.
 SHR|EXCL
Whether the latch is held in shared or exclusive mode.
age
The amount of time users have waited for the file system latch
for waiters. If the time exceeds 99 hours, two asterisks (**)
appear in the hour position.

OTHER WAITING THREADS:     USER   ASID     TCB         PID   
       AGE 
This section shows the remaining waiters that are waiting for
reasons other than the mount latch, outstanding sysplex messages,
or file system latch. user
The user ID of the address space.
asid
The address space ID.
tcb
The task.
 pid
The process ID.
age
The amount of time the user has been waiting. If
the time exceeds 99 hours, two asterisks (**) appear in the hour position. 

TIME: yyyy/mm/dd hh.mm.ss
The date and time when the activity started.
IS DOING: activity / [pfs_qualifier] 
 activity
Description of what the holding task is doing. activity is
displayed as either:  A wait, such as HSM recall when the task is waiting on an HSM
recall
The type of physical file system (PFS) and the operation that
the task was  called to do, such as READ, WRITE, MOUNT, or FSYNCH 

pfs_qualifier
If the activity field shows a PFS, the pfs_qualifier field
shows what the PFS is doing. For example, pfs_qualifier might
show: Running - If the pfs_qualifier field
shows Running for very long, it probably indicates
that the thread is in a PFS wait that cannot be detected by DISPLAY
OMVS.
Osi Wait
XSYS Message to: sysname

FILE: file_name (devno,ino)
For operations on a specific file, this line shows the following
information: file_name
 Up to 16 characters of the file name when this
information is available. 
devno
The device number of the file.
ino
The inode number of the file.
When the waiter is waiting on an HSM recall,
the file_name will show the directory created by automount,
but the devno and ino  are unavailable because these
numbers are not known until the file system is mounted.

FILE SYSTEM: file_system_name
The name of the file system involved, when available.
HOLDING: File System Latch latchno SHR|EXCL
 A file system latch is held by this thread. latchno
The latch number that corresponds to the latch shown by DISPLAY
GRS.
 SHR|EXCL
Whether the latch is held in shared or exclusive mode.

OUTSTANDING CROSS SYSTEM MESSAGES:
SENT SYSPLEX MESSAGES: 
USER   ASID   TCB    FCODE  MEMBER   REQID     MSG TYPE     AGE 
This section displays information about the broadcast messages
sent to another system in the sysplex for which no reply was yet received. 
user
The user ID of the address space.
asid
The address space ID.
tcb
The task.
fcode
The function code being sent.
member
The sysplex member name of the system or systems that sent the
message and from which a reply is outstanding. As replies are received
for broadcast messages, member names are removed from the list.
reqid
The unique request ID of this message. You can use this value
to find the message in the display of RECEIVED SYSPLEX MESSAGES on
the system that received the message.
seqno
The 4-byte hexadecimal sequence number identifying the unique
message buffer. The number is of the form xxyyyyyy,
where xx is the system ID of the sender, and yyyyyy is
the expected sequence number suffix.  This number may be used to correlate
with output from message BPXN004I or BPXN005I, if they exist.  In
some cases, it may be 0.
msg_type
The function that the message is performing.
age
The amount of time the task has been waiting for a reply. If the time exceeds 99 hours, two asterisks (**) appear
in the hour position. 
FILE: file_name (devno,ino)
For operations on a specific file, this line shows the following
information: file_name
 Up to 16 characters of the file name when this
information is available.
devno
The device number of the file.
ino
The inode number of the file.

HOLDING: File System Latch latchno SHR|EXCL
 A file system latch is held by this thread. latchno
The latch number that corresponds to the latch shown by Display
GRS.
 SHR|EXCL
Whether the latch is held in shared or exclusive mode.

RECEIVED SYSPLEX MESSAGES: 
on_tcb   asid tcb 
     fcode member   requid 
  msg_type     age
This section displays the sysplex messages that have arrived at
this system, but that were not yet responded to.
on_tcb
The worker's task TCB address in the OMVS address space.
FROM asid
The address space ID of the message sender.
FROM tcb

fcode
The function code that arrived to be processed. If
preceded by an asterisk(*), the received message is an ASYNC message.
Otherwise, the received message is a SYNC message.
FROM member
The sysplex member name of the system sending the message.
reqid
The unique request ID of this message. You can use this value
to find the message in the display of SENT SYSPLEX
MESSAGES on the system that sent the message.
msg_type
The function that the message is performing.
age
The amount of time the worker task has been processing the message. If the time exceeds 99 hours, two asterisks (**) appear
in the hour position. 
TIME: yyyy/mm/dd hh.mm.ss
The date and time when the activity started.
IS DOING: activity / [pfs_qualifier] 
 activity
Description of what the worker task is doing. activity is
displayed as either: A wait, such as a Latch Wait
 The type of physical file system (PFS) and the operation that
the task was called to do, such as READ, WRITE, MOUNT, or FSYNCH

pfs_qualifier
If the activity field shows a PFS, the pfs_qualifier field
shows what the PFS is doing. For example, pfs_qualifier might
show Running,Osi Wait or XSYS
Message to: sysname.  If the pfs_qualifier field
shows Running for very long, it probably indicates
that the thread is in a PFS wait that cannot be detected by DISPLAY
OMVS.

FILE: file_name (devno,ino)
For operations on a specific file, this line shows the following
information: file_name
 Up to 16 characters of the file name when this
information is available.
devno
The device number of the file.
ino
The inode number of the file.

FILE SYSTEM: file_system_name
The name of the file system involved, when available.
HOLDING: File System Latch latchno SHR|EXCL
 A file system latch is held by this thread. latchno
The latch number that corresponds to the latch shown by Display
GRS.
 SHR|EXCL
Whether the latch is held in shared or exclusive mode.

System action
 The system continues processing.

System programmer response
 Use the displayed information to
determine if users are hung or waiting for either a mount latch or
for replies to sysplex messages. If some tasks appear to be deadlocked,
you can use the information in the display to figure out which tasks
to cancel, in order to clear up the deadlock. 

Module
 BPXOMAST

Source
 z/OS UNIX System Services kernel (BPX) 

Routing Code
 -

Descriptor Code
 -