RE: Need for separate Input and Output Areas in Display File

Ravi,

I didn't realize you were referring to 01-level entries.

Quite honestly, I don't see any advantage to this method
for standard display file storage except maybe for
readability - like allowing you to INITIALIZE Header-Output
rather that INITIALIZE Header-O (or for using the READ and
WRITE statements).

I normally group all of my display formats under a single
01 entry and INITIALIZE or READ using the individual 05
level that's generated.

       01  DSPFILE-area.
           copy dds-m1map-o     of OE314D.
           copy dds-m2ctl-o     of OE314D.
           copy dds-m2sfl-o     of OE314D.
           copy dds-m2key-o     of OE314D.

Looks like a matter of preference to me.  Maybe someone
else on the list has a better reason why this would be
helpful/necessary.

Terry

> -----Original Message-----
> From: Ravi Prasanna Annasagara Nagarajan
> [mailto:ravi.annasagara@wipro.com]
> Sent: Tuesday, August 13, 2002 7:25 AM
> To: cobol400-l@midrange.com
> Subject: RE: Need for separate Input and Output Areas in Display File
>
> This is a multi-part message in MIME format.
> --
> Terry,
>
> Thanks for the reply. I know it is not necessary to define separate
> Input and Output areas. I refer to the case that is shown below.
>
> WORKING-STORAGE SECTION.
> 01  HEADER-OUTPUT.
>     COPY DDS-HEADER-O   OF PAD0137NW.
> 01  HEADER-INPUT.
>     COPY DDS-HEADER-I   OF PAD0137NW.
>
> In this case, the HEADER record format has  seperate as Input
> and Output Areas. What is the need for this?
>
> As you said it is easier to code without seperating the two areas and
> also eliminates the need for qualification. But what do you
> think is the purpose of seperating the I-O area? I have been blinding
> doing this from a long time, but have not understood the reason
> for seperating the I-O area, hence the question.
>
> I would be grateful for any inputs on this issue.
>
>
> Thanks and Regards,
> Ravi Prasanna A.N.
> mailto:ravi.annasagara@wipro.com
>