RE: Display Files in Cobol/400

[Vernon Hamberg <vhamberg@xxxxxxxxx>]

I think this technique was common before subfiles were available. Maybe 36
days. All the fields that are normally displayed by a subfile would be a
matrix of fields in a single format. If there are input fields in a header,
they'd be included with these in the same format.

What you don't get is the READC (read changed subfile record).You need to
check all the fields in your array (matrix) for change.

Doable, just more work. You'd different field names for each row. Or you
could use the COBOL equivalent of RPG's multiple occurrence data structure
(is there one? 2-dimension array?). You might need separate processing
branches for each row (not with MODS or 2d array?), etc.

At 02:22 PM 3/20/02 +0000, you wrote:
>Vernon wrote:
>
> > The display shows a window on this array, and there's no
> > reason this can't be done, including rollup/down, Bottom,
> > More..., etc., activity. The one area that could be a problem
> > is, you might run out of indicators for display attributes.
>
>You can certainly have several formats displayed on the screen at the same
>time. I'm not sure that you can have active input fields in more than one
>at a time however. It's not really a COBOL question. If it can be done in
>RPG it's almost certainly possible in COBOL.
>
>Dave...
>                _________  ,___o
>              __________   _\ <;_
>            ___________   (_)/ (_)       http://www.twickenhamcc.co.uk
>=======================================================
>The opinions expressed in this communication are my own and do not
>necessarily reflect those of my employer.
>
>_______________________________________________
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
>To post a message email: MIDRANGE-L@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/midrange-l.