Classification: Confidential I use "X-PARM" and "X-PROC" to support concurrent parmlib's SYS1.&lpar.(PARM/PROC)LIB is searched first SYS1.(PARM/PROC)LIB is searched next. SYS1.IBM.( PARM/PROC)LIB is searched last.
Normally, everything in (PARM/PROC) is identical within the sysplex. At need, a unique (PARM/PROC) member can be created and will be found first. At some later time, (after rollout complete) the changed (PARM/PROC)s in SYS1.&lpar can be returned to SYS1. This also allows for :"permanent discrepancies" to be accommodated. My USD $0.05 (inflation) worth. -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Pommier, Rex Sent: Tuesday, September 3, 2024 11:58 AM To: [email protected] Subject: Re: [EXTERNAL] Upgrading z/OS vs. z/VM [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.] Almost the same here. IPLPARM and PROCLIB are not on res pack. PARMLIB is - with the indirect cataloging. That way I can have my new PARMLIB (pointing to new BPXPRMxx for example) ready to go. Side story, when I first started here 11 years ago, they were doing upgrades exactly like Phil described. Upgrading all third party products and the OS at the same time, complete clone of all data volumes and everything. Weekend nightmare to go thru. I sat my new coworkers (and manager) down and explained to them how much safer and easier it was to upgrade a third party product at a time, get them out of the way ahead of time, then just upgrade the OS and leave everything else the same. They were skeptical - until I dropped the first OS upgrade in and showed them how much easier it is this way. 😊 Rex -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Allan Staller Sent: Tuesday, September 3, 2024 11:43 AM To: [email protected] Subject: Re: [EXTERNAL] Upgrading z/OS vs. z/VM Classification: Confidential Have no clue about AD/CD configuration. As I stated earlier, just point to new sysres and IPL. In my configuration PARMLIB/PROCLIB/IPLPARM *ARE NOT* on the sysres. HTH, -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Phil Smith III Sent: Tuesday, September 3, 2024 11:35 AM To: [email protected] Subject: Re: [EXTERNAL] Upgrading z/OS vs. z/VM [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.] Ok, that's interesting. Maybe we're more constrained because it's an ADCD image? -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Pommier, Rex Sent: Tuesday, September 3, 2024 11:38 AM To: [email protected] Subject: Re: [EXTERNAL] Upgrading z/OS vs. z/VM Phil, I'm going to give you a qualified "nope" here. Granted I work at a small site - 2 production LPARs and a sandbox, no shared anything, no sysplex yadda yadda yadda. We currently have 3.1 sitting on a mod27 volume (with its unix filesystem datasets that shipped with it ready to go). Had to put new catalog entries into the master for the new USS datasets and new libraries on the RES pack - using indirect cataloging for it. IPLed 3.1 and ran for a few hours before we hit a snag that forced us to back out to 2.4. Backout was simply shutting down, pointing the hardware to the 2.4 SYSRES and IPLing. No messing with spool or anything else. Just need to make sure fallback maintenance is in place. Rex -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Phil Smith III Sent: Tuesday, September 3, 2024 10:20 AM To: [email protected] Subject: [EXTERNAL] Upgrading z/OS vs. z/VM I'm NOT trying to start a war here, just trying to grok whether I'm confused or not. I will make assertions below, any/all of which may be wrong, but that seems better than qualifying each with "I think..." etc. Upgrading z/VM versions has been pretty trivial for quite a while: point to a new CP module, reIPL. Upgrading z/OS is a lot harder. There's no way to just swap the OS itself, which means you need to clone the LPAR and then connect the user data volumes, with required catalog tinkering. And SPOOL needs to be backed up and restored (or contents lost). Is this really still true in 2024? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] 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 [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
