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



Ron,

I'll venture some guesses.  If you have PC's on a Windows network and do not
have Client Access installed (i.e. either nothing or CA Express) then you
would reference the AS/400 by its name that was configured in Netserver - by
default this is the system name + a Q prefix.  If you have PC's that
communicate with the AS/400 via Client Access, then the default name is
usually the system name (w/o the Q).  Could this be your situation?

Also, once you install Client Access in a scenario w/o a DNS server that
knows the AS/400, it will write an entry to the PC's local hosts file,
making a cross reference between the system name that was entered and the IP
address.

And finally, it is only the default to use the system name when configuring
a Client Access connection.  So if you have two people doing configurations,
and one adds a prefix while the other does not...

Chuck

----- Original Message -----
From: "Klein, Ron" <ron.klein@acs-inc.com>
To: "''MIDRANGE-L'" <MIDRANGE-L@midrange.com>
Sent: Friday, April 05, 2002 2:47 PM
Subject: System Names


> Hi All,
> We have a program that is called from a PC and creates directories on the
> 400 in the IFS and then does a bunch of things with the files.
>
> On some boxes we have to use 'Q' in front of the system name to access the
> correct IFS directory and on other boxes we can't access the system if we
> use the 'Q'.
>
> Is there a way to determine which designation the 400 is goning to like
> ahead of time without receiving an error message?
>
> TIA
> Ron




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.