BPXF083I THE FOLLOWING FILE SYSTEM HAS BEEN QUIESCED FOR MORE THAN 10 MINUTES: filesys_name QUIESCING SYSTEM=sysname JOB=jobname PID=pid LATCH=latnum

Explanation

The file system is quiesced and will not be usable until it is unquiesced.

In the message text:
filesys_name
The file system name.
sysname
The name of the system that executed the job.
jobname
The name of the job that quiesced the file system.
pid
The process ID that quiesced the file system.
latnum
The latch number on this system used to quiesce the file system. z/OS® UNIX System Services uses the specified GRS latch in latchset SYS.BPX.A000.FSLIT.QUIESCE.LSN to prevent I/O operations from being processed by the physical file system.

System action

The file system can't be used.

Operator response

If the condition persists, contact the system programmer.

System programmer response

The file system can only be unquiesced by an authorized user. To unquiesce the file system, use the ISPF Shell (ISHELL) to Reset unmount or quiesce from the Work with Mounted File Systems panel (BPXWP20).

Note that for a shared file system configuration, the attempt to unquiesce a quiesced sysplex root file system will fail if the authorized user ID you use was defined with an OMVS HOME directory, and the user ID is not already active (logged in and dubbed).

Use the D OMVS,U=userid system command to determine if the authorized user is dubbed. In a RACF® environment, issue the following RACF command from the TSO command line to alter a userid to have no HOME directory. 
alu userid omvs(home(''))
Additionally, the ISPF Shell (ISHELL) cannot be used to unquiesce the sysplex root because it attempts to access the root file system resources during its initialization processing. The following REXX exec can be executed from the TSO command line to unquiesce the sysplex root HFS file system with name 'ZOS17.SYSPLEX.ROOT.HFS' . Note that the user ID you use must be a superuser ID (UID=0) with NO HOME directory specified: 
/* REXX */  
address syscall  
call syscalls('ON')  
unquiesce ZOS17.SYSPLEX.ROOT.HFS 1
Alternatively, you can use a non-UID 0 user (with NO HOME directory specified) to unquiesce the file system if the user is permitted to the BPX.SUPERUSER facility class. In this case, the REXX exec must also include a seteuid 0 call, as follows: 
/* REXX */
 address syscall
 call syscalls(’ON’)
 seteuid 0
 unquiesce ZOS17.SYSPLEX.ROOT.HFS 1

Another possible reason that this message is issued is because a backup is currently in progress. If the reason for the quiesce is unknown, search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM® Support Center.

Module

BPXFTSYN

Source

z/OS UNIX System Services kernel (BPX)

Routing Code

2

Descriptor Code

11