*LOCAL cannot be used as a hostname for LANSA Client

Date:	Archived
Product/Release:	LANSA Client V10.0
Abstract:	If you specify *LOCAL as the Hostname in the LANSA Client Administrator you will not see the correct file definition in LANSA Client
Submitted By:	LANSA Technical Support

Description:

In LANSA Client you can specify to connect to different hosts and also different types of hosts (ie. "Other" or "AS/400") which indicates either to use a local Repository or an iSeries Repository when creating queries or reports.

When using *LOCAL as the Host Name in the LANSA Client Administrator. LANSA Client will not display the correct file/fields definitions.

For example:

You will get a message "Attempt to save local PC definitions failed":

Next, if you drag the file and it's fields - in this example, using "DEPTAB" to create a query:

Without saving that query if you create another new query by dragging another file - this time using the file "PSLMST". You will get misleading results - the same file definition of "DEPTAB".

As a result, the correct file definition has not been retrieved.

Reason:

LANSA Client produces a file called '<Hostname><partition><language>.key' (e.g. localhostdemeng.key) for the current connection definition and this file cannot be created if the name *LOCAL is defined as a host name in LANSA Client because the character '*' is a restricted character in DOS/Windows environment.

Workaround:

To workaround this issue, use LOCALHOST or the local PC Name or any other relevant Host name ie. any host name other then *LOCAL in the LANSA Client Administrator like this:

You should then be able to see the correct file definition when creating any new queries.