Re: Perm. apply PTF's thoughts

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
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 




Mike.Crump@xxxxxxxxxxxxxxxx
Sent by: midrange-l-bounces@xxxxxxxxxxxx
03/28/2003 08:33 AM
Please respond to Midrange Systems Technical Discussion
 
        To:     midrange-l@xxxxxxxxxxxx
        cc: 
        Fax to: 
        Subject:        Perm. apply PTF's thoughts


Folks,

Historically, I've been remiss about permanently applying PTF's.
Originally, my thought process was that normally you see it as an item on
new releases with corresponding instructions to clean up disk space.  I've
never had storage problems around new release installs so I have forsaken
that process in the name of time.

I'm beginning to wonder how wise that is.  Doesn't that leave some
potential for PTF *SAVF's and other objects (potentially IFS) out there 
for
cleanup?  And couldn't those objects be in many different places on the
system (QSYSDIR, QIWS, QDNS, stream files in IFS directories, etc)?  What
do other people do with regards to perm apply of PTF's?  Do you think it 
is
easier to perm apply PTF's prior to a new release as opposed to cleaning
their tracks later or never?


Michael Crump
Saint-Gobain Containers
1509 S. Macedonia Ave.
Muncie, IN  47302
(765)741-7696
(765)741-7012 f
(800)428-8642

"We will meet that threat now with our Army, Air Force, Navy, Coast Guard,
and Marines so that we do not have to meet it later with armies of
firefighters and police and doctors on the streets of our cities."  George
W. Bush  March 19, 2003

www.standwithbush.com




_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.