RE: Client Access Printer emulation delay

We use Zebra printers this way with the following emulation setup:

Checked - Transform print data to ASCII on AS/400
Printer model 'Other Printer'

Every thing else is defaulted, and the device is automatically created as 3812

It ususally takes just a few seconds for output on ours. Not sure what else it could be.

HTH,

Regards,
Jon A. Erickson
Sr. Programmer Analyst
800.COM Inc.
1516 NW Thurman St
Portland, OR  97209-2517
 
Direct: 503.944.3613
Fax: 503.943.9313
Web: http://800.com

-----Original Message-----
From: Sneddon, Jim [mailto:JSneddon@AllstateTicketing.com]
Sent: Tuesday, February 27, 2001 12:42 PM
To: 'MIDRANGE-L@midrange.com'
Subject: Client Access Printer emulation delay

Our end-users access our AS400 (on V4R4) with a Client Access terminal
session and they have a small thermal ticket-printer which is connected with
a Client Access printer emulation window. This all goes through a NT network
via TCP/IP to the AS400

Whenever the user hits enter in the program that prints the tickets the
printer emulation window shows it's little "activity" icon and then it takes
15 to 20 seconds for the printer to start printing.  All of the tickets in
the batch after the initial delay come out one after another.

If I watch the appropriate outq while this happens everything appears to be
normal and the output is gone within the first couple of seconds after
hitting enter so it doesn't appear to be hanging around in the outq.

This happens to workstations in the field connected via 56K dial-up to our
NT network and it happens here in the office on my PC less than 10 feet from
the 400. 

On the NT side the Client Access printer emulator prints to the
"Generic/Text Only" driver and I've fiddled around with the spool settings
and priorities to no avail.  I can have it go directly without going to NT
spool and it still takes 15 - 20 seconds to print.

Just for grins I've tried Mocha, Rhumba, and a couple of more obscure 5250
emulation packages and the delay remains.

Most of the end-users are on Client Access and I'm on Client Access Express
4.3 and the delay is the same.

So....

Anyone have any ideas???  Is there something I'm missing on the 400 side
that could cause the delay ???? or am I stuck with an NT problem...

Thanks,

Jim Sneddon
jsneddon@allstateticketing.com
Las Vegas, NV

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