Re: "Phantom" Spool file entries

[Michael Mayer <michael.mayer@xxxxxxxxxxxxx>]

I forgot about that parm on the CHGIPLA command .... Jim O to the rescue as usual!


                        Change IPL Attributes (CHGIPLA)                    
Type choices, press Enter.                                                 
Restart type . . . . . . . . . .       *SYS               *SAME, *SYS, *FULL        
Keylock position . . . . . . . .    *NORMAL       *SAME, *NORMAL, *AUTO...  
Hardware diagnostics . . . . . *MIN                 *SAME, *MIN, *ALL         
Compress job tables  . . . . .  *NONE             *SAME, *NONE, *NEXT...    



Respectfully, 
Michael Mayer
IBM i on Power System Admin
ERMCO-ECI
2225 Industrial Rd
Dyersburg, Tennessee 38024
Cell, Office and Text Messages: 518.641.8906
Email: michael.mayer@xxxxxxxxxxxxx
https://www.ermco-eci.com   
https://ermcopower.com/
IBM i Award Winning Blog Site: https://ibmireference.blogspot.com
Awarded IBM 2024/2025 Advocate, Contributor, Influencer and IBM i Ready Badges.     

----------------------------------------------------------------------

message: 1
date: Tue, 11 Nov 2025 11:46:59 -0500
from: Jon Paris <jon.paris@xxxxxxxxxxxxxx>
subject: Re: "Phantom" Spool file entries

Yes, I have an "all-powerful" profile, Jim.

Just in case I was hitting the kind of limit you mention I ran the function multiple times but the number stayed fixed.


Jon Paris
Jon.Paris@xxxxxxxxxxxxxx



> On Nov 11, 2025, at 9:32?AM, Jim Franz <franz9000@xxxxxxxxx> wrote:
>
> are you doing the wrkoutq with a profile with special auth *SPLCTL to 
> see all spools?
> (slightly related), fyi - if using apis to purge spooled files by date 
> or other criteria, the older api to collect spools had a limit of # of 
> spools returned and therefore purge "some" but not all- quick fix was 
> to call purge mult times Jim Franz
>
> On Mon, Nov 10, 2025 at 6:13?PM Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:
>
> > Many of the "stuck" files dated back to 2022 - we have IPL'd many, 
> > many times since then!
> >
> > The STRSPLRCL seems to have (mostly) done the job.
> >
> >
> > Jon Paris
> > Jon.Paris@xxxxxxxxxxxxxx
> >
> >
> >
> > > On Nov 10, 2025, at 5:47?PM, x y <xy6581@xxxxxxxxx> wrote:
> > >
> > > Sorry to sound like the MSFT support desk but an IPL might help.
> > >
> > > On Mon, Nov 10, 2025 at 2:15?PM Jon Paris <jon.paris@xxxxxxxxxxxxxx>
> > wrote:
> > > > I'm trying to clear up thousands of old spool files.
> > > >
> > > > Tried using SQL to delete anything prior to 2025, and some 
> > > > disappeared, but nowhere near as many as should have. Used option 4 
> > > > to delete a
> > bunch of
> > > > the remainder to see if there would be some error message. Nope -
> > nothing.
> > > > So I decided to hell with it and used CLROUTQ against those queues 
> > > > that
> > I
> > > > knew contained nothing that was needed.  That worked - kinda.
> > > >
> > > > I now have this situation in WRKOUTQ:
> > > >
> > > > Queue          Library           Files
> > > >
> > > > QPFROUTQ       QGPL                  0
> > > > QPRINT         QGPL               1731
> > > > QPRINTS        QGPL                  0
> > > >
> > > > But if I take option 5 against the QPRINT entry, instead of seeing 
> > > > 1,731 files, I see 4! And those 4 are for currently active jobs so all normal.
> > > > But where the heck are the other 1,727 that WrKOUT shows?
> > > >
> > > > Similar situation with QEZDEBUG, and QEZJOBLOG.
> > > >
> > > > Any ideas on the cause and how to get the numbers to make sense?
> > > >
> > > >
> > > > Jon Paris
> > > > Jon.Paris@xxxxxxxxxxxxxx