× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. November 2019

RE: Removing superseded PTFs

That concurs with what IBM is telling me.

Thanks



-----Original Message-----
From: Rob Berendt [mailto:rob@xxxxxxxxx]
Sent: Wednesday, November 06, 2019 10:25 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Removing superseded PTFs

I believe so.

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 Justin Taylor
Sent: Wednesday, November 6, 2019 11:14 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Removing superseded PTFs

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.


So you're saying that:
1. Superseded PTFs are not always permanently applied.
2. If I apply SI71481 it will also apply SI70970, and that removing SI71481 will also remove SI70970.

Correct?



-----Original Message-----
From: Rob Berendt [mailto:rob@xxxxxxxxx]
Sent: Wednesday, November 06, 2019 9:54 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Removing superseded PTFs

Going by the assumption that IBM is right, let's see how this might work.
Let's say the object in question (just for an example) is QCMDEXC.
You run this command: DSPOBJD OBJ(QSYS/QCMDEXC) OBJTYPE(*PGM) DETAIL(*SERVICE) and you see that the current PTF is SI70520.
Now you put on PTF SI71481. You run the DSPOBJD command again and you see SI71481.
In the process of putting on SI71481 it created a save of QCMDEXC into a save file then restored it with the new one. When you do a RMVPTF it will restore the one saved. Now, keep in mind that the one save had SI70520 in it's DSPOBJD so therefore a RMVPTF of SI71481 would also remove SI70970.
Make sense?
If, instead of RMVPTF of si71481, you applied it permanently, it would get rid of the save file containing the SI70520 version of QCMDEXC. Thus freeing up that space.

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 Justin Taylor
Sent: Wednesday, November 6, 2019 10:43 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Removing superseded PTFs

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.


We have a bad PTF that I removed (SI70970). IBM support wants to send a superseding PTF as a test PTF (SI71481). IBM says if I delete the bad PTF and apply the test PTF, I'll end up with this:
SI71481 Temporarily applied (test PTF)
SI70970 Superseded (bad PTF)

If SI71481 is also a bad PTF, they say that removing SI71481 will also remove SI70970. This will cause IBM i to revert to the prior PTF (SI69828). PTFs would show:
SI71481 Not applied (test PTF)
SI70970 Superseded (bad PTF)

It's my understanding that superseded PTFs are permanently applied. I'm skeptical that removing the latest PTF would revert the superseded one. Are my wrong on this?

TIA
--
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

--
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


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.