RE: Problems with spool files

Depending upon what you're saying, this could be true.

If you're saying that a spooled file might be held after a data queue entry
is posted by the system, that's true. To work properly, the file should be
held before hitting the queue (read on).

If you're saying that a data queue entry might be posted by the system even
though the print file is held, I don't think that's true (at least it didn't
used to be). From my experience, the system will post entry to the output
queue's data queue only if "print-ready" files are placed onto the queue, or
when an entry already on the queue is released.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"A fashion ten years before its time is indecent. Ten years after its time
it is hideous. After a century, it becomes romantic."
-- James Laver

There could also be a program monitoring the output queue (tied into it
with a data queue). A hold on the spool file (or any spool file) might
be ignored by that process. Maybe using your own output queue is
appropriate.

Paul

Principal Programmer Analyst
IS Supply Chain/Replenishment


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of James H. H. Lampert
Sent: Tuesday, August 24, 2010 2:25 PM
To: Midrange Systems Technical Discussion
Subject: Re: Problems with spool files

Morgan, Paul wrote:

If your process is mixed in with
other things (called from somewhere, calling something else or maybe
using the attention key) then a different print file with a hold
override on that print file might be appropriate.

That's exactly the situation: it's an external call from a script
that's
being run in a trigger program that is in turn tripped by an
application
that may be trying to do some sort of print-to-email itself. (And for
all I know, there could be another job monitoring the job we're running
in, doing the application-initiated print-to-email!)

If we're getting into a fight, let's try to avoid the fight in the
first
place.

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