Hello,
I found out that continuation lines (hyphen column 7) are not supported in copybooks. I encountered this bug with a level 88 with multiple values.
can you provide an example ???
Anonymous
You seem to have CSS turned off. Please don't fill out this field.
Here is an example:
01 ROOT. 05 SUBLEVEL PIC X. 88 FIRST-VALUE VALUE 'S'. 88 SECOND-VALUE VALUE 'S' 'T' 'U' 'V' 'W' 'X' 'Y' 'Z - '' 'B' 'C' 'D' 'E' 'F' 'G'.
I am currently travelling around Europe (for the next 2 months) + I have other Requests so I can not give you a date for the fix.
In the short term fixes include
JRecord uses Cb2xml to process Cobol. Cb2xml has a simple pre-processor to strip out columns 1-6 and 72-80. The pre-Processor is ** preProcess(Reader r, int columnStart, ...** method in https://sourceforge.net/p/cb2xml/SVN/HEAD/tree/source/cb2xml/src/net/sf/cb2xml/CobolPreprocessor.java
You could create an updated version to handle string extensions for 88 values. (There is code to handle normal extensions for value clauses (non 88 levels).
If you are using IOBuilders use the set the Copyboo-Format to FREE_FORMAT option
JRecordInterface1.COBOL .newIOBuilder(new StringReader(updatedCopybook) .setCopybookFileFormat(Cb2xmlConstants.FREE_FORMAT)
A fix for this issue will be in JRecord version 0.90
can you provide an example ???
Here is an example:
I am currently travelling around Europe (for the next 2 months) + I have other Requests so I can not give you a date for the fix.
In the short term fixes include
CB2XML Background
JRecord uses Cb2xml to process Cobol. Cb2xml has a simple pre-processor to strip out columns
1-6 and 72-80. The pre-Processor is ** preProcess(Reader r, int columnStart, ...** method in
https://sourceforge.net/p/cb2xml/SVN/HEAD/tree/source/cb2xml/src/net/sf/cb2xml/CobolPreprocessor.java
You could create an updated version to handle string extensions for 88 values.
(There is code to handle normal extensions for value clauses (non 88 levels).
If you are using IOBuilders use the set the Copyboo-Format to FREE_FORMAT option
Last edit: Bruce Martin 2017-04-16
A fix for this issue will be in JRecord version 0.90