Re: PTF Rollback Ideas

[Jack Kingsley <iseriesflorida@xxxxxxxxx>]

You don't mention what type of PTF's that they were, cume, groups, etc.
Have you been able to narrow it down or not really based on your number of
127.  Did you apply these to any lower environments first and test with
them, did you see the same results.  You also didn't mention what the
vendor is doing about the problem. In the article below they don't mention
using RMVPTF.

There is this if it helps.
https://www-01.ibm.com/support/docview.wss?uid=nas8N1014960



On Tue, Aug 13, 2019 at 7:52 PM Krill, Coy <CKrill@xxxxxxxxxxx> wrote:

> Recently made the mistake of applying some PTFs that had not yet been
> vetted by our vendor (I'm, lucky if they vet a CUME per year these days)
> and have now had two weeks of production impact with what appears to be
> slow record lock releases. I'm in limbo between IBM and my vendor at the
> moment as IBM has now decided it's probably an issue in the vendors code,
> however, they keep focusing on some SQL action that isn't part of the
> problem. The problem is two RPG programs where program 1 updates a record
> and then calls the next program to do another update to the same record.
> This worked fine until I loaded some group PTFs.
>
> All that preamble to get to my question. I want to roll these off. It's
> been probably 20+ years since I've had to back off PTFs and never about 127
> of them to roll it all back. Is there any kind of automated way of
> determining the right/best sequence for unrolling them? Anybody had to do
> this in recent years?
>
> Coy Krill
> Core Processing Team Lead
> Washington Trust Bank
>
>
> This electronic mail message and any attachments may contain confidential
> or privileged information and is intended for use solely by the
> above-referenced recipient. Any review, copying, printing, disclosure,
> distribution, or other use by any other person or entity is strictly
> prohibited under applicable law. If you are not the named recipient, or
> believe you have received this message in error, please immediately notify
> the sender by replying to this message and delete the copy you received
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com