Troubleshooting
Problem
DCS: VT220 Key mapping for Function and arrow keys for RF gun - Model Telxon PTC - 960 SL
Symptom
PART: 6.2 SP2 DCS
PRODUCT: RF with VT220 emulation
OS: All
DATABASE: Oracle
What is the setup required for RF equipment that
only has VT220 emulation?
Cause
Resolving The Problem
Basically there is a file called yntrsmvars.bin in DCS_BASE/jam/files. This
is the binary representation of file yntrsmvars. This file defines which is the
key file to use for the current TERM ( e.g.: currently on support server
$SMBASE/files/yntrvt100keys.bin is setup as the file for vt100 ). Now this key
file is binary representation of the ascii file which contains the key
mapping.
So the steps involved are
--------------------------------------
1. Create a new ascii keymap file
for telxon and update the key mapping
2. Create a binary representation
of the key file ( for this we need a utility provided by JAM which is available
only on devp boxes)
3. Update yntrsmvars file to add mapping for the new
TERM to the binary file created in previous steps
4. Create a binary
representation of the smvars file ( for this also we need a utility provided by
JAM which is available only on devp boxes)
5. Export the correct term
when users log in to telxon. (The other users should still export vt100 or
whatever key mapping they use)
Another issue is that yntrsmvars
(default SMVARS file) does not have a link to yntrvt220keys.bin file. So the
customer has 2 options
1. rename yntrvt220keys.bin to one of the files
for which there is a link and set the corresponding SMTERM in WMSYantra/whmenu
2. Generate a new SMVARS file and create a binary for it. For this we
will need to contact the engg or send the vars2bin.
The customer
logs into Yantra application using the RFs, netterm(PC) and Xwindows. netterms
can be configured to generate VT100 or VT220 keys. But I am not sure of xterm.
If xterm cannot produce the VT220 keys, the customer will need to implement a
change to the WMSYantra script to identify the machine from which the user is
logged in and dynamically set the keystroke to expect, VT220 for RF and VT100
for the rest.(One way of implementing this is to keep a list of ips assigned to
RFs in a file.Any time a user logs in, system will check if the request is from
one of the ips in the file and set the correct keymap).
Binary
files need to be placed in the $DCS_BASE/jam/files directory. These files are
required by Yantra to understand the VT220 key strokes. I will also send a
detailed mail on the environment variables to be exported etc.
Create the file required to enable the customer to use both VT220 and VT100
simultaneously.
The vt220 key map file to produce TAB on F1.
Steps to be followed to implement this below.
1. ftp the
attached files to the yantra server (ensure that *.bin files are ftped in
binary mode and others in ascii mode)
2. Copy the files to
$DCS_BASE/jam/files
3. When login through the RF mode, export variable
SMTERM to vt220 (export SMTERM=vt220)
4. When login from CRT or RF,
ensure that the SMTERM to vt100
Contact Applications Support for
the new binary and ascii files.
The keymap files can be found in their
SupportAttachments/Internal/VT220KeyMappingsForTelxonPTC960SL_RF_Gun
folder.
Below are the commands that the RF gun from TELXON is sending :
F1 = ^[ [11~
F2 = ^[ [12~
F3 = ^[ [13~
F4 = ^[ [14~
F5 = ^[ [15~
F6 = ^[ [17~
F7 = ^[ [18~
F8 = ^[ [19~
F9 = ^[ [20~
F10 = ^[ [21~
F11 = ^[ [23~
F12 = ^[
[24~
Cursor up = ^[ [A
Cursor down = ^[ [B
Cursor left =
^[ [D
Cursor right = ^[ [C
( ^[ = Escape )
Historical Number
PRI49433
Product Synonym
[<p><b>]Fact[</b><p>];
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21529782