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



midrange-l-request@xxxxxxxxxxxx wrote:

>   1. Re: Failure to permanently apply ptf's prior to an upgrade
>      (Sue Baker)
>
> wrote on Thu, 16 Feb 2006 13:36:56 GMT:
>
>> Object      Object    Object      Creation
>>             Type      Attribute   Date 
>> QSF56133J1  *FILE     SAVF         042299 
>> QSF56133J2  *FILE     SAVF         042299 
>> QSF56133J3  *FILE     SAVF         042299 
>> 
>
>It's been a while since I ran into this sitution, but I'm pretty 
>sure that if you do a DLTPTF SF56133 it will take care of these 
>three files.  You can do the same for the remaining ones on your 
>list and it will clean things up in a similar manner.


I haven't done it much either and not recently. But I seem to recall the DLTPTF 
can be very picky. For PTF savefile objects that are leftover from previous 
releases, I think it needs to be told explicitly the correct ProductId _and_ 
the correct VRM.

Perhaps a DSPPTF *ALL *ALL *ALL to an *OUTFILE will list enough info that a 
useful DLTPTF command can be entered?

Tom Liotta


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.