Thanks, Will fix. Cheers, Brian
Why did the hipster burn her mouth? She ate the pizza before it was cool.
For future reference. Seems like a nicely detailed paper on the ins and outs of COBOL data conversions when getting things to and from a mainframe. Via LinkedIn http://georgenet.net/oracle/files/publications/DFSORT_feature_updated.pdf
For future reference. Seems like a nicely detailed paper on the ins and outs of COBOL data conversions when gettings to and from a mainframe. Via LinkedIn http://georgenet.net/oracle/files/publications/DFSORT_feature_updated.pdf
Not sure about that, Pat. An alternative is to crank up the COBOL-UP project space. I just turned up the blogging module at https://sourceforge.net/projects/cobol/ Seeing as you have edit powers there, and it's called COBlog, feel free to write up some blog entries, Pat. (We may want to change your spell-gooder user name there first - but seeing as you have admin privs, you can probably do that yourself). We could route people to the Utilities Project for commercial angles with GnuCOBOL, but this...
New copies of the FAQ are linked from the top menu here. This was fixed some time ago, but due to site changes, I no longer have access to a add1tocobol.com shell to update that old copy. Here is the better link https://open-cobol.sourceforge.io/faq/index.html#inspect
(it checks for recursive copybooks since years). Are you sure about that Simon? identification division. program-id. sample. data division. working-storage section. COPY datadef. procedure division. display datadef goback. end program sample. copies.cob 01 datadef pic x(32). COPY datadef. datadef.cpy prompt$ cobc copies.cob datadef.cpy: 2: error: datadef.cpy: Too many open files attempt to reference unallocated memory (signal SIGSEGV) cobc: aborting compile of datadef.cpy at line 2 (unknown: unknown)...
I'm not convinced. ;-) Can I get you to do me a favour, Anon and post the last hundred or so lines from prompt$ strace cobc ... 2>&1 >compilepass.txt where the ... is your program build of TEST.cob and whatever other files you are using on the command line? We'll track this down, but I'm still leaning to find that there is a cyclic loop going on somewhere. The strace will show all the low level open and access calls. Cheers, Brian