We’ve been shared ZFS for quite awhile now. If you wish to reach out off-list I’ll be glad to do a back-and forth.
_______________________________ Dave Jousma Vice President | Director, Technology Engineering Fifth Third Bank | 1830 East Paris Ave, SE | Grand Rapids, MI 49546 From: IBM Mainframe Discussion List <[email protected]> on behalf of Steely.Mark <[email protected]> Date: Thursday, October 16, 2025 at 3:52 PM To: [email protected] <[email protected]> Subject: Shared ZFS CAUTION EXTERNAL EMAIL This message came from outside your organization. DO NOT open attachments or click on links from unknown senders or unexpected emails. Report Suspicious<https://us-phishalarm-ewt.proofpoint.com/EWT/v1/MwwqYLOC6b6whF7V!odOElr-FgiBBXko5TJjPeTB9oyQe5yXpA_AIQpNmFatEAuGgEt0jmsCQ-FPgtFjkxzVQxKBsq8v0c3XAQWLmbditiYtY8BVpEmkwJd4_V1sFUKxY3PNhmrCcVV85BuePKgqU5sOijltwUA$> The environment is currently running z/OS V3.1 and we plan to implement a shared zFS file system across our SYSPLEX of four LPARs. I am seeking step-by-step accounts from anyone who has completed a similar implementation. Background and findings so far: * We have a SYSPLEX with four LPARs. * Preliminary research indicates the following items must be addressed: * SYSPLEX root file system configuration * System-specific file system configuration on each LPAR * Creation and allocation of the CDS. * BPX parameters update - SYSPLEX(YES) SYSNAME(&SYSNAME) AUTOMOVE. Questions and primary concern: * What is the recommended sequence of events to enable shared zFS in a SYSPLEX? * Do all LPARs have to be updated or IPLed simultaneously to enable sharing, or can this be accomplished by updating one LPAR at a time? * Is it safe to leave the current zFS filesystems in place and then unmount/remount the filesystems to change sharing modes when the shared configuration is ready? Thank You ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
