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



What you are describing is the save file. Not the one in QGPL, but the one that exists in the product library.

Pete

rob@xxxxxxxxx wrote:

Test. I don't think that permanently applying a ptf removes the save file. What it does remove is the copy of the objects changed by the ptf stored "somewhere". Permanently applying removes the ability to remove a ptf by removing this backup copy. It also applies it to the 'A' side of the machine. Which, in all but the rarest of cases, is insignificant to you and I.

To remove the save file you're better off to do a WRKOBJ OBJ(QGPL/QMF*) OBJTYPE(*FILE)
WRKOBJ OBJ(QGPL/QSI*) OBJTYPE(*FILE)
Actually I favor the huge
DSPOBJD OBJ(*ALL/*ALL) OBJTYPE(*FILE) OUTPUT(*OUTFILE) OUTFILE(QTEMP/DSPOBJD)
Followed by
SELECT ODLBNM, ODOBNM, ODOBTP, ODOBAT, ODSIZU*ODBPUN AS Size,
ODOBTX
FROM qtemp/dspobjd
WHERE ODOBAT = 'SAVF'
ORDER BY size desc
Often when 'the other guy' downloads a ptf they may give it a non standard name. Or you may have a program product that uses QSF* or some other naming convention. And, you'll also find those save files from a year ago when 'that one gal' saved an entire data library into a save file to transfer to another system.


Tech note: Once you get a size of all 9's for ODOBSZ you'll never use it again and rely upon ODSIZU*ODBPUN as per the text on ODOBSZ says to.

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.