RE: Odd Printer/Print Writer question

We had a similar situation where we had multiple customers dialing into us
through an ASYNC protocol converter (Andrew DataLynx YUK)

If a customer spooled a report, then hung up the connection before it
printed, the report was left in the spool file.

If another customer dialed in, the spool file would still be there and they
could print it.   The reports showed prices, which of course were different
for each customer.

Here's what we did:

User signs on and calls our startup program
ENDWTR  KIOSK *IMMED
CLROUTQ         KIOSK
STRPRTWTR   KIOSK

When they sign off, we called our signoff program

ENDWTR  KIOSK *IMMED
CLROUTQ KIOSK

The ENDWTR and CLROUTQ commands are done in the signon program in case they
don't signoff properly.


Art Tostaine, Jr.
CCA, Inc.
Parlin, NJ  08859


> -----Original Message-----
> From: owner-midrange-l@midrange.com
> [mailto:owner-midrange-l@midrange.com]On Behalf Of
> mcrump@ballfoster.com
> Sent: Thursday, March 25, 1999 11:29 AM
> To: midrange-l@midrange.com
> 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.....
>
>
> +---
> | 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
> +---
>

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