I have a program which runs online, letting the user select parameters to be
fed to a report program, which is then run with its output pointed to disk.
The online program then presents the report to the online user, with the
only whistle being that the first line of the report, known to be page
headings, is written to line 5 of display memory, then on line 6 Memory Lock
is turned on, and the rest of the report is dumped line-by-line to the
display.  That all works fine.

But at the end of that cycle, I want to put the cursor in the locked area,
which seems to be inaccessible, apparently because I'm using memory-relative
cursor positioning.  When I try to do the subsequent IO sequence at line 3,
the cursor ends up on line 6, "as close as it can get" to line 3. (and of
course my prompt overwrites the first data line of the report).

Before I go playing with my terminal-IO driver, can someone tell me off the
top whether switching to screen-relative cursor positioning for subsequent
IO will let me place the cursor in the area above the Memory-lock line?

This is all being done with pure character-mode; the user can actually do
the IO from anywhere on the screen, but it looks nicer if it happens in the
expected location.  Strictly a cursor positioning problem.

A simple YES answer from one of you terminal IO experts would be most
welcome; if it's NO, some workaround would be great!

TIA

Tracy Pierce, Systems Programmer
Golden Gate Bridge, Hwy & Trnsp Dist
P.O.Box 9000, Presidio Station
San Francisco, CA  94129-0601
phone 415-923-2266
email to [log in to unmask]