Moving to GitHub
Interesting. https://www.ibm.com/support/knowledgecenter/en/SS6SG3_4.2.0/com.ibm.entcobol.doc_4.2/PGandLR/ref/rldadgrp.htm "When specified at the group level, the USAGE clause applies to each elementary item in the group. The usage of elementary items must not contradict the usage of a group to which the elementary items belongs."
Interesting. Can you provide a language reference link that shows this to be valid COBO?. The IBM 4.2 language reference doesn't seem to permit this. It's an interesting technique, and I didn't know the language permitted it. https://www.ibm.com/support/knowledgecenter/en/SS6SG3_4.2.0/com.ibm.entcobol.doc_4.2/PGandLR/ref/rldadgrp.htm Talks about National groups for Usage is National to permit Unicode. It doesn't mention Usage is Computational to provide a parent-level definition.
Interesting. Can you provide a language reference link that shows this to be valid COBOL. The 4.2 language reference doesn't seem to permit this. It's an interesting technique, and I didn't know the language permitted it.
group-level COMP-3 not properly passing USAGE to sub-elements
change to cobol.defs.DDE incompatible with python 3.4
change to cobol.defs.DDE incompatible with python 3.4
change to cobol.defs.DDE incompatible with python 3.4
Build Instructions Wrong
Windows Build Failure
SKIP2 and SKIP3 added to ignored syntax.
SKIP2 causes problems
66 level RENAMES causes problems
cobol.loader.picture_parser problem with precision using (#) syntax
Added unit test cases. Looks to be fixed.
Change Handling of 1-byte values.
number_display incorrect for signed EBCDIC fields
Version 4.4.7. Added unit tests and cleaned up ...
Add the formulae
Further cleanup of documentation.
Remove all but one dependence on xlrd, making i...
Fix issues #23 and #24 (also #20 and possibly #19)
66 level RENAMES causes problems
cobol.loader.picture_parser problem with precision using (#) syntax
number_display incorrect for signed EBCDIC fields
The above code has been tested with real data and properly handles PIC S9 with the...
well, that's what I thought, thus my initial recommended fix, however, precision+=...
Important: The field in question is defined as a PIC S9. The raw EBCDIC value is...
cobol.loader.picture_parser problem with precision using (#) syntax
cobol.loader.picture_parser problem with precision using (#) syntax
To be slightly more general. if decimal: precision += irpt Not sure of PIC 9(5)V99(2)...
correction...the above fix isn't correct. the line SHOULD be: if decimal: precision...
number_display incorrect for signed EBCDIC fields
cobol.loader.picture_parser problem with precision using (#) syntax
Ignore all .zip files.
Change unit test for RECFB_VB reader to have tw...
bdw_iter() consuming 2 records at a time
Test case revised to show multiple records per block.
Nope, it is a user confusion error. Looking back on the documentation, it should...
That indicates a unit testing error. Here's data used to test a VB file with a BDW...
That indicates a unit testing error. Here's data used to test a VB file with a BDW...
bdw_iter() consuming 2 records at a time
Fix the cobol.RECFM_VB file handling
Updated the bdw_iter() method of the cobol.RECFM_VB class as suggested in the bug...
Updated the bdw_iter() method of the cobol.RECFM_VB class as suggested in the bug...
Problem with cobol.bdw_iter
Updates for 4.4.5, including a fairly large num...
yield bdw+data should be yield bdw+block_data
Problem with cobol.bdw_iter
Fix the COBOL Schema Parser Functions
Fix the COBOL Schema Parser Functions
Here's another approach: fix the COBOL_schemata function to take the lexer class...
Here's an approach 250 with tempfile.TemporaryFile(mode='w+') as stripped_copybook:...
Here's the definition of COBOL_schemata. def COBOL_schemata( source, replacing=None...
Release 4.4.4 may solve this via "subrecord" processing. See :py:class:stingray.test.cobol_2.Test_Copybook_13(...
Version 4.4.4 Update:
"the different segments define the data that may be found within RDT-ADDL-DATA" Aha....
"the different segments define the data that may be found within RDT-ADDL-DATA" Aha....
I understand how to parse a workbook using one schema or another, but I'm not sure...
66 level RENAMES causes problems
The RENAMES has been reset to be merely a warning instead of an unsupported exception....
In effect a RENAMES is another kind of group-level item. The offset begins at the...
SKIP2 causes problems
There are four relatively common "Compiler-Directing Statements" that must be filtered...
oops....this isn't a problem, it just looks different from the others because most...
single-entry 01 level records are not properly parsed
66 level RENAMES causes problems
SKIP2 causes problems
single-entry 01 level records are not properly parsed
COBOL Schema vs. COBOL Schemata
Added a COBOL_schemata function which builds mu...
ODO SetSizeAndOffset
After limited testing of the current code and the issue appears to be resolved.
Release 4.4.3 Bug Fixes and Small API Change
Make external schema loader tolerant of empty s...
Changed :py:meth:`cobol.COBOL_file.row_get` to ...
Fix documentation.
ODO SetSizeAndOffset
The exception shows a single byte value (b'\x00') for a two-byte COMP field. How...
http://www-01.ibm.com/support/docview.wss?uid=swg1PI07821 "The behavior is undefined...
The section that is throwing the exception (occasionally) is: 018500 04 CHD-NO-DEL-ITEMS...
This isn't an issue that is specific with the demo app. I simply attempted to use...
Problem opening XLSX file
This is a lack of clarity in the documentation. The demo/app.py doesn't work with...
The demo/app.py isn't really designed to work with the .xlsx files. It doesn't use...
What's the ODO definition? And the definition on which it depends? An OCCURS DEPENDING...
Problem opening XLSX file
ODO SetSizeAndOffset
Split large files
Added features to support split of large files.
RECFM_VB while offset<= len(block_data)
setSizeandOffset group size calculation incorrect after first pass
Version 4.4.2