Re: Trying to position cursor on complicated screen

"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on 05/08/2019
01:47:42 PM:

----- Message from smith5646midrange@xxxxxxxxx on Wed, 8 May 2019
13:39:11 -0400 -----

To:

"'RPG programming on the IBM i \(AS/400 and iSeries\)'" <rpg400-
l@xxxxxxxxxxxxxxxxxx>

Subject:

Trying to position cursor on complicated screen

I have a very complicated screen and I am having problems positioning

the

cursor. There are no modifiable fields. It is display only and

function

keys allow for editing via a different screen



Here is a brief layout.

Record1 - lines 1 - 4

Window subfile1 - lines 5 - 12

Window - lines 13 - 17

Window subfile2 - lines 18 - 25

Subfile - lines 26-27 (contains system error messages)



All of the records are OVERLAY without erasing.



I write the records in this order

Subfile

Record1

Window subfile1

Window

Window subfile2



Any other sequence seems to wipe out one or more of the previously

written

records.



Because the window subfile 2 is the last record written (exfmt) , all

of

the records written are displayed correctly but the cursor positions to

the

first subfile record inside of it which looks strange. I would like to
position it to the top left or right corner, I don't care which. I

tried

using CURSOR but it positions within the window, not the entire screen.



If I could write record1 last, I could solve the problem but that seems

to

clear the records below it. Is there something that I might have wrong

on

that record causing it to erase the window records?



Is there something else that I am missing? I really don't want to have

to

create fake subfiles (2 sets of fields) and programmatically make it

look

like the fields are rolling with the page up / page down.

At first I missed that you said all the records are OVERLAY and I thought
you were just missing that. So I never replied. The issue appears to be
that Record1 is not a "Window" record. Hence, when you write it, it wants
the whole screen. Could you make Record1 a window. Then other windows
should not be erased when Record1 is written last.

The only part I'm not clear about is when you say you Subfile first--is
that a subfile for which Record1 is the control?

Michael Quigley
Computer Services
The Way International
(419) 753-1222