Re: output queue object size question

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

 Hi

RCLSPLSTG doesn't have any effect on *OUTQ objects that I know of. Could 
be wrong, of course. Look at the help text, and you'll see that this 
command removes unused, empty members of the PFs in which spooled files 
are stored. These members are cleared but not removed when a spooled 
file is deleted, so as to allow reuse, hence, better performance when 
creating spooled files (printed output).

I don't know about the *OUTQ object itself - that would probably be 
something that contains a list of the spooled files that it "queues" - 
it never has the actual contents of the spooled files. I looked at 
several OUTQs on a v5r3 machine, and they are typically 24KB or 32KB or 
40KB - seems they get bumped by 8KB as needed. Didn't do an exhaustive 
study - are yours larger that that? If so, maybe do a DMPOBJ on the OUTQ 
and see what you see - might not be meaningful, bu maybe!

Vern

On 8/19/2010 8:21 AM, tim.dclinc@xxxxxxxxx wrote:
> I was just looking at object sizes on our system and noticed an output queue
> storage size that was pretty large. The output queue was empty, and I ran a
> RCLSPLSTG, but the size was still large.
>
>
>
> Is this something that is reduced during an IPL?