Re: Holding S/36 DFU printouts

[Dave Mahadevan <mahadevan@xxxxxxxx>]

Don Schenck wrote:
> 
> Neil --
> 
> Uh ... but WHAT printer file? QSYSPRT????
> 
> I THOUGHT it was PRIORITY-0.
> 
> I mis-typed earlier: I want to have the report NOT print until released.
> 
The easiest way to do this is in the procedure before you do the DFU
program, do a OVRPRTF
like OVRPRTF QPDZDTALOG HOLD(*YES) I know it is CL, but you can put CL
in a procedure and it will be processed (this little feature saves a lot
of time particularly when you want to use certain native commands like
CPYF instead of S/36 command COPYDATA).
> 
> Don Schenck wrote:
> >
> > All --
> >
> > It's been a LONG time!
> >
> > I'm modifying some S/36EE code (OCL), and I need to hold the DFU printouts 
>(all in S/36 mode).
> >
> > What's the correct // PRINTER statement?
> >
> 
> Don - add HOLD-YES to the // PRINTER

HOLD-YES will produce one copy! and put the spool on hold after printing
the copy (I never understood the logic behind this one ...)

> 

-- 
Thank You.

Regards

Dave Mahadevan.. mailto:mahadevan@fuse.net
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *