Once I get the last of the maintenance I am working on applied, I'll go back and try to apply these again looking for any irregularities with SYS1.NUCLEUS.
On Tue, Mar 4, 2014 at 9:25 AM, Staller, Allan <[email protected]>wrote: > UA69565 closes APAR OA42179 > UA71730 closes APAR OA43690 > > As of a few minutes ago, neither PTF was indicated as a PE. > I checked the cover letters for the z/OS 2.1 versions of those PTF's > (UA69566 and UA71731) and of the 2 I would consider UA71730 the most likely > culprit. > > I would check you apply run for failures during the application of these > PTF's, or bypass of a pre -req. Can you post the SMPOUT from your apply run? > I can't think of anything else that would cause this. > > <snip> > But through some slow application of maintenance I determined the 2 that > PTFs that cause the DW are UA69565 and UA71730. I've no idea why they > cause an issue, but when I apply them I get the DW. To make it even more > odd is those PTFs are applied to other z/OS 1.13 systems I run. > </snip> > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- The postings on this site are my own and don't necessarily represent Mainline's positions or opinions Mark D Pace Senior Systems Engineer Mainline Information Systems ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
