Subject: | |
From: | |
Reply To: | |
Date: | Sat, 5 Oct 1996 04:25:51 -0700 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
How can I tell within the job stream what O#### is?
Ed
David Maclary wrote:
>
> Ed,
>
> One thing you might try is to do only one FCOPY per file.
> Maybe something like...
>
> 1. FCOPY the disc file to a printer, but leave the spoolfile
> deferred.
>
> 2. SPOOLF O####.out.hpspool;PRINT;DEV=another-printer. Do this
> for each additional copy that you need to send to another
> printer. Hopefully, this is faster than additional FCOPYs.
>
> 3. SPOOLF O####.out.hpspool;PRI=8 to let the original FCOPYed
> report print.
>
> Good luck!
>
> David Maclary
> --------------------------
> Analog Devices, Inc.
> [log in to unmask]
> (617) 461-4127
> --------------------------
>
> >Date: Mon, 30 Sep 1996 09:59:31 -0700
> >From: Ed Uber <[log in to unmask]>
> >Subject: Better method of CCTL printing than FCOPY?
> >
> >I've just recently started reading this newsgroup, but in a thread
> >printed in the September issue of _Interact_, Stan Sieler said:
> ><snip>
> >>yes it's often not appropriate to use FCOPY...Several jobs I support
>use
> FCOPY
> >to print disc files with CCTL.
> >Sometimes the same file is FCOPY'd to several printers. For large
> >files, this can take a noticeable amount of time. Does anyone have a
> >suggestion for a better (faster, or capable of dealing efficiently
> >with multiple destinations) MPE command to use? If not, a third party
> >utility?
> >
> >Thanks,
> >Ed Uber
> >[log in to unmask]
> >
> >------------------------------
|
|
|