TN5250 and TN3270 Terminal Types
If your TN5250 or TN3270 connection requires a device ID (LUName for 3270), you can use this option to set it. Note that if you have multiple hosts with different requirements, you should use the DeviceID(n) setting, using the host number to apply the setting.
Very few hosts still require this setting for connection purposes with Telnet protocols. You do not need to worry about it unless you know specifically that your host connections require unique LUNames or Device ID's for each user.
Settings:
*none |
Default--no deviceID or LUName is needed for a new connection |
*required |
Individual users will need to know and enter their deviceID or LUName on first use. After this point, it will be stored in a cookie (local storage if available in browser). If the user's cookies or local storage values are cleared, the user will need to re-enter the LUName on next connection. |
*prompt or *prompt=text |
On each connection, will prompt the user for the DeviceID or LUName. If the "*prompt" has an equals sign, the text to the right of the = will provide the prompt to the user.
For example, *prompt=Please Enter the LU Pool Name to Connect to: |
Template |
If you would like to utilize the acquired Session index (a number starting with 0 and ranging up to 1 less than the number of sessions licensed on your server) to generate a LU name, you can use a wildcard pattern based on the following syntax:
|{d/h}width[:offset]|
Where: d=decimal representation (1,2..9,10,11) h=hexadecimal representation (1,2..9,A,B)
width=width of the number padded to the left with zeroes
:offset (optional) if the starting number should be some offset from zero, include it here. For example, if the first number inside the LUName should start with 21, rather than 0, use 21 for this value.
Examples, server licensed for 15 sessions:
LU|d6:1| LU000001, LU000002...LU000015 #REG|h4| #REG0000, #REG0001...#REG000E OE|d6:22| OE000022, OE000023...OE000036 |
TNVT-ASCII Terminal Types
For ASCII connections, the DeviceID setting can be used for an Answerback reply (Telnet request 0x05 / Answerback Request).
If this setting is not included in the web.config or profile, the default answer-back is "FlynetVT" with a CarriageReturn LineFeed at the end.
