I did that, it didn't change from what I could see. I might open a question to
IBM support. See what they say.
Mark Jacobs
Sent from ProtonMail, Swiss-based encrypted email.
GPG Public Key -
https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com
--- Original Message
On Mon, 20 Mar 2023 14:42:41 +, Mark Jacobs
wrote:
>Thanks, no I didn't think of the chmount command. I ran a test on my sandbox.
>the /u directory is showing that automove will exclude the system I specified,
>but the file systems mounted under it don't show that attribute, just
Thanks, no I didn't think of the chmount command. I ran a test on my sandbox.
the /u directory is showing that automove will exclude the system I specified,
but the file systems mounted under it don't show that attribute, just
Automove=Y. Do I need to change the mount attribute for all
On Mon, 20 Mar 2023 13:04:44 +, Mark Jacobs
wrote:
>Thanks, but that's not helpful in my situation. The problematic file system is
>under /u which is under the sysplex root, That has to be automove.
>
>Mark Jacobs
>
Correct. Then the only way to "avoid" a lpar is to avoid it with the
Thanks, but that's not helpful in my situation. The problematic file system is
under /u which is under the sysplex root, That has to be automove.
Mark Jacobs
Sent from ProtonMail, Swiss-based encrypted email.
GPG Public Key -
On Mon, 20 Mar 2023 12:03:28 +, Mark Jacobs
wrote:
>I've been looking at that and testing somethings in our sandbox environment.
>The problematic file system that's already impacted us twice is being managed
>by automount and I can't see anyway to instruct OMVS not to automove
I've been looking at that and testing somethings in our sandbox environment.
The problematic file system that's already impacted us twice is being managed
by automount and I can't see anyway to instruct OMVS not to automove
filesystems that are managed by the automount policy.
Mark Jacobs
This link has more details about file system movement/ownership during recovery
scenarios.
https://www.ibm.com/docs/en/zos/2.4.0?topic=recovery-managing-movement-data
--
For IBM-MAIN subscribe / signoff / archive access
Check the INCLUDE/EXCLUDE parameters on the MOUNT statements in BPXPRMxx
https://www.ibm.com/docs/en/zos/2.4.0?topic=parameters-statements-bpxprmxx
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to
When the owning system is removed from the sysplex is there a way to influence
which remaining systems becomes the owner of the file system? I'd like a way to
tell OMVS not to assign any automoved file systems to one specific system in
the sysplex.
Mark Jacobs
Sent from
10 matches
Mail list logo
