Visara LINCS Features - Manual (Page 67)

57
Chapter 6. 3270 Server Features
707021-001
The Nickname file is not required to provide specific LU assignments, but may be used to
provide a means to this end.
LINCS accepts as the Nickname file, a file by the name of: nickname.sys
This file can placed on a floppy diskette residing in the floppy drive, or may be located in the
SYSTEM subdirectory on the hard drive. LINCS will search the available drives for the
nickname.sys file in the order of drives c, d, a, b. Although it may be useful to create the
nickname.sys file and test it on a diskette, you will normally want to copy it to the hard drive
using Media Management for normal operations.
The nickname.sys file is read into memory at IML time. You may also invoke changes on the
fly by copying a new nickname.sys file to the hard drive, then invoking Central Control Mode
utility 3/5. This will cause the new nickname file to be read into LINCS memory, and all new
connections will use the new file.
Syntax for the nickname.sys file is as follows:
nickname1=host,lu1
nickname2=host,lu2
or
nickname3=class_name
or
nickname4=LUnn
where each nickname must be a unique string of up to 16 characters consisting of alphanumeric
characters and/or the characters space, !, “, #, $, %, &, ‘, (, ), *, +, ,, ., -, /, :, ;, <;, =, >;, ?,
{, |, }, and ~. Do not use [, \, ], ^, or _.
All entries into the file should be on consecutive lines, with each line terminated with a carriage
return. There is to be one entry per line, with no white space to the left of the carriage return
other than as part of the nickname itself.
LINCS is not case sensitive for the nicknames. When using the format of nickname=LUnn,
however, the characters “LU” must be in capitals.
Each host,lu in the nickname file should be in the form of a single letter corresponding to the
host letter assigned by LINCS for the host connection, separated by a comma from a two digit
LU number (in hex!). Do not use the Host ID name from configuration.
If a class_name is used, this corresponds to the LINCS Class Name for a 3270 host. LINCS is
not case-sensitive for the class_name parameter.
When using the format LUnn, the letters LU must be in capital letters, and the nn is the hex
value of the desired LU. The client must also send the appropriate Service Name that is LINCS-
compatible to let LINCS know which PU that the LU is on.
TN3270E Server
LINCS provides TN3270 and TN3270E Clients access to all types of 3270 hosts. Clients can
connect to a LINCS node to communicate with SNA, Non-SNA and Bisync hosts on a session
basis. LINCS provides server capabilities for TN3270 clients as defined in RFC1576, and