Skip Navigation

The Computer Journal 1974 17(1):93-94; doi:10.1093/comjnl/17.1.93
© 1974 by British Computer Society
This Article
Right arrow Full Text (PDF)
Right arrow Alert me when this article is cited
Right arrow Alert me if a correction is posted
Services
Right arrow Email this article to a friend
Right arrow Similar articles in this journal
Right arrow Similar articles in ISI Web of Science
Right arrow Alert me to new issues of the journal
Right arrow Add to My Personal Archive
Right arrow Download to citation manager
Right arrow Search for citing articles in:
ISI Web of Science (1)
Right arrowRequest Permissions
Google Scholar
Right arrow Articles by Triance, J. M.
Right arrow Search for Related Content
Social Bookmarking
 Add to CiteULike   Add to Connotea   Add to Del.icio.us  
What's this?

Discussion and Correspondence

Handling records with a variable structure in COBOL

J. M. Triance *

Computation Department, University of Manchester Institute of Science and Technology, Sackville Street, Manchester, UK

In many data processing applications records are encountered where the fields vary in length and position within the record. In the case of Utility Programs this variation can occur from one run to another and in the case of input data it can occur from one record to another in the same file. Normal COBOL data definition is incapable of handling this type of data but it can be handled effectively by means of the DEPENDING ON option of the OCCURS clause. But the proposed Standard in COBOL will have an adverse effect on this invaluable facility.


Received May 1973.

* Computation Department, University of Manchester Institute of Science and Technology, Sackville Street, Manchester


Add to CiteULike CiteULike   Add to Connotea Connotea   Add to Del.icio.us Del.icio.us    What's this?




Disclaimer:
Please note that abstracts for content published before 1996 were created through digital scanning and may therefore not exactly replicate the text of the original print issues. All efforts have been made to ensure accuracy, but the Publisher will not be held responsible for any remaining inaccuracies. If you require any further clarification, please contact our Customer Services Department.