DMTLPR190E Connection timed out on LPR printer.

[william JANULIN]

Yes, I am going through all the parameters with a fine
tooth comb. What is really wierd is that I can send
stuff to the same printer (it has a different IP
address) from another system. In fact I can send stuff
to that printer from the zOS LPAR that is on the same
z800 as the VM system that I am currently working
with. rSCS is indeed busier on this partucular system
so I may have to define some additional ports in my
Profile TCPIP for RSCS traffic.

If anyone on the list has run into this, please pass
along any info you may have on this.

Hmmm...well, I'll have to admit, I'm not terribly
familiar with how RSCS
does its job, but it sounds like the problem lies
with the connection
between RSCS and the printer (RSCS seems to be
getting the job from you
and trying to send it off to the printer, where it
fails)...Poking around
a bit, it looks like this is the only time RSCS will
display the LPR190E
with "connection timed out", so I imagine there is
some problem routing
traffic to the printer from this stack.
Regards,
Miguel Diaz
z/VM TCP/IP Development

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

[David Boyes]

Yes, I am going through all the parameters with a fine tooth
comb. What is really wierd is that I can send stuff to the
same printer (it has a different IP
address) from another system. In fact I can send stuff to
that printer from the zOS LPAR that is on the same z800 as
the VM system that I am currently working with. rSCS is
indeed busier on this partucular system so I may have to
define some additional ports in my Profile TCPIP for RSCS traffic.
If anyone on the list has run into this, please pass along
any info you may have on this.

Another possibility is that you have reached the number of supported
connections in the embedded LPD in the printer -- many support 50 or
less at a time (early JetDirect cards are notorious for this). Most
embedded LPD servers support only a limited number of connections, and
many LPR implementations hold an open connection for the 2 minute FIN2
signoff timeout after sending a job. If this printer is shared with a
lot of different hosts, you can easily exceed the number of permitted
connections the LPD can support (one of the better reasons to spool
output from multiple systems to one or two "buffer" systems, or to use
IPP, which has an explict requirement for disconnection following job
transmission).