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



Occasionally "things happen".
For example, Let's say I order ptf SI12345. I will get a save file
QSI12345. Now maybe it's not in WRKPTF. Rare but possible. Most likely
if someone restores it from another machine or some such thing.
UPDPTFINF fixes this.

PTF process:
you order a ptf. Let's say SI12345.
You get the save file QSI12345.
Let's say it fixes QCMDEXC.
You load and apply SI12345. It copies the old QCMDEXC to somewhere, let's
say QSI12345V1. Then it restores the new QCMDEXC.
You apply this permanently (and IPL if necessary). This will remove the
backup (QSI12345V1). However it still leaves QSI12345 on your system, AND
it leaves member SI12345 for the cover letter in QGPL/QAPZCOVER.
Now you run the DLTPTF (and you do NOT specify *SAVFONLY). This will
remove save file QSI12345 and it will also remove the member SI12345 from
QGPL/QAPZCOVER.
If you had specified *SAVFONLY on the DLTPTF it would have left QSI12345
and that member on your system sucking up space.

Where RMVPTF comes into play is this.
You've loaded SI12345 and applied it temporarily. However you discover it
has a bad effect on QCMDEXC.
So you run RMVPTF SI12345. It restores QCMDEXC from somewhere (let's say
QSI12345V1).

Once you've applied a ptf permanently you cannot do a RMVPTF so why keep
the save files around, or the cover letters? Run the DLTPTF.


Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.