Re: Defective PTF set to apply at IPL - how to stop it.

[CRPence <CRPbottle@xxxxxxxxx>]

  The reference to DLTPTF as having possible added value [to ensure no 
residual effects], was noted to be performed only *after* the defective 
PTF had been permanently removed.  Alluded in my original reply was the 
need to first perform [after the APYPTF IPLAPY(*NO) request had been 
performed as the recovery\answer for the "Subject" scenario]:

   RMVPTF PTF(SI54738) LICPGM(5770TC1) RMV(*PERM) DELAYED(*NO)

  Since the prior corrective action to change the APYPTF action from 
delayed to no-apply, that PTF should be effectively the same as if just 
loaded; i.e. neither applied nor scheduled for apply at IPL, thus a 
status of merely /loaded/.  In that state, I am somewhat confident the 
remove with DELAYED(*NO) should be possible; though any existing 
requisites for that PTF could complicate the removal.

  If a request to DSPPTF 5770TC1 SI54738 fails with a "PTF not found" 
condition, then [irrespective the success or failure of the DLTPTF 
request] the supersede should be capable of being ordered, loaded, and 
[scheduled to be] applied without any issues; i.e. no potentially 
negative effects per remnants of either the defective PTF or a PTF save 
file with that defective PTF.  If instead that DSPPTF request shows a 
PTF, then whatever steps are necessary to effect the Remove PTF must be 
performed.

Regards, Chuck

On 02-Dec-2014 12:00 -0600, Jeff Crosby wrote:
> My command:
>
> DLTPTF PTF(SI54738) LICPGM(5770TC1)
>
> On Tue, Dec 2, 2014 at 11:03 AM, John McKee wrote:
>
> > What was in the job log ahead of the listed message?
> >
> > On Tue, Dec 2, 2014 at 9:34 AM, Jeff Crosby wrote:
> >
> > > Hey, the APYPTF worked! It now has IPL Action of None. Thanks
> > > Chuck.
> > >
> > > I can't seem to delete it entirely, though.  I get this:
> > >
> > > Message ID . . . . . . :   CPF35C5
> > > <<SNIP>>