× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



At 09:48 07/17/98 -0400, Joe Giusto wrote:
>I have just started using TCP/IP to access the 400 and have noticed that
>it gives me a device name QPADEVxxxx (like when doing passthru).  Is
>there any way to get the same device name each time (like I did before
>using the TCP/IP)?  We have an application that uses the device name and
>user id to validate authority and this is going to be a mess if we start
>using TCP/IP company wide.

Named telnet devices are supported by Client Access V3R1M3 with PTFs to the 
TCP/IP and server code. Be sure to apply the latest PTFs, since there were some 
significant problems when this was first released. It's working fine now. Just 
do NOT set the CA "automatically re-connect" switch unless you are prepared to 
trap errors caused when the named device is not available. This will still 
cause a message loop situation because CA doesn't get notified of the problem 
(or ignores the notification - I don't know which) and blindly keeps retrying. 
Otherwise, it's working like a charm for us.


Pete Hall
peteh@inwave.com 
http://www.inwave.com/~peteh/

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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.