× 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 to AS/400
  • From: PaulMmn <PaulMmn@xxxxxxxxxxxxx>
  • Date: Fri, 23 May 1997 00:52:04 -0400

At 06:44 PM 5/21/97 -0400, CVWD@aol.com wrote:
>In a message dated 97-05-21 15:13:19 EDT, cgalgano@ediconsulting.com (Carl
>Galgano) writes:
>
>>  Maybe I am ignorant or braindead, but what is the
>>  big deal anyway, why do some of you guys out there need a correlation
>>  between device and device name???
>
>Vendor-supplied programs that use workstation-name-based files.


We have over 50 remote locations.  Our line/controller/device names are set
up so that we can tell at a glance where the device is supposed to be:

Device Name:

        ALA1W002        
        --|||---
        | ||||
        | |||+-----device address (yes, 3 characters for 0-7 is overkill)
        | ||+------W=Workstation, P=Printer, C=PC
        | |+-------Port
        | +--------Controller 
        +----------Location Code ALabama...


Controller Name:

        ALA     1st controller in ALabama
        ALB     2nd controller...

Line Name:

        ALABAMA (Ideally, the first 2 letters match the prefix for CTLR/DEV,
but we've been known to cheat.


At our headquarters the name was supposed to correlate to the room the
device was in (as taken from the blueprints).  However... since it's a lot
easier to rewire the patch panel when a device is moved, the name only
indicates the place the device was in when it was created...  *sigh*

--Paul E Musselman
PaulMmn@ix.netcom.com





* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* 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 MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  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.