openmainframeproject / openmainframeproject/cobol-programming-course
CBLDB22R did not generate correctly from course JCL
Nobody has claimed this yet.
- Dominant language
- COBOL
- Stars
- 3.6k
- Forks
- 721
- Avg merge
- 11d 16h
- Merged PRs (30d)
- 1
Description
Course Details
IBM Learning Platform
Description
Ran the zos.public.db2.jcl(db2setup) JCL to generate CBL and JCL files in VSCode (see page 39 of the COBOL Programming Course #3 3.2.0). The version of CBLDB22R.JCL generated by the course scripts is missing a four year old fix found in the corrected github repository:
//REPORT DD SYSOUT=*
Without the //REPORT, submitting the job results in file status 96 and IGZ0035S at runtime as well as an hour or two of debugging to fix something that was fixed four years ago!
Reproduction Steps
1.submit job for zos.public.db2.jcl(db2setup) and follow instructions on page 39 for the rest.
2.
3.
...
Additional Context
IGZ0035S There was an unsuccessful OPEN or CLOSE of file REPORT in program CBLDB22 at relative location X'1EE'.
Neither FILE STATUS nor an ERROR declarative were specified. The status code was 96.
From compile unit CBLDB22 at entry point CBLDB22 at compile unit offset +000001EE at entry offset +000001EE
at address 1B2011EE.
Error message using the course jcl (missing the //REPORT line).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the zos.public.db2.jcl(db2setup) course script and the generated CBLDB22R.JCL, then compare them with the corrected repository version mentioned in the issue. Confirm that the generated JCL defines REPORT and that following the course procedure no longer produces the reported file status 96 and IGZ0035S errors.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100