ITEM: F0979L

How do I get PF3 to work on cicsterm

Question:

When working with CICS/6000 via TCP/IP on OS2 why doesn't PF3 work as
expected?

Response:

The problem is because the key mappings in the .3270keys file does not 
match the escape sequences being put out by the terminal emulator.  The 
way to fix this is to edit that file using vi so that it can be 
corrected.

The .3270keys file contains lines like the following:

bind    pf1             "\\eOq"          \# keypad 1
bind    pf2             "\\eOr"          \# keypad 2
bind    pf3             "\\eOs"          \# keypad 3
bind    pf4             "\\eOt"          \# keypad 4
bind    pf5             "\\eOu"          \# keypad 5
bind    pf6             "\\eOv"          \# keypad 6
bind    pf7             "\\eOw"          \# keypad 7
bind    pf8             "\\eOx"          \# keypad 8
bind    pf9             "\\eOy"          \# keypad 9

The values inside the double quotes are the sequences that cicsterm will
check for and if they do not match will cause problems.  To insert the 
correct values do the following:

Repeat following for each key binding:
   1) Move the cursor underneath the first character after the /e 
      (ie. for pf1 above it would be on the O).
   2) Type 'cw' to change the word
   3) Type \V                
      - where \ indicates the Control key, on the keyboard
   3) Type the key you are trying to bind (eg. pf1)
   4) Type \ to exit editing mode
      - where \ indicates the Escape key, on the keyboard

Note:
The \V indicates to vi that it should display the escape sequence 
instead of acting on it.  That means it also includes the control code 
for \.  As the .3270keys file expects \\e to stand for \ we now 
need to remove that control code (probably \^[).

   5) Type 'T' 'e' 'x' to delete the first character after the last 
      letter 'e'

Once all the binding have been done keys will work as expected within 
cicsterm.



Support Line: How do I get PF3 to work on cicsterm ITEM: F0979L

Dated: November 1993 Category: N/A

This HTML file was generated 99/06/24~13:30:52

Comments or suggestions?
Contact us