I agree with others that you may not be able to have your z/OS V1.11 system in this plex with z/OS V2.1.
In the text of the APAR on IBM.COM it states PTF List: Release 750 : UA68052 available 13/03/12 ( ) Release 760 : UA68053 available 13/03/12 ( ) Release 770 : UA68054 available 13/03/13 (F303 ) Release 780 : UA68055 available 13/03/13 (F303 ) I think when there is nothing behind the parentheses - there are NO PTFS for z/OS V1.11 (UA68053) and z/OS V1.10 (UA68052). From what I have reviewed they were both cancelled. Starting in z/OS V2R1, JES2 will only be supported if it is the level that was shipped with the active MVS. If JES2 and MVS are not at the appropriate z/OS level a "$HASP2101 JES2 level (HJExxxx) IS NOT SUPPORTED RUNNING ON mvs_level" message will be issued at initialization to indicate the mismatch, and a "$HASP2102 REPLY "CONTINUE" TO INITIALIZE JES2 IN THIS UNSUPPORTED ENVIRONMENT, "TERM" TO SHUT DOWN JES2" message will be issued to accept an operator reply. The operator will need to reply "TERM" to terminate JES2 initialization. The operator will need to reply "CONTINUE" to allow the JES2 initialization to complete. Initializing in this environment may cause errors in applications that use JES2 services. Starting in z/OS V2R1, JES2 supports a new data structure in a JES2 checkpoint, a JOE index, which is used to optimize SYSOUT work selection. When a pre-z/OS V2R1 member joins the MAS, the JOE index is suspended. This does not have a functional impact. However, z/OS V2R1 members in the MAS will not benefit from the performance improvement of the JOE index until all pre-z/OS V2R1 members in the MAS are upgraded to V2R1 (or leave the MAS) and the JOE index is rebuilt. >From Marna Walle' Presentations - z/OS V1R13 is the last release to support a staged migration for JES2 and JES3. As of z/OS V2R1, you must migrate to all elements of z/OS at the same time, including JES2, JES3, or both. As of z/OS V1R2, compliance to the coexistence, fallback, and migration policy for JES2 and JES3 is enforced. A migration to a JES2 or JES3 release level that is not supported by the policy results in the following: . For JES2: If the JES2 release level for a system that is initializing is not compatible with the other active systems in the JES2 MAS, message HASP710 is issued and the JES2 address space for the initializing system is terminated. JES2: Verify z11 checkpoint level JES2_Z11_UPGRADE_CK_JES2 (no APAR) ACTIVE LOW For z/OS R11 and Beyond Use the $D ACTIVATE command. This command indicates if activation to z11 level will succeed. z/OS V1R11 25 September 2009 Occurred 30 September 2012 * *See "z/OS V1.11 Lifecycle Extended Service" below for a fee-based accommodation, through 30 September 2014. .If you are running z/OS R11 and would like coexistence support, plan for a migration to z/OS R13. Thus, z/OS V2R1 is coexistence, fallback, and migration supported with the following two z/OS releases: V1R13 and V1R12. This means that: . Coexistence of a V2R1 system with a V1R13 or V1R12 system is supported. . Fallback from V2R1 to V1R13 or V1R12 is supported. . Migration to V2R1 from V1R13 or V1R12 is supported. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of venkat kulkarni > Sent: Thursday, January 09, 2014 6:55 AM > To: [email protected] > Subject: Re: z/OS 2.1 toleration PTFs > > Hello, > Yes, FIXCAT report run good on z/OS 1.11 but when I tried downloading PTF > mentioned in this report using Shopzseries, I got below error. > > SDF Order# was Rejected at 00:23:04 01/09/2014 UA68053 (ORDERED) <<-- Fix > not found UA68449 (ORDERED) <<-- Fix not found UA68484 (ORDERED) <<-- > Fix not found UA68642 (ORDERED) <<-- Fix not found UA68647 (ORDERED) <<- > - Fix not found UA68660 (ORDERED) <<-- Fix not found UA68664 (ORDERED) > etc..... > > Yes, I did same with z/OS 1.13 and downloaded PTF mentioned in FIXCAT report > and I was able to download using Shopseries. > > But all these PTF are mentioned are coexistence PTFs. But My idea was to atleast > make this sysplex work with (z/OS 1.11, z/OS 1.13,z/OS 2.1) > > using toleration PTFs and then we can apply coexistence PTFs, if required. > > Please suggest. > > > > On Thu, Jan 9, 2014 at 7:06 PM, Richards, Robert B. <[email protected] > > wrote: > > > For starters, I would APPLY CHECK and then APPLY *ALL* "good" and > > RECEIVE "yes" PTFs. > > While that is running, order the "good" and RECEIVE "no" PTFs. Once > > they are received, APPLY CHECK and APPLY them. > > Rerun the FIXCAT report. > > > > Do you receive the enhanced "FULL" holddata on a daily basis? If not, > > start to do so. > > > > Run the same process against your 1.13 SMP/E system. > > > > Ignore toleration and coexistence at your own peril. There are reasons > > they are there. > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
