Profile wanted: IBM Enterprise COBOL

Open
#6 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
testing

Research direction

Read docs/adding-a-compiler.md, especially step 2 and step 5, then generate the example project with cobalto test --profile NAME --generate-only. Compile and run the sources with IBM Enterprise COBOL, and report the compiler version, compiled items, totals line, and test cases that differ from the reference. If the profile works, submit it as a pull request; the issue also calls out PDS member names, fixed200 results, build and run scripts, and remote transport as areas to check.

Written by the indexing model from the issue text.

Description

compiler help wanted

Cobalto has no profile for IBM Enterprise COBOL. The built-in gnucobol-ibm profile runs GnuCOBOL with -std=ibm: it shows how a suite reacts to IBM-like rules, but it is not the IBM compiler.

What is needed

Someone with access to Enterprise COBOL who can run the example project and say what happened. No change to Cobalto is needed for that: Adding a compiler goes through it step by step.

Running the CLI on z/OS itself has not been tried. The path that works today without running it there is the one used for hosts without ssh:

  1. With a project profile that extends remote-sim, as in step 2 of the guide, cobalto test --profile NAME --generate-only leaves the sources and two scripts in build/remote/.
  2. Carry the sources to the host, then compile, link and run them there with your own JCL or from z/OS UNIX.
  3. Bring back the results file and, if you can, the job output, and read them with cobalto report --results FILE --output SCREEN.

What we expect to need attention, none of it tried yet:

  • member names in a PDS (upper case, at most 8 characters) for sources and copybooks;
  • the results file as fixed records (results_format: fixed200);
  • the build and run scripts, which today exist as DCL and sh templates;
  • a transport for a remote profile: Zowe CLI could fill the upload, invoke and fetch steps, but nobody has tried it.

What helps

  • A Compiler report, whether or not it worked: compiler version, what compiled, the totals line and the test cases that differ from the reference.
  • If it works, a pull request with the profile, as described in step 5 of the guide.

Please keep host names, user names and site-specific JCL out of the issue. Enterprise COBOL is one of the two compilers that the roadmap to 1.0 needs verified.

Dominant language
Python
Stars
2
Forks
0
Avg merge
4h 51m
Merged PRs (30d)
9

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from abstracta/cobalto

All issues in abstracta/cobalto

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.