RE: Tumble Duplex on IBM Infoprint 21

Hi Dave -

>How about a brute-force-and-ignorance work around?  Create a dummy output
>queue, and attach a data queue to it.  Create a CL program to monitor the
>data queue from a never-ending job.  When the CL program gets a data queue
>entry signifying that a spool file has landed on the dummy queue, have it
do
>a CHGSPLF to make the spool file tumble duplex and move it to the real
>output queue for the Infoprint.

Actually, I thought of that right after sending my message.  (Great minds
think alike! <G>)

Since we have user profiles and overrides pointing to the queue, I attached
the data queue to the original queue and created a new queue that actually
feeds the printer.  I also included code to move the entry back afterwards
(changing duplex back to *no as well) since many reports to that printer are
save(*yes), only having one entry at a time in the new queue, moving entries
to the new queue only if the writer is running and waiting between files and
the output queue is released; moving the entry back to the old queue if the
entry is held or if the writer is not running or is held or if the output
queue is held; and various other things to make the whole process as robust
as possible.

>I realize that this is akin to using a sledgehammer, whereas your data 
>transformation program would be more like a scalpel, but I've always 
>found it easier to make sledgehammers work than scalpels. <grin>

Well, I would still like to find a "scalpel" solution if anyone has one.  I
prefer scapels to sledgehammers.  And despite all of the extra code that I
put into the program to make it as robust as possible, things can still get
messed up if someone moves a report into or out of the new queue manually
(messed up only to the extent of printing simplex on the Infoprint or
printing duplex on some other printer).  Also, if someone moves a report out
of the original queue to some other queue during those milliseconds between
the time that I retrieve the information and the time that I do the move, it
can get moved from that other queue to my new queue even though it shouldn't
be.

Ken
Southern Wine and Spirits of Nevada, Inc.
Opinions expressed are my own and do not necessarily represent the views of
my employer or anyone in their right mind.

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---