ITEM: E7082L

Function Key mapping problem with Micro Focus COBOL 3.0 on Mod 360

Question:

I am using Micro Focus COBOL 3.0 (trademark of Micro Focus limited).
The function key mapping for COBOL works fine for a 340 and a 220. But 
it doesn't for a 360. All the three are running on AIX 3.2.3 and they 
are all clones of the same system. I have also tried switching the 
terminals but I still have the same problem.

All systems have the same cobkeymap and keybcf is setup the same.
The terminals are DG217's and Qume 30's.  There are no HFT's on these
systems.  We have setup our own terminfo files for the terminals and 
they are the same on all systems.

When we try keybcf on the Model 360, instead of seeing FF0182, or
some other valid code for F1, we get a string of five numbers.  When
we take these same terminals and cables to either the Model 340 or
Model 220 they work fine.

In our COBOL program we are trying to ACCEPT function keys.  The
codes that are coming across are not being recognized as the function
keys.

Response:

There is an environment variable called COBKEYTIMEOUT.  This is used
mainly with networked terminals where the escape sequences for function
keys may be split between packets.  This allows COBOL to wait until all
information is received before acting on any escape sequence.  Although
this is not a networked situation, the escape sequence seems to be a 
key here.  The DG217 terminals use an escape sequence for function keys.
The Qume 30 terminals do not.  The Qume 30s are now working properly on 
both 340 and 360 machines.  The theory here is that the 360 may be 
delivering the escape sequence to COBOL so fast that it beats the rest 
of the sequence and COBOL sees a separation similar to packets.  Use of 
this environment variable may solve the problem.

Response:

Setting COBKEYTIMEOUT to 10 corrected this situation.  All terminals
are now working correctly on all models.



Support Line: Function Key mapping problem with Micro Focus COBOL 3.0 on Mod 360 ITEM: E7082L

Dated: May 1994 Category: N/A

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

Comments or suggestions?
Contact us