Re: Odd Printer/Print Writer question

[Larry Bolhuis <lbolhui@xxxxxxx>]

This might work, but remember those printer buffers! Could easily hold the whole
report in many cases.  Gotta know how to either not buffer or clear buffer when
spool file is clobbered or in the case of SPOOL(*NO) the program stops or is
cancelled.

 - Larry

Kevin Watkins wrote:
> 
> Wound SPOOL(*NO) on the printer file do what you need? You should be able to
> OVRPRTF and change that attribute for just that job running. Never tried
> it... but it might do what you want
> 
> ----- Original Message -----
> From: <>
> To: <midrange-l@midrange.com>
> Sent: Thursday, March 25, 1999 10:28 AM
> Subject: Odd Printer/Print Writer question
> 
> I have a payroll/time clock application.  We are planning on allowing
> employees
> to inquire on their timecards and check stubs in a centralized terminal
> method -
> I call it a kiosk.  Application security on the terminal is fairly robust
> with
> the use of timers and badge readers.  My problem is we want to enable an
> employee to print their information.
> 
> What I can't let happen is let someone print their check stub, run into some
> printer problem (jam, out of paper, etc.), walk away from the kiosk, have
> the
> problem solved, and the information prints after the employee leaves and is
> at
> risk of being picked up by someone else.
> 
> This kind of 'process' is completely foreign to how we have operated in the
> past.  I was wondering if anyone had some similar scenarios or any
> suggestions.
> I am currently thinking of:
> 
> 1.) some sort of monitor environment whereby printed information is
> automatically deleted in an error situation.
> 2.) direct print from the application.
> 3.) starting and stopping the writer from within the online program with
> feedback to the program on error situations.
> 
> Of course, I would like to do this with minimal or no modification to the
> existing online program.....
> 
-- 
Larry Bolhuis         |
Arbor Solutions, Inc  | Two rules to success in life:
(616) 451-2500        | 1. Never tell people everything you know.
lbolhui@ibm.net       |
+---
| 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
+---