The way I did it,
Major release new res pack.
PTF’s (this is a depends). Example ICKDSF (IIRC) has one module I copy the old
version to my private library and update the new version and do a F LLA,refresh.
Jes2 is funny the way I do it and it depends on either the HOLD data or
verbiage in the cover letter, and it depends on the modules it hits.
If its in LPA I copy the old version to MLPA and create a parmlib member
for it (this is for a quick IPL backout) If hits JES2 I keep a old copy before
the apply into my own library then apply the main and copy it into Linklib and
then either IPL or $Pjes2 then s JES2. It also depends on if other people are
working on the same issue. I get everyone together and tell them where the
back out is and if there are special issue that we have to be concerned about.
I try and keep PTF’s to a 1 digit number if its a RSU then I create a new
respack.
If it gets complicated I create a new res pack.
I would say it depends on the fix going one, if its say to GDDM or another
small product. I back the entire library up and then apply maintenance, but
usually it can be installed without an IPL then I use the KISS methodology.
In any case I keep a second person involved and he/she understands on how the
fix is going on as I explain it.
This works even if we both drop dead as a third person is kept in the loop by
email, not necessarily by phone.
Ed
> On Sep 24, 2017, at 11:27 PM, Peter <[email protected]> wrote:
>
> Hi
>
> Whenever we moved to the higher version of zOS we have applied the
> toleration maintenance but never applied fallback.
>
> Fallback is something when we have to move back to the previous version.
>
> So to my understanding if we can Backout all the changes to the previous
> level then how does fallback PTF helps ?
>
> What exactly the fallback PTF does interns of Backout ? Can someone please
> help me to understand.
>
> Regards
> Peter
>
> ----------------------------------------------------------------------
> 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
