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

Dear all especially to Hamid:

This is the price you pay for belonging to a mailing list.  If you are fed
up with receiving lots and lots and tons and tons of e-mail, just quit.

I do not care.  As long as my e-mail server doesn't blow up, keep sending me
the wonderful e-mails of yours.

Thanks

A good US citizen
============================================================================
==========



-----Original Message-----
From: Hamid Ghaffari [mailto:HamidGhaffari@bigfoot.com]
Sent: Tuesday, August 13, 2002 5:24 PM
To: cobol400-l@midrange.com
Subject: Re: Need for separate Input and Output Areas in Display File


Dear all,

Can we please refrain from sending mails to the distribution list for the
sake of it. Maybe you should limit it to the individual you want to have a
banter with. I have just had over 20 emails with the same subject. I wonder
how many of them actually discuss the subject matter to the benefit of the
novice?

My problem with "hundreds" of emails flying around via the distribution
lists (without sometimes advancing the technical issue in question) is that
my forwarding service provider's limit is reached before all my mail has
been received and real emails do not get through to.

Please do not suggest that I de-subscribe as that is not the answer! Just be
a little more selective in your choice of receipient.

Thanks,

 Hamid

----- Original Message -----
From: "Joe Pluta" <joepluta@PlutaBrothers.com>
To: <cobol400-l@midrange.com>
Sent: Tuesday, August 13, 2002 2:35 PM
Subject: RE: Need for separate Input and Output Areas in Display File


> ARGH!  Careful here.  I just got bitten by this particular issue.
>
> > > WORKING-STORAGE SECTION.
> > > 01  HEADER-OUTPUT.
> > >     COPY DDS-HEADER-O   OF PAD0137NW.
> > > 01  HEADER-INPUT.
> > >     COPY DDS-HEADER-I   OF PAD0137NW.
>
> This creates separate spaces in memory for each object.  There is no
chance
> for one to overlay the other.
>
> >        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.
>
> With THIS technique, however, each record shares the same memory location.
> Changes to dds-m1map-o", for example, are reflected in "dds-m2ctl-o".  If
> you're lazy and don't update your variables prior to each WRITE operation,
> you can get decimal data errors quite easily.
>
> Joe
>
> _______________________________________________
> This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing
list
> To post a message email: COBOL400-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/cobol400-l
> or email: COBOL400-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/cobol400-l.
>
>

_______________________________________________
This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing list
To post a message email: COBOL400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/cobol400-l
or email: COBOL400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/cobol400-l.