RE: Archiving Spooled Files

["Dwayne Allison" <Dwayne.Allison@xxxxxxxxx>]

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.