*optional* might be debated....I wouldn’t run without. In a sysplex configuration, the alternate sysplex root file system is a hot standby for the sysplex root file system that is used to replace the current sysplex root file system when the sysplex root file system becomes unowned. The alternate sysplex root file system is established by using the ALTROOT statement in the BPXPRMxx parmlib member during OMVS initialization or by using the SET OMVS command.
Requirements: When replacing the sysplex root file system, take the following requirements into consideration: A shared file system configuration is required. However, the sysplex can be a single system. All systems in the shared file system environment must be at z/OS® V1R11 at the minimum. The alternate sysplex root must have the same mount points and symbolic links as the current sysplex root. The mount points are validated during processing, but the symbolic links are not. If mount points are missing, the current sysplex root is not replaced by the alternate sysplex root. The file system type for the alternate sysplex root and the current sysplex root must be either HFS or ZFS. They do not have to be identical. The alternate sysplex root PFS must be active on all systems in the shared file system configuration. If the SECLABEL class is active and the MLFSOBJ option is active, then the multilevel security label for the alternate sysplex root must be identical to the assumed multilevel security label of the current sysplex root. The sysplex root or any directories in the sysplex root file system must not be exported by the DFS or SMB server. The real path name for the mount points in the current sysplex root must not exceed 64 characters in length. Restriction: The ALTROOT statement is ignored during processing of the F BPXOINIT,FILESYS=REINIT system command. You will have to manually issue SET OMVS=(xx) where BXPRMxx is the parmlib member containing the original ALTROOT statement. _____________________________________________________________________________________________________ Dave Jousma AVP | Manager, Systems Engineering Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI 49546 616.653.8429 | fax: 616.653.2717 -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Allan Staller Sent: Wednesday, May 6, 2020 12:30 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ALTROOT **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** This is for recovery and migration purpose. It will allow the sysplex root dataset to be replaced without a sysplex-wide IPL. It is optional and *NOT* required. HTH, -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Steve Beaver Sent: Wednesday, May 6, 2020 11:27 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: ALTROOT [CAUTION: This Email is from outside the Organization. Unless you trust the sender, Don’t click links or open attachments as it may be a Phishing email, which can steal your Information and compromise your Computer.] I have come up against a question that I can't answer. In OMVS why is an ALTROOT needed in a SYSPLEX? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: ________________________________ The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. ________________________________ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
