I'm pretty adamant on this question: I will not bypass an error hold unless Level 2 blesses it. Relying on the error description and the environment it pertains to can be very risky. Error descriptions are often tailored for the customers reporting the problem. You don't want to be grist for the next description update: 'and BTW this problem may affect you in this additional circumstance'. The only valid case I can see for bypass is to install a fix that I absolutely need for an ongoing problem. That is, break-fix, not preventative maintenance. Even then I would still seek the vendor's counsel.
Picture this scenario. Your latest maintenance bundle goes south and causes an outage. The boss invites you drop by and explain what happened. Where would you rather be? 1. Gee boss, I looked at an error hold, decided it didn't pertain to us, and jammed it on over SMPE's objection. 2. I followed the vendor's educated advice and let the process work as designed. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile [email protected] [email protected] > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Staller, Allan > Sent: Tuesday, December 22, 2015 07:00 AM > To: [email protected] > Subject: [Bulk] Re: PTF error clarification > > Research this apar: > > ERROR HOLD AA49159 WAS NOT RESOLVED > > > Either order/install the additional maintenance required *OR* > > *WITH GREAT CARE AND EXTREME DILIGENCE*, determine if the exposure in > this AA49159 will affect you installation. > > If *YES* ****DO NOT**** bypass the error hold. > If *NO*, the error hold can be bypassed on the APPLY. > > e.g. Many times the error holds are associated with a particular feature. If > you > do not have, and are not planning to install this feature, the error hold may > be > safely bypassed. > The fixing PTF will come along in due course and be installed in the normal > maintenance stream. If you have, or are planning to install the feature, then > it is > most likely not a good idea to bypass the error hold. > > Another possibility is to research the PTF chain leading to AA49159. It is > possible > that somewhere in the chain, there is a "stop point" where all prior maint > will go > on with error. IF PTFS in the chain subsequent to the "stop point" are > excluded > from the apply, the earlier PTF's will go on without any issues. > > HTH, > > > <snip> > I am applying few toleration fixes for a hardware but I a receiving the below > error message. > > CAUSER SYSMOD SUMMARY REPORT FOR APPLY CHECK PROCESSING > > CAUSER FMID MESSAGE ID PAGE ERROR DESCRIPTION AND POSSIBLE > CAUSES > > UA90976 HBB7790 GIM35901I 2 ERROR HOLD AA49159 WAS NOT > RESOLVED. > > PAGE 0003 - NOW SET TO TARGET ZONE TZN210 DATE 12/22/15 TIME > 06:33:34 > SMP/E > > > UNRESOLVED HOLD REASON REPORT FOR APPLY CHECK PROCESSING > > NOTE: THE SYSMODS LISTED IN THIS REPORT ALSO APPEAR IN THE CAUSER > SYSMOD SUMMARY > > > HOLD MISSING HELD RESOLVING RESOLVER > > TYPE FMID CLASS APAR SYSMOD SYSMOD STATUS > > ------ ------- ------- ------- ------- --------- -------- > > ERROR HBB7790 PE AA48273 UA90976 UA78633 NOGO(H) > UA78870 NOGO(H) > AA48642 UA90976 UA78971 NOGO(H) > AA48858 UA90978 UA78965 NOGO(H) > AA49159 UA90976 > > ....deleted > > MISSING > APAR > ------- > AA48273 > > AA48642 > AA48858 > AA49159 > > z/OS 2.1 > </snip> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
