> In message <[email protected]>, eppyebots <[email protected]> > writes >>what do you mean with a 'blocking convention'? > > :-) I suspect that you may be rather younger than I am. Stream data was > often resolved (blocked), physically or logically, as 80 character lines > to correspond to the display characteristics of a dumb terminal.
The free EDICLEAN utility at my website www.talsystems.com, click "tech corner" tab, supports blocked data as either input or output. You can run any file in and specify an output format of blocked to see what 'blocked' data look like. (The software automatically detects blocked mode on the input side) Also FWIW... using "blocked format" (fixed-length delimited records) was also quite popular on IBM mainframe systems, as not all COBOL programmers had the, er, uh, "practical experience" necessary to code programs using variable-length records. (No such thing as "ORGANIZATION LINE SEQUENTIAL" in Mainframe COBOL like there is in, say, Microfocus COBOL). Michael C. Mattias Tal Systems Inc. Racine WI [email protected] ------------------------------------ ... Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Job postings are welcome, but for job postings or requests for work: <JOBS> IS REQUIRED in the subject line as a prefix.Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/EDI-L/join (Yahoo! ID required) <*> To change settings via email: [email protected] [email protected] <*> To unsubscribe from this group, send an email to: [email protected] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
