z/OS MVS System Messages, Vol 3 (ASB-BPX)
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


BPXF041I

z/OS MVS System Messages, Vol 3 (ASB-BPX)
SA38-0670-00

BPXF041I
timestamp MODIFY BPXOINIT,FILESYS=DISPLAY,GLOBAL text

Explanation

In the message, text is:
SYSTEM   LFS VERSION   ---STATUS------------ RECOMMENDED ACTION
system   ver  pro mod  sysstatus                           action
CDS VERSION=cdsver       MIN LFS VERSION=  ver   pro   mod
BRLM SERVER=brlmsysname  DEVICE NUMBER OF LAST MOUNT=lastmountdevice
MAXIMUM MOUNT ENTRIES=maxmounts     MOUNT ENTRIES IN USE=activemounts
MAXIMUM AMTRULES=maxamtrul          AMTRULES IN USE=amtrulinuse
DISTBRLM ENABLED=YES|NO|N/A             DISTBRLM ACTIVE=YES|NO
serializationcategory
  (Since datetime)
    sysname      sysname     sysname     sysname  sysname    sysname
  FILESYSTEM NAME=fsname
  NUMBER OF UNMOUNTS IN PROGRESS=numunmounts
queuename
cattype                   execution  

   

In response to a MODIFY BPXOINIT,FILESYS=DISPLAY,GLOBAL command, this message displays system information about the z/OS® UNIX System Services member status of each system in the SYSBPX sysplex group.

In the message text:

timestamp
The date and local time for the MODIFY command output. The date is represented as year/month/day, and the time is represented as hours (00–23), minutes (00–59), and seconds (00–59).
system
The name of the system in the sysplex for which status is being provided.
ver
The LFS functional capability version.
pro
The LFS protocol version.
mod
The LFS protocol modification level.
sysstatus
One of the following:
VERIFIED
Sysplex and local state are consistent.
SYSTEM NAME INCONSISTENT
The system name is inconsistent between the sysplex representation and the local representation.
MEMBER TOKEN INCONSISTENT
The member token is inconsistent between the sysplex representation and the local representation.
SYSTEM ID INCONSISTENT
The system ID is inconsistent between the sysplex representation and the local representation.
action
One of the following:
NONE
There is no recommended recovery action to take.
FIX
There is an inconsistency in the sysplex representation of this system.

Use the MODIFY BPXOINIT,FILESYS=FIX system command to further diagnose and possibly correct this inconsistency.

After performing the FIX function, if the inconsistency persists, a restart of the named system may be required to correct the error.

cdsver
The version of the type BPXMCDS couple dataset.
brlmsysname
The name of the system in a z/OS UNIX System Services sysplex that is functioning as the Byte Range Lock Manager server. brlmsysname = 'N/A' when either no z/OS UNIX System Services sysplex is active, or when the distributed BRLM function is active in z/OS UNIX System Services sysplex.
lastmountdevice
The device number of the last file system mounted in the sysplex.
maxmounts
The maximum number of file systems that can be mounted in the active type BPXMCDS couple data set. This value corresponds to the NUMBER parameter specified in the MOUNTS item name statement in the JCL used to format the type BPXMCDS couple data set. See SYS1.SAMPLIB(BPXISCDS) for a sample JCL job.
activemounts
The number of mount entries in the active type BPXMCDS couple data set that are in use.
maxamtrul
The maximum number of automount rules defined for the type BPXMCDS couple data set. This value corresponds to the NUMBER parameter specified in the AMTRULES item name statement in the JCL used to format the type BPXMCDS couple data set. See SYS1.SAMPLIB(BPXISCDS) for a sample JCL job.
amtrulinuse
The number of automount rules in the active type BPXMCDS couple data set that are in use. An automount rule is required for each generic or specific entry in an automount map file.
DISTBRLM ENABLED=YES|NO|N/A
YES indicates that Distributed BRLM is enabled in the shared file system Configuration. This value corresponds to a NUMBER(1) value specified in the DISTBRLM item name statement in the JCL used to format the type BPXMCDS couple data set. See SYS1.SAMPLIB(BPXISCDS) for a sample JCL job.

NO indicates that Distributed BRLM is not enabled in the shared file system configuration. This value corresponds to a NUMBER(0) value specified or defaulted to in the DISTBRLM item name statement in the JCL used to format the type BPXMCDS couple data set. See SYS1.SAMPLIB(BPXISCDS) for a sample JCL job.

N/A indicates that the DISTBRLM indicator in BPXMCDS is ignored.

DISTBRLM ACTIVE=YES|NO
YES indicates that Distributed BRLM is active on all systems in the shared file system configuration.

NO indicates that Distributed BRLM is not active in the shared file system configuration.

serializationcategory
One of the following:
SYSTEM PERFORMING INITIALIZATION
This entry lists the system that is performing file system initialization.
SYSTEM PERFORMING MOVE
This entry lists the system that is in the process of moving ownership of a file system to another system.
SYSTEM PERFORMING QUIESCE
This entry lists the system that is in the process of quiescing a file system that it serves.
SYSTEMS PERFORMING UNMOUNT
This entry lists the systems that are in the process of unmounting one or multiple file systems that they serve.
SYSTEMS PERFORMING MOUNT RESYNC
This entry lists the systems that are in the process of updating their local file system hierarchy to be consistent with the file system hierarchy.
SYSTEMS PERFORMING LOCAL FILE SYSTEM RECOVERY
This entry lists the systems that are in the process of performing local file system recovery resulting from a system exiting the SYSBPX sysplex group.
SYSTEMS PERFORMING FILE SYSTEM TAKEOVER RECOVERY
This entry lists the systems that are in the process of performing file system takeover recovery resulting from a system exiting the SYSBPX sysplex group.
SYSTEMS RECOVERING UNOWNED FILE SYSTEMS
This entry lists the systems that are in the process of performing file system takeover recovery for one or more unowned file systems.
SYSTEMS PERFORMING REPAIR UNMOUNT
This entry lists the systems that are in the process of performing a repair unmount, which is initiated as a result of MODIFY BPXOINIT,FILESYS=FIX or FILESYS=UNMOUNTALL system command, or a similar file system diagnostic function.
SYSTEM PERFORMING REMOUNT
This entry lists the system that is in the process of remounting a file system.
datetime
The date (year/month/day) and time in hours (00–23) minutes (00–59), and seconds (00–59) that this category of processing was started.
sysname
The name of the system associated with the event.
fsname
The name of the file system associated with this event.
numunmounts
The number of file systems that are in the process of being unmounted.
queuename
One of the following:
ACTIVE QUEUE
This entry lists the active serialization categories.
PENDING QUEUE
This entry lists the pending serialization categories.
cattype
One of the following:
MOUNT RESYNC
One or more systems are in the process of updating their local file system hierarchy to be consistent with the sysplex hierarchy.
UNMOUNT
One or more systems are in the process of unmounting one or more file systems.
UNOWNED RECOVERY
One or more systems are in the process of recovering unowned file systems.
MOVE
A system is in the process of moving ownership of one or more file systems to another system.
UNMOUNT SUBTREE
One or more file systems are in the process of being unmounted.
RECOVERY
One or more systems are in the process of recovering file systems. This is performed as part of partition recovery.
INTERVAL
One or more systems are waiting for an interval when there is no serialized shared file system activity in progress.
REMOUNT
A system is in the process of remounting a file system.
**INVALID**
An invalid value was found.
execution
One of the following:
EXCLUSIVE
One operation in this serialization category is allowed.
SHARED
Multiple, concurrent operations in this serialization category are allowed.

System action

The system continues processing.

Operator response

None.

System programmer response

None.

Module

BPXTXRDA

Source

z/OS UNIX System Services kernel (BPX)

Routing Code

-

Descriptor Code

5,8

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014