The SQL function is how I got the list of what was actually applied. Made it very easy to get a list, that's why I was hoping IBM could point to a clear path but they didn't respond to my request for help in unrolling them.
Our vendor would prefer we get it fixed. They're actually happy we have the issue because we were the second reporter and they were about to vet the latest cume and have people install before end of year. That has been delayed due to my situation. So I know that they are working on it, but I also know that they w
Management already nixed the idea of the slip install and our vendor didn't think it was a good idea. That option also makes me paranoid just because I've never done it and we really don't have the time at the moment due to the projects going live or deeply in motion.
Coy Krill
Core Processing Team Lead
Washington Trust Bank
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob Berendt
Sent: Wednesday, August 14, 2019 04:43
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: PTF Rollback Ideas
Importance: Low
Let's say it's been a year. At that time PTF SI12345 was the latest for some LPP. During that interval that was replaced by SI12444. Then later it was replaced by SI14698. When you put SI14698 on it applied SI12444 permanently. With no RMVPTF capability.
You could query this for more information:
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20i%20Technology%20Updates/page/QSYS2.PTF_INFO%20catalog
However, about the only way you're going to make your vendor happy is to slip install the LIC and OS (and maybe LPPs) and apply only those PTF's approved by them.
https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_74/rzahc/upgradesameversion.htm
Of course, when you do that be careful that you only use a LIC resave version that has been approved by them.
https://www-01.ibm.com/support/docview.wss?uid=nas8N1022015
But in actuality your vendor is probably happiest now. They don't have to work on resolving the issue and can simply point fingers at you because it's always the customers fault.
And, thanks for the maintenance money which we'll only use for funding our latest leveraged buy out.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Krill, Coy
Sent: Tuesday, August 13, 2019 7:52 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: PTF Rollback Ideas
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
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
midrange.com
