While I also would not trust is system, I do trust SMP/E. After running the APPLY EXCLUDING the PTF(s) with errors, he can run the SMP/E report of errors on his system. He can research the errors and possibly RESTORE those he just put on if they sound like they cause aprolem he is likely to encounter,
> -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Lizette Koehler > Sent: Friday, September 05, 2014 8:19 AM > To: [email protected] > Subject: Re: RSU APPLY ISSUE GIM23911E > > You do not know if your system is good or not. > > It is better to open a case with IBM and ask for Language Environment > to check. If you do not want to do this, then start over. > > That means you should have > 1) Backed up your SMPE Environment (Both Tlibs, Dlibs and all > associated SMPE libraries) before starting maintenance. > > 2) If not, you may need to delete your environment and start from > scratch. > > Basically you have put your SMP/E environment in a bad state. I am > sure many on this list has done this at one time or another. > > Therefore you need to get back to a good point in time and then start > again. Do not bypass any HOLDERRORs in the future. > > Lizette > > > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] > > On Behalf Of Mainframe Mainframe > > Sent: Friday, September 05, 2014 7:28 AM > > To: [email protected] > > Subject: Re: RSU APPLY ISSUE GIM23911E > > > > Thanks all for reply. Now to resolve this issue, I tried running > below more steps. > > > > 1) I run APPLY CHECK Job without HOLDERROR included in it. Job failed > > with RC 08 > > > > GIM69168E ** HFSCOPY PROCESSING TO THE SIZUFSC LIBRARY FAILED FOR HFS > > IZUGNAAC > > IN SYSMOD UI16044. THE RETURN CODE (12) EXCEEDED THE > > ALLOWABLE > > VALUE. DATE 14.247 - TIME 23:39:39 - SEQUENCE NUMBER > 000025. > > GIM30216I APPLY PROCESSING FAILED FOR SYSMOD UI16044. SYSTEM > > UTILITY > > PROCESSING FAILED FOR AN ELEMENT IN UI16044. > > GIM30219E ** APPLY PROCESSING FAILED FOR SYSMOD UI18572. > > PROCESSING FAILED FOR > > SYSMOD UI16044, WHICH WAS SPECIFIED ON THE ++VER PRE > > OPERAND. > > GIM30221E ** APPLY PROCESSING FAILED FOR SYSMOD UI16025. > > PROCESSING FAILED FOR > > SYSMOD UI16044, WHICH WAS SPECIFIED ON THE ++VER REQ > > OPERAND. > > GIM30221E ** APPLY PROCESSING FAILED FOR SYSMOD UI16026. > > PROCESSING FAILED FOR > > SYSMOD UI16044, WHICH WAS SPECIFIED ON THE ++VER REQ > > OPERAND. > > GIM30221E ** APPLY PROCESSING FAILED FOR SYSMOD UI16027. > > PROCESSING FAILED FOR > > SYSMOD UI16044, WHICH WAS SPECIFIED ON THE ++VER REQ > > OPERAND. > > GIM30221E ** APPLY PROCESSING FAILED FOR SYSMOD UI16028. > > PROCESSING FAILED FOR > > SYSMOD UI16044, WHICH WAS SPECIFIED ON THE ++VER REQ > > OPERAND. > > GIM30221E ** APPLY PROCESSING FAILED FOR SYSMOD UI16029. > > PROCESSING FAILED FOR > > SYSMOD UI16044, WHICH WAS SPECIFIED ON THE ++VER REQ > > OPERAND. > > GIM30221E ** APPLY PROCESSING FAILED FOR SYSMOD UI16030. > > PROCESSING FAILED FOR . . . . . . . . . . . . . . . . > . . . . . . . . . > > . . > > Then I tried looking at UI16044 PTF in SMPPTS and this is basically > > for z/OSMF and we are not using this product.So, I tried EXCLUDING > and > > run Job again. This time it failed with > > > > GIM30204E ** APPLY PROCESSING FAILED FOR SYSMOD UI18572. > > REQUIRED SYSMODS WERE > > EXCLUDED. > > GIM35905I PREREQUISITE SYSMOD UI16044 WAS EXCLUDED. > > > > And UI18572 also belongs to z/OS MF. So, I EXCLUDED this as well from > > APLLY CHeck Job and run with RC00. > > > > Is it good way to bypass the issue, I am facing or Do I have to solve > > it now before moving forward. > > > > Suggestion Please. > > > > > > On Fri, Sep 5, 2014 at 7:36 PM, Tom Marchant < 0000000a2a8c2020- > dmarc- > > [email protected]> wrote: > > > > > On Fri, 5 Sep 2014 06:56:17 -0700, Lizette Koehler wrote: > > > > > > >Do not change the CEEPLPKA. IBM sets that and probably requires it > > > >to be > > > a 0 max cc. > > > > > > > >So, try the apply without the BYPASS HOLDERROR and see if it > works. > > > > > > We don't know the state of his system. Those APARs are likely not > > > for LE, but for some other component. His APPLY failed, but we > don't > > > know what was done when he ran the APPLY with BYPASS (HOLDERROR). > > > The > > > PTF(S) with the error holds may or may not have been applied. > > > > > > At this point, I wouldn't trust his system. > > > > > > -- > > > Tom Marchant > > > > > ---------------------------------------------------------------------- > 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
