LOCATE command for non-existing line number

George,

Observed on v2.7.22301 alpha.

LOCATE gets a rather confused when looking for non-existing line number.s

  e.g. LOCATE 900 on a file that only has 200 lines.

You end up with an extra line below the Primary command line (corrupt display).

Pressing the <RETURN> key, the cursor is trapped between this extra line and the primary command line.

The data on the extra line depends on whatever was near there when the LOCATE command was issued.

It could be a copy of the upper-most data line or a second **** Top of Data **** line.

It doesn't matter whether you type in the LOCATE command or if it is issued via macro.

I spotted it when a wayward macro tried to locate a non-existent line and failed to return an error code or error message.

It may help resolution to know that the error does NOT occur if the command is LOCATE TOP 900
You still get neither a non-zero RC nor a message, but the display corruption does not occur.