Re: Sample Code for OUTQ Processing? / API Confusion

["Rory Hewitt" <roryhewitt@xxxxxxxxx>]

Dave,

Another option you might consider is changing the output queue (or multiple
output queues if necessary) to use a data queue - when a spooled file on
that OUTQ goes to ready (RDY) status, an entry is added to the data queue
containing details of the spooled file. Then you creat a
never-ending-program (aka a NEP) which waits for entries to appear on the
data queue and processes them.

The benefit of this is that you don't need to use any list API's (just the
data queue API's which are easy). Also, you won't get problems with entries
being added to the OUTQ just after you've done your API read and being
missed.

I wrote a program a while back (as have many others!) which uses a data file
to determine commands to process on spooled files - that way you can set up
'rules' to govern how your spooled files should be routed/processed/deleted
etc.

I can send you some sample code also.

Rory