On Fri, 26 Feb 2016 09:19:53 -0500, Kurt Quackenbush wrote: > >> ... 4- RUN >> APPLY CHECK with BYPASS(DB2BIND,DOC,IPL) and GROUPEXTEND for each PTF >> one by one. > ... >> 5- For those Jobs which the RC=00 run the apply without CHECK. At >> this step some of them finished correct and some gave RC=08 which the >> ERROR was LINK- EDIT. Which it was estrange for me???!!! Whenever >> taking SMPE LIST ERROR the STATUS is REC APP ERR . I don't know >> what to do for this kind off PTFs????? > >Not knowing exactly the state of your target zone and libraries before >this adventure, its possible if you do as I suggest above and apply all >applicable PTFs in a single step, then some of those errors might get >resolved on their own. That is, higher level PTFs supply higher >level MODs that likely contain the references that are missing and >causing the binder errors. > In that case, the PTFs that introduce the Binder errors should, in principle, have been declared PE with those resolving PTFs as REASON, and GROUPEXTEND should resolve the errors. In practice, it's more productive that the customer get current on service.
>Are the regressed and regressing SYSMODs in the report all IBM PTFs? > Always a fair question. Assuming, with reasonable confidence, that the IBM PTFs are structurally correct. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
