HP3000-L Archives

July 2005, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Wirt Atmar <[log in to unmask]>
Reply To:
Date:
Thu, 14 Jul 2005 12:56:04 EDT
Content-Type:
text/plain
Parts/Attachments:
text/plain (62 lines)
One person wrote me privately the following this morning:

=======================================

I realize this is OLD, but it took me this long to find out.  All the
terminal emulators are having problems with this, even Reflection, which
usually works when nothing else does.  The workaround is to use /1 for
F1, /2 for F2, etc.  This is buried in the documentation of MF cobol.


>>> Wirt Atmar <[log in to unmask]> Friday, January 21, 2005 12:10:50 PM
>>>
Jeff writes:

> My company is currently using QCTerm as a unix emulator, when I try
to
> run the anim command (animate command in MF Cobol) it works, but I
am
> not able to use important function keys like F4 to monitor. If I
press
> function keys the session just freezes and I have to do a hard reset
> from the QCTerm drop-down menus. Not sure hw much knowledge anyone
here
> has in Unix Emulators or if I am posting in the right area. Anyway,
any
> help would be appreciated it. It appears the function keys are
clashing
> with the animator function keys.

Unfortunately, there's not enough information in what you write to say
anything definitively. In fact, pretty much the only way to debug a
problem like
this -- which is an interaction of a program with the emulator -- is
for us to
sign onto your machine, using a step-by-step set of instructions that
gets us to
the failure point as quickly as possible.

By performing a trace analysis, we should be able to characterize the
problem
very quickly.

Wirt Atmar
Author of QCTerm

=======================================

Unfortunately, I don't know anything about MF COBOL (other than what "MF"
usually stands for, as in "MF UNIX"), but what I can now guess from the response
above is that MF COBOL is simply not setting the functions keys properly for
an HP terminal.

Rather than properly fix the problem in MF COBOL by having it query the
terminal type and setting the function keys correctly as a result, the
documentation suggests that they would rather put the onus on the user to type "what the
keys would have transmitted," thus earning their MF status.

Wirt Atmar

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2