Hello, I used to use http://www-969.ibm.com/software/reports/compatibility/clarity/index.html for these kind of reports, however it currently looks down to me....
------------------------------------------------------------------------------------------------------------------------------- *Lucas Rosalen* Emails: [email protected] / *[email protected] <[email protected]>* LinkedIn: http://br.linkedin.com/in/lrosalen Phone: +48 792 809 198 2016-02-01 16:17 GMT+01:00 Lizette Koehler <[email protected]>: > If you have the latest hold data, then you can use FIXCAT to find what you > are looking for. > > A fix category is an identifier used to group and associate PTFs to a > particular category of software fixes. A fix category might be used to > identify a group of fixes that are required to support a particular > hardware device, or to provide a particular software function, similar to > how a preventive service planning bucket (PSP-bucket) identifies a group of > PTFs. Fix categories are supplied to you in the form of SMP/E FIXCAT > HOLDDATA statements. Each FIXCAT HOLDDATA statement associates an APAR and > its related fixing PTF to one or more fix categories. > > During SMP/E RECEIVE command processing, SMP/E translates fix category > values into source IDs and assigns them to the resolving (fixing) PTFs > identified on the HOLDDATA. You can then use the fix category values as > source IDs when selecting a set of PTFs to be applied. For example, if you > have a z/OS V1.13 target zone named ZOSR13T, you can attempt to install all > required coexistence and fallback fixes for z/OS V2.2 that have already > been received by using the following command: > > SET BDY(ZOSR13T). > APPLY SOURCEID(IBM.Coexistence.z/OS.V2R2) > CHECK. > > In addition, the SMP/E REPORT MISSINGFIX command can be used to identify > PTFs for interesting fix categories that are missing in one or more target > zones. In this case only the latest HOLDDATA needs to be received and not > the individual resolving PTFs. For example, using the same zone as > described above, you can identify all required coexistence and fallback > fixes for z/OS V2.2 that are not yet applied in the ZOSR13T zone by using > the following command: > > SET BDY(GLOBAL). > REPORT MISSINGFIX ZONES(ZOSR13T) > FIXCAT(IBM.Coexistence.z/OS.V2R2). > > Lizette > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] On > > Behalf Of zos reader > > Sent: Monday, February 01, 2016 8:05 AM > > To: [email protected] > > Subject: z/OS 2.2 compatibility check for IBM Products > > > > Hi All, > > > > I am doing my per-works for upgrading z/OS 2.1 to 2.2. before May, > > > > Few of the Ibm Products are in n-2 and n-3 level, so i planning to apply > PTF's > > and proceed my OS upgrade. > > > > I am looking into the IBM site, but i couldn't find the exact path that > lists > > the required PTF's for the IBM Products > > > > Can anyone have the link or any useful data that would help me more > > > > Please provide your valuable inputs. > > > > Thanks, > > Samat > > > > ---------------------------------------------------------------------- > 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
