Failure to permanently apply ptf's prior to an upgrade

If I fail to permanently apply ptf's prior to an upgrade I believe that it 
leaves the temp stuff around for all perpetuity.  And once I've upgraded 
to the new release it is too late to permanently apply the ptf's from the 
earlier release.  For example look at these objects in QHTTPSVR:
Object      Object    Object      Creation
            Type      Attribute   Date 
QSF56133J1  *FILE     SAVF         042299 
QSF56133J2  *FILE     SAVF         042299 
QSF56133J3  *FILE     SAVF         042299 
QSF59810J1  *FILE     SAVF         110999 
QSF61510J1  *FILE     SAVF         030600 
QSF61510J2  *FILE     SAVF         030600 
QSF61510J3  *FILE     SAVF         030600 
QSI01612J1  *FILE     SAVF         053101 
QSI02026J1  *FILE     SAVF         081001 
QSI02026J2  *FILE     SAVF         081001 
QSI02425J2  *FILE     SAVF         110801 
QSI04067J3  *FILE     SAVF         051402 
QSI04067J4  *FILE     SAVF         051402 
QSI04133J2  *FILE     SAVF         050202 
QSI04133J3  *FILE     SAVF         050202 
QSI04134J1  *FILE     SAVF         050202 
QSI04273J2  *FILE     SAVF         043002 
QSI05385J1  *FILE     SAVF         071802 

The change date on all of these is equal to our last unload/reload. Think, 
it has been many releases ago since there was any SF* ptf's for the 
standard set of LPP's.  Don't let yourself fall into this morass.  Apply 
your ptf's permanently prior to any upgrade.  Yes, it may mean an extra 
IPL on a weekend when you least have the time.

In case you're wondering these fields were the same for all of the ptf's 
listed:
System  LICPGM   LICPGM
Level   Name     Level 
999999                 

Rather worthless, eh?

Makes me wonder if this garbage is why IBM changed from SF to SI.  Perhaps 
SF was getting close to rolling over, number wise.

Rob Berendt