Re: RPG36 with OCL examples desired; 1) insert-a-record 2)

The record ID was very important to the processing of data.

Back then we're talking code for 80 or 96 column cards. In other words, every record was the same length, so a file would hold the header record and all of the associated detail records. The cards were put in the desired order with mechanical sorting machines. So, generally, you had only one input file. The Record ID was a punch in a column. Quite often a column, say column 95, was reserved for a record ID. An A in column 95 was a header record. A B in column 95 was a ship-to address. C in 95 might be an item record, a D in column 95 might be a Tax Code record, and T in column 95 might be a Total record.

Say column 1-6 is an invoice number. So, you sort your cards in ascending order by Column 1-6 and by Column 95. Then run the cards through to print invoices. Those record IDs tells your program what the data looks like and tells your program what to do with the data.

(This also explains why Matching Records and Level Breaks were so important back then.)

On 7/29/2016 6:18 PM, CRPence wrote:

I still am not entirely clear what is the general purpose of the
Record ID indicator on the type=record-format line of the I-spec;
possible values being any 01-99, L1-L9, H1-H9, LR, **, DS, and 01-10
specifically for CONSOLE files. I understand the effect as utilized, or
I believe I do; i.e. the indicator is on, when and only when, the record
from the I-spec is read, thus appropriately controlling the write which
is since conditioned with the same indicator.