However, record is part of the buffers associated with the file and record data written will not be available after the WRITE statement is done. In this way, different data items can refer to the same memory location to reduce the memory space and the program is easier to maintain as well.
In addition, it is also a faster way to reinterpret the same data. Specifically does not affect the data-area fields. If you wish to define a particular storage with a different data descriptions, then you can use COBOL Redefines clause.
#Cobol fd statement manuals#
If you click the manuals link at the top of the page, bring up the COBOL Language Reference manual, and look at the WRITE statement syntax, you will find that Code: Is updated to point to the next record in the buffer. The physical write will occur if the buffer is filled.īefore the buffer is filled the internal buffer pointer I vaguely remember the following scenario : The Cobol coding sheet was a structure to identify from where the cobol coding statements punched or started writing to differentiate the statements from other. For to identify the program coding by the punch card reader,there was a need of coding sheet. When I do a WRITE WS-RECORD, I expect the WS-RECORD to retain the values after the write.īut I get the WS-RECORD as initialized to spaces in my program though the file has the record with data. Cobol Coding Sheet In olden days, COBOL programs needs to be punched on the card and it will be loaded to punch card reader.
0 kommentar(er)
