× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




On 26/02/2010, at 8:34 AM, Doug Palme wrote:

I am sure this is possible but what I am not sure on is how to set it up.
I have a full screen display file that uses lines through 16. I have a
subfile control record defined with headings on line 17 and a subfile that
has fields layed out beginning on line 18.

What I would like to do, is display the main record format and then lay
the subfile on top of that, so that both are displayed at the same time.

Ensure all record formats do not overlap. This is different from overlay. Overlap means record formats share lines and will require a different technique. All data and display attributes for each record format must be on discrete lines. That is the beginning or ending attributes for a field cannot be on a line used by another format. This can happen without you being aware of it when fields start in the first column or end in the last column of a screen.

If all formats are discrete then simply specify OVERLAY on the second and subsequent formats. There is an implied OVERLAY on SFL records so you don't need to (can't?) specify it there.

I know that I have seen this done, or something similar to it at some
point. Or do I have that in reverse order, the subfile displayed first as
a write and then exfmt on the main record format?

The order in which you write is unimportant as long as the OVERLAYing records are written after the record without OVERLAY. You generally need one record without OVERLAY to cause the screen to be cleared of previous output. The decision on which format to read is usually based on the one most likely to be changed by users. I usually build screens from the top down but there is no requirement for that.

Consider FORMATA occupies lines 1 to 16. FORMATB (SFL) occupies lines 18 to ?? (probably 22), FORMATC (SFLCTL) occupies line 17, and FORMATD (f-keys) occupies line 23.

I would put OVERLAY on FORMATC and FORMATD. I would load FORMATB, write FORMATA, write FORMATD, and EXFMT on FORMATC.

If the SFL is simply informational and FORMATA accepts user input then I would probably put OVERLAY on FORMATA, and FORMATC. I would load FORMATB, write FORMATD, write FORMATC, and EXFMT on FORMATA.

Other combinations are equally valid.

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.