Hi Jake, I work on CA Allocate and CA Disk. From a customer perspective you can apply the compatibility PTFs for a new z/OS release to these products and continue to run on the current z/OS release. We assemble the compatibility PTFs with macros from the new release. Outside of the macros, we do not make any copies of new or old release environments. Before we make the compatibilty PTFs available, we test on the new z/OS and all current z/OS releases.
When we do have to publish PTFs for a new release of z/OS, we supply fixcat holddata so that you don't need to visit the support webpage of each product and do a cut and paste of PTF numbers. For example, the fix category for z/OS 2.3 is "CA.TargetSystem-RequiredService.z/OS.V2R3". All of our PTF delivery methods (CA Support online, MSM, and RECEIVE ORDER) are capable of delivering the prereqs along with the compatibility PTF. Bob Longabaugh Broadcom Storage Management On Fri, Feb 8, 2019 at 10:16 AM Carmen Vitullo <[email protected]> wrote: > That is the intent of toleration or coexistence mant or PTF's for the > running system, not the system or zone you are about to install. if you > have a 2.3 zone, you'll prolly see the PTF will not receive or apply ++NO > APPLICABLE VERS, toleration is for the system you are currently running > > Carmen Vitullo > > ----- Original Message ----- > > From: "Jake Anderson" <[email protected]> > To: [email protected] > Sent: Friday, February 8, 2019 10:08:29 AM > Subject: Re: General question about toleration maintenance > > Hi > > Apology for not being clear > > For example a product with a toleration maintenance PTF UAXXXX supplied > to run on z/OS 2.3. > > Currently the product is running on zOS 2.2. > > My question is PTF UAXXXX can be applied even if the z/OS operating system > is 2.2 without the need of z/OS 2.3 library ? > > As I had a curiousity if the PTF needs zOS 2.3 maclibs to assemble and > linkedit the new module ? or the ISVs build the PTF in their own zOS 2.3 > environment and supply it along with PTF ? > > > > > > > > > > On Fri, 8 Feb, 2019, 8:00 PM Joel C. Ewing <[email protected] wrote: > > > On 2/8/19 7:13 AM, R.S. wrote: > > > W dniu 2019-02-08 o 02:01, Jake Anderson pisze: > > >> Hi, > > >> > > >> When a toleration maintenance(PTF) is made for a product to support > new > > >> z/OS release. Is it always we need the z/OS new release library to be > > >> present or to be updated in products DDDEF while apply toleration PTF > > >> ? Or > > >> else vendor would have already assembled and made the load module in > PTF > > >> and it just gets copied to target library without the need of > > >> assembly and > > >> link edit ? > > > > > > Honestly,... I don't understand your English. > > > What is the question? > > > > > > Any PTF is for some product. It does modify (or add) product > libraries. > > > The way how it's applied depends on PTF content. > > > > > As near I decipher the orginal question, what was meant was: > > I have product A, I plan to install product B, there is toleration > > maintenance for product A to tolerate product B, do I need anything > > associated with product B in order to install toleration maintenance for > > A. > > > > The answer is NO. Any toleration maintenance for product A is for the > > FMIDs associated with product A and is only dependent on product A and > > any pre-requisite/co-requisite products you already have installed for > > product A and the SMP/E zones and data sets associated with product A. > > > > This is true whether the products involved are versions of z/OS or some > > other product. You generally need the toleration PTFs in place for A > > before running version B against any production volumes or data used > > with version A. This is true whether you plan to run both versions A > > and B concurrently, or just serially as in upgrading from A to B. One > > rare possibility you should always be prepared to deal with is finding > > some issue unique to your installation that cannot be quickly resolved > > that might force you to revert back to version A after your data and > > volumes have been touched and potentially changed using version B. > > JC Ewing > > > > -- > > Joel C. Ewing > > > > ---------------------------------------------------------------------- > > 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 > > > ---------------------------------------------------------------------- > 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
