×
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.
So far I do not see any special instructions like that you mentioned in the cume nor the group.
But what is different in my case is that I've had MF66517 since 12/2019, which makes since as "MF66517 is included in cumulative PTF package C9304740." Based on the name was the 304th day of 2019.
I suspect that I put it on in our December 2019 downtime and then did an APYPTF LICPGM(*ALL) APY(*PERM) DELAYED(*YES) prior to loading on the June 2020 PTF's. That would be my usual method of operation. I must have forgotten to do the perm apply prior to the March 2020 downtime. I sometimes forget due to pressing time issues.
I guess this is another reason to flag ptf's to apply permanently prior to loading on new PTF's. In addition to clearing up space.
Product ID/PTF ID . . . . . . . . . . : 5770999 MF66517
...
PTF status . . . . . . . . . . . . . . : Permanently applied
Latest superseding PTF . . . . . . . . : None
Status date/time . . . . . . . . . . . : 06/20/20 00:22:50
...
PTF creation date/time . . . . . . . . : 08/13/19 14:25:11
Temporarily applied date/time . . . . : 12/14/19 19:59:25
Technology refresh PTF . . . . . . . . : No
Rob Berendt
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.
midrange.com
