|
Hi, Geir > May be this is why it has been 'normal' in COBOL environments to have a > WORKING-STORAGE area to work on before you write or modify a record. > Working directly on the file buffer has not been 'good latin'. Could be. I understand your point, but this is a practice (a good one) rather than a stated requirement that I'm aware of. Maybe it's even a strong suggestion. Yes, defining it in WS will (OK, *SHOULD*) protect you from this particular anomoly, but what guarantee do we have of that? If in fact the compiler can choose to clear fields outside of documented means (and again, if this is documented, then show me where and I'll be less disgruntled).... what reliability do we have in any area, including WORKING-STORAGE? Dennis geir.kildal@entragroup.com@midrange.com on 12/11/2002 03:26:24 AM Please respond to cobol400-l@midrange.com Sent by: cobol400-l-admin@midrange.com To: cobol400-l@midrange.com cc: Subject: Re: R: COBOL WRITE after OPEN EXTEND results in CLEAR-AFTER-WRITE This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] Dennis. May be this is why it has been 'normal' in COBOL environments to have a WORKING-STORAGE area to work on before you write or modify a record. Working directly on the file buffer has not been 'good latin'. If you define your record in Working-Storage and use WRITE record FROM WS-RECORD-DEFINITION, you will avoid the problem. The contents of WS-RECORD-DEFINITION will not be affected when you write the record.. Mvh. Geir _______________________________________________ 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.
As an Amazon Associate we earn from qualifying purchases.
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.