|
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] Folks, COBOL has not changed this in 30 years, the only time the actual write buffer is preserved after a write is when the record is also defined as SAME-RECORD-ONLY or the WRITE statement fails. The only way to preserve the contents if you have crafted a program that requires it is to work in working-storage and do a WRITE FD-01-Record from WS-01-Record. Having said that it is possible that the buffer may be usable after the write i.e. preserved, but there are no guarantees on that. -----Original Message----- From: geir.kildal@entragroup.com [mailto:geir.kildal@entragroup.com] Sent: Wednesday, December 11, 2002 10:04 AM To: cobol400-l@midrange.com 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. I have looked up this in an old COBOL/400 reference(from the age of Sauron), SC09-1240-00 page 196 - WRITE: "After successful execution of the WRITE or REWRITE statement, the current record may no longer be available in record-name, but is still available in identifier(WS-REC, my comment)" 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.