I have included below a cut and paste in text format of a program that
allows maintenance of help text - Question: Is this one subfile or two ???
I am not sure if the list will remove underscores - hopefully it does not.
Find _______________________________ MFS510D MFS510S1 5 31 1
Cmd Ctl ...+... 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6
...+... 7
__ .h2 MFS510S1
__ Account entry
__ .p Enter the debtors account company and the account number or prompt
for
__ .pe an account.
__ .p To prompt for an account enter
__ .pe alpha search key.
__
__ Company
__ .p Enter a valid company number. If prompting, the company can be left
Find _______________________________ MFS510D
__ .h1 Debtors balance inquiry
__ .h2 MFS510S1
__ Account entry
__ .p Enter the debtors account company and the account number or prompt
for
__ .pe an account.
__ .p To prompt for an account enter
__ .pe alpha search key.
__
More...
Answer: 1
If you use sflpag = sflsiz you can do just about anything you want
although putting buttons on a subfile record may be not possible.
If you have to have buttons then make the screen a non subfile display
screen.
Build a subfile within your program then read the subfile to build the
displayed page - we do this quite often, effectively instead of a work
file we use a work subfile.
Not sure if this addresses the original question correctly ,,,
Cheers
Don Brown
From: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
To: "RPG programming on the IBM i (AS/400 and iSeries)"
<rpg400-l@xxxxxxxxxxxx>
Date: 18/01/2018 11:31 AM
Subject: Re: Enhanced 5250 screen - two active windows?
Sent by: "RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx>
On 1/17/18, 12:47 PM, Booth Martin wrote:
How do I do that? Can I do that?
You could always fake it, i.e., take full control of the screen, NOT
using actual 5250 windows.
QuestView, for example, doesn't use actual 5250 windows. That's why it
works, "windows" and all, on pre-InfoWindow 5250 terminals. Of course,
it also uses mostly a user-defined data stream (which is a royal pain in
the butt), and "Read Input Fields" rather than the more common "Read MDT
Fields" (which involved me, many years ago, in assisting an emulator
vendor in fixing a bug in their support of that protocol).
--
JHHL
As an Amazon Associate we earn from qualifying purchases.