Re: Output queue size issue -- MIDRANGE-L

× 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.

Subject: Re: Output queue size issue
From: Paul Jackson <paulgjackson@xxxxxxxxx>
Date: Tue, 1 Sep 2009 18:28:18 -0700
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

I can confirm that RCLSPLSTG doesn't affect the output queue size. Just
tried it on a test system (V5R4)

On Tue, Sep 1, 2009 at 11:53 AM, Paul Jackson <paulgjackson@xxxxxxxxx>wrote:

Hello,

We have an empty programmer output queue that is shown as having a size of
8,409,088 which seems a little excessive as a newly created outq has a size
of 32,768.

We've tried multiple CLROUTQ's to no avail.

Does anyone know what might be causing this behavior? Would a RCLSPLSTG
reset the size?

Thanks!

As an Amazon Associate we earn from qualifying purchases.

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.