× 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.


  • Subject: Re: TCP/IP and NAMED Devices
  • From: mcrump@xxxxxxxxxxxxxx
  • Date: Thu, 11 Dec 1997 08:52:45 -0500






>Does V3R2 TCP/IP support named devices? In many of our applications
required
>that we route data to a specific device by name. That name is setup in a
>table(s). So getting a new device(qpadevxxxx) etc everytime you won't
work.
>Can we do this with 3.2? or is it only on the RISC versions?

I think this requires a combination of the client and the server having
this capability.
I believe the new beta version of CA/400 has some support in this area.  I
do know
that the TN5250 with the Network Station allows this to be administered.  I
have
been experimenting with this and have had mixed results.....My V4R1 system
seems
to work fine but my V3R2 and V3R7 machines don't.  I have not had a whole
lot
of time to dig into this.

Maybe someone with some TCP knowledge at IBM could help illuminate (Mark?)?





+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@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 ...


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.