Installation guide

26
SCON-3074 Configuration
707112-001
Entry 10
Line Port IP Address Type 3270 Host LU
—— —— ————— —— ————
FET1 02122 ___ ___ ___ ___ Client+CC VMESA_prod3 02
Similar to the previous two entries, only TN3270 clients that provide their own handling of
Command Chaining sequences for console sessions should attempt to use this entry. In this
case the user must connect to port 2122, and must be using the configured IP address of
207.15.182.137.
The Nickname File
Optionally, a nickname file may be used to assign sessions to users and to help provide
password security. Differently formatted entries may be used to provide resource assignment,
User ID/password security, and resource security.
The nickname file (nickname.sys) is an ASCII text file, and can be created on a PC using any
text editor. The Visara eManager product also may be used to create, manage, and distribute
the nickname.sys file. The name of the file must be nickname.sys, and no other file name will
be recognized by LINCS. The file must be present in the system directory on the LINCS hard
drive, or on a floppy present in the floppy drive at boot time. The file is read only at boot time,
or when the utility /3/5 is run. Note that you can only run the /3/5 utility if the file already
exists, and the new file should not exceed the original file size (read at boot time) by more
than 20%.
File entries may be of the following types:
Name=resource
Where the name can be any alphanumeric name, 12 characters or less, and the resource is a
LINCS SCON-3074 resource. LINCS resources that are valid include the name of a 3270
Host Class, or a host designator followed by a comma and the two hex character address of
the desired session. Here is an example:
Console003=05,03
In this example, the resource name ‘console003’ would be configured in the TN3270E client
(LU Name field), and would be requested by the client emulator at connection time. The
resource that the SCON-3074 will give to the client is session 03 from Host Circuit 05.
Name=resource password
This entry is exactly the same as the previous entry except that a password is added to the end
of the entry, separated from the rest of the entry with a space. In this instance, to receive the
requested resource, the user must enter the correct password. A corresponding example is
shown below:
Console003=05,03 pituitary
The password can be a combination of alphanumeric characters.
UserID-password
This type of entry is used to validate a user at connect time. It is used with all client types
defined on the TN3270 Client Definition panel that have the letters ‘ID’ included (‘Client