× 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.



Hmmm.  It wasn't EXACTLY this technique.  I used:

       01  DSPFILE-area.
           copy dds-all-formats     of OE314D.

I don't know if that makes a difference.

Joe

> -----Original Message-----
> From: cobol400-l-admin@midrange.com
> [mailto:cobol400-l-admin@midrange.com]On Behalf Of Joe Pluta
> Sent: Tuesday, August 13, 2002 8:57 AM
> To: cobol400-l@midrange.com
> Subject: RE: Need for separate Input and Output Areas in Display File
>
>
> > From: R. Bruce Hoffman, Jr.
> >
> > no offense intended here, Joe, but that's an RPG programmer's view.
>
> Bruce, you miss my point.  With this code:
>
>        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.
>
> The four data structures OVERLAP.  Changing a field in
> dds-m1map-o will ALSO
> affect all three other formats.  And it's unlikely that those changes are
> ones you want.  With this technique, I can't just initialize a field in
> dds-m2ctl-o and be assured it will stay that way throughout the
> life of the
> program.
>
> I understand all about MOVE CORR and the joy it brings.  I use it
> extensively in my COBOL version of PSC/400.  But I ran into difficulties
> with the above coding technique.
>
> Joe Pluta
> www.plutabrothers.com



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.