RE: Deleting PTF *SAVF to clear disk space

(sorry for the late post - left in my draft folder)
fyi
One note on deleting SAVF of ptf.
If you are using SAVSYSINF command as part of your backup strategy - it
wants to save ptfs installed since last SAVSYS, and will complain when not
found (if you deleted the SAVFs (at V7R1). Of course its good to do a SAVSYS
after the ptf install, but not always possible.

Jim Franz


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob
Berendt
Sent: Monday, May 07, 2018 2:43 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Deleting PTF *SAVF to clear disk space

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