Re: Print files

The thing I always worry about with this is the spool file disappearing
before you can process it unless it's SAVE(*YES).  

I'd go with the option of putting it in an outq not attached to a writer
and use the dataq monitor to either do the CPYSPLF or SNDNETSPLF to the
appropriate people.
 
BTW... I don't have ObjectConnect on my system and SNDNETSPLF works
fine.

AlanShore@xxxxxxxx 11/28/2006 2:05:24 PM >>>

If you don't have a CL program wrapping this RPG program, how about the
following (and this is just off the top of my head)

Change the print file to USROPN (if you can), so that at the end of the
program, close the print file,
trap the job name info etc and use the SYSTEM() api to CPYSPLF to
whatever
different OUTQ's & USER's you may wish.

Like I said, just a thought. I don't know how feasible this idea is.



Alan Shore

NBTY, Inc
(631) 244-2000 ext. 5019
AShore@xxxxxxxx

midrange-l-bounces@xxxxxxxxxxxx wrote on 11/28/2006 04:52:35 PM:

Nick_Radich@xxxxxxxxxxxxxx wrote:

We use SNDNETSPLF all the time.  The only thing is that
you have to  program it into your CL and trap the Job Name
Info.
You can send it to a single User, or to multiple Users.

What CL?

The idea is for the print file itself to produce multiple
copies, going to multiple *OUTQs

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