RE: Easy PTF retrieval ate up the DASD

I did find several SAVFs in QGPL. Oddly they were all dated back to 2014; I would've expected them to be more recent than that - like, last week, when I downloaded them?

Also, I assumed that either DLTPTF or the Clean Up Fixes would remove the SAVFs; guess not.

Anyways, I've deleted all of these and am now down to 69%, much better than where I was when I started. Some of these must've been lingering for a while.

Thanks
Bob

From: Justin Taylor

What do these commands show:
WRKOBJPDM LIB(QGPL) OBJ(QS*) OBJTYPE(*FILE) OBJATR(*SAVF) WRKOBJPDM LIB(QGPL) OBJ(QM*) OBJTYPE(*FILE) OBJATR(*SAVF)

That should be the PTF save files that were downloaded.

From: Bob Cagle

I was watching last week's thread on Easiest PTF Upgrade Retrieval with interest as I know I'm behind on PTFs.

So I submitted a SNDPTFORD PTFID((*CUMPKG)) and let it run. Within a couple of hours, my system hit 95% storage utilization, up from around 88%. I made the decision to cancel the job instead of letting the storage go critical.

I followed that up by doing a DLTPTF PTF(*ALL) LICPGM(*ALL), and running the Clean Up Fixes in Navigator. The system was IPL'd over the weekend, but is still sitting at 94% utilization instead of the 88% before I started this endeavor.

Any suggestions for clearing up this space?

For the record, we are on a 520 at 7.1 with just 175GB DASD. I have been working on the boss for 2 years to get him to agree to an upgrade, but have not yet been successful. Maybe I should just let the PTFs fill the disk and crash the system...