On Thu, 17 Nov 2016 12:35:46 -0600, Paul Gilmartin wrote: >o APPLY REDO doesn't always undo the side effects of the prior APPLY. > I suspect this is particularly true if the SYSMOD contains ++*UPD or > ++ZAP or if the newer version contains fewer CSECTs than the > previous and this is what I misremember as "can't RESTORE".
Do you mean, for example, if your PTF included elements A and B, and the updated PTF includes only element A, that the updates from B for the original PTF are still there? Or if the original PTF put element C into target library X and the updated one put C into target library Y? This is not a surprise to me. It is the kind of reason that I don't like to modify a PTF and reapply it with REDO. In fact, I don't like to modify a PTF. In some cases we will do so, but ONLY IF WE ARE CERTAIN that the PTF has not been shipped to any customer. Tom's rule number 1 about creating PTFs: Don't change the PTF! Tom's rule number 2: If you think it is ok to change the PTF this time, refer to rule 1. Tom's rule number 3: If you do change the PTF, despite the first two rules, then RESTORE and REJECT it, then RECEIVE and APPLY, and check all possible permutations. -- Tom Marchant ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
