So you've got a python error; it likely works to run it with an older version of python (3.6?), which you could install next to your system installation and explicit setup before calling OCIDE.
... or, consider to switch from the archived, not maintained any more program to a maintained; in this case I'd suggest to have a look at Gix IDE (from a quick test not yet as mature as OCIDE was, but improving) or to use vscode with COBOL specific extensions.
I personally use a setup with VSCodium + [old] bitlang.gnucobol and bitlang.cobol (newer have an anti-feature of disabling itself if any other extension that may handle COBOL parts is enabled - especially debugging which are also registered by general purpose debugging extensions - is enabled, with the exception of the proprietary one from Micro Focus; you may could go with current bitlang.gnucobol only [which misses some features but the author may add it if you create an issue for what you miss]) + project specific task definition to build and recognize cobc's output better than OCIDE did.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When I attempt to invoke the opecobolide from the command line I get the output in the attached file.
How do I overcome these errors?
Thanks in advance
Arch
Your error output is (quoted here so people are able to search for it):
So you've got a python error; it likely works to run it with an older version of python (3.6?), which you could install next to your system installation and explicit setup before calling OCIDE.
... or, consider to switch from the archived, not maintained any more program to a maintained; in this case I'd suggest to have a look at Gix IDE (from a quick test not yet as mature as OCIDE was, but improving) or to use vscode with COBOL specific extensions.
I personally use a setup with VSCodium + [old] bitlang.gnucobol and bitlang.cobol (newer have an anti-feature of disabling itself if any other extension that may handle COBOL parts is enabled - especially debugging which are also registered by general purpose debugging extensions - is enabled, with the exception of the proprietary one from Micro Focus; you may could go with current bitlang.gnucobol only [which misses some features but the author may add it if you create an issue for what you miss]) + project specific task definition to build and recognize cobc's output better than OCIDE did.