IBM Z Hardware and Operating Systems Ideas Portal
This is the public portal for all IBM Z Hardware and Operating System related offerings. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
.This item is not in our plans but is being kept in our backlog.
USS does not recognize the rwshare state change because
there is no support to recognize that. We understand the
requirement to allow dynamic changes between rwshare and
norwshare.
I previously provided additional information as comments, but I have been unable to determine if the comments were saved within this RFE, so I am submitting the additional information again. I apologize if this is a repeat.
I considered what I did to be dynamic because I didn't unmount the zFS filesystem. Let me explain what I did.
We have a test LPAR (MVST) in our sysplex. From the UNIX shell on MVST, I first made MVST temporarily RWSHARE:
zfsadm config -sysplex_filesys_sharemode rwshare
The following message was issued:
IOEZ00300I Successfully set -sysplex_filesys_sharemode to rwshare
Next I verified that the filesystem was not currently sysplex aware:
zfsadm aggrinfo zfs3.all.pfg –long
ZFS3.ALL.PFG (R/W COMP): 22942 K free out of total 293120
version 1.4
auditfid D7C1C6F0 F0F308C5 0000
2810 free 8k blocks; 462 free 1K fragments
720 K log file; 48 K filesystem table
48 K bitmap file
Next I issued a chmount command to move the filesystem to MVST to enable it as sysplex aware:
chmount -d MVST /pfg
Then verify:
zfsadm aggrinfo zfs3.all.pfg –long
ZFS3.ALL.PFG (R/W COMP): 22942 K free out of total 293120
version 1.4
auditfid D7C1C6F0 F0F308C5 0000
sysplex-aware
2810 free 8k blocks; 462 free 1K fragments
720 K log file; 48 K filesystem table
48 K bitmap file
Then since we prefer that MVST does not ‘own' filesystems, I moved the filesystem back to the LPAR that was the owner:
chmount -d MVSB /pfg
Then verified again that the filesystem is still sysplex aware:
zfsadm aggrinfo zfs3.all.pfg -long
ZFS3.ALL.PFG (R/W COMP): 22942 K free out of total 293120
version 1.4
auditfid D7C1C6F0 F0F308C5 0000
sysplex-aware
2810 free 8k blocks; 462 free 1K fragments
720 K log file; 48 K filesystem table
48 K bitmap file
Next I turned off RWSHARE on MVST:
zfsadm config -sysplex_filesys_sharemode norwshare
IOEZ00300I Successfully set -sysplex_filesys_sharemode to norwshare
So based on the output from the zfsadm aggrinfo command, this filesystem is sysplex aware. However, OMVS does not appear to recognize this.
D OMVS,F,NAME=ZFS3.ALL.PFG
BPXO045I 08.52.45 DISPLAY OMVS 118
OMVS 0011 ACTIVE OMVS=(00,F0)
TYPENAME DEVICE ----------STATUS----------- MODE MOUNTED LATCHES
ZFS 158 ACTIVE RDWR 08/01/2015 L=77
NAME=ZFS3.ALL.PFG 21.54.31 Q=0
PATH=/pfg
OWNER=MVSC AUTOMOVE=E CLIENT=N
EXCLUDE SYSTEM LIST: MVSD MVSE MVST MVSI MVSJ
I believe if USS recognized this filesystem as sysplex aware, this output should include a line that says: MOUNT PARM=RWSHARE
In addition, Healthchecker check USS_PARMLIB flags an exception for this filesystem. We have PARM('RWSHARE') coded in BPXPRM00 for this filesystem, but the System Value in the healthcheck says Parm: NONE
If I remember correctly, a co-worker had an issue open with IBM Support 2 or 3 years ago (it may have been longer ago than that) and this is what we were told to do. I believe we were told at that time that USS would not recognize the filesystem as sysplex aware.
I believe this will all get cleaned up when we have all the systems in our sysplex down for the time change in November. However, if zFS recognizes this change without unmounting the file, USS should also be able to recognize this change.
I hope this provides the additional information that you needed.
Thank you.
Carolyn Stirler
What do you mean by dynamically changing a file system to sysplex aware?
There is currently no capability to change a mounted file system from
not sysplex aware to sysplex aware.
Creating a new RFE based on Community RFE #74121 in product z/OS.