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




No, you need it to be 133...you'll need that CTLCHAR byte

Don in DC

On Tue, 28 Sep 2004, Dwayne Allison wrote:

> Why not create a File 132 position in length and write to it as you write to 
> the spool file.
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Fisher, Don
> Sent: Tuesday, September 28, 2004 2:37 PM
> To: 'Midrange Systems Technical Discussion'
> Subject: RE: Archiving Spooled Files
>
>
> I have thought of the periodic scan, but we generate so many of these that
> it would take longer than I'd like.
>
> Don also suggested placing the spooled files into another output queue
> without a writer and I'm thinking about that.  It would require a minor
> redesign of our report control process, but I think it's doable.  The good
> news is I'd process the spooled file and then move it to the correct queue
> so I'd be unlikely to hit the 33,000 files limit.
>
> Thanks.
>
> Donald R. Fisher, III
> Project Manager
> Roomstore Furniture Company
> (804) 784-7600 extension 2124
> DFisher@xxxxxxxxxxxxx
>
>
> <clip>
> To catch the held ones, you could periodically run a job to scan the output
> queue(s) to grab files not already archived.
> <clip>
> What we did for RVI was modify the report programs to place a copy of the
> report in a specific output queue not attached to a writer. It was
> periodically scanned.
>
> The only catch I've seen is using the spooled file APIs on an output queue
> with more than 33000 or so entries, it tends to bomb.
> <clip>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.