Add Lab: Case Sensitive Nature of COBOL Conditions (Lab 9)

[oathar]

Proposed changes

This pull request introduces a new lab to the COBOL Programming Course, focusing on the case-sensitive nature of string literal comparisons in COBOL conditional expressions. The lab demonstrates how COBOL is case-insensitive for keywords and identifiers, but case-sensitive when comparing string literals, which can lead to subtle and hard-to-detect bugs in real-world applications.

I have included all the necessary details and comprehensive guidance to assist the user in successfully completing this lab. Initially, the user may encounter an incorrect answer in their report. I then explain to the user what might have caused the error and offer helpful hints on specific areas to review and possible changes to make. This step-by-step approach aims to improve their understanding and ensure accurate results in their report.

Files added:
• CBL0066.cbl - COBOL program source
• CBL0066J.jcl - JCL job to compile and execute

Final look:

Fixes # (issue) - Not applicable, as this is a new feature addition.

Type of change

What type of changes does your PR introduce to the COBOL Programming Course? Put an x in the boxes that apply.

• Bug fix (change which fixes one or more issues)
• New feature (change which adds functionality or features to the course)
• Translations (change which adds or modifies translations of the course)
• Documentation (change which modifies documentation related to the course)
• This change requires an update to the course's z/OS environment

Checklist:

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This checklist will be used as reference for both the contributor and the reviewer

• I have read the Contributing Guideline
• I have included a title and description for this PR
• I have DCO-signed all of my commits that are included in this PR
• I have tested it manually and there are no regressions found
• I have commented my code, particularly in hard-to-understand areas (if appropriate)
• I have made corresponding changes to the documentation (if appropriate)

[MikeBauerCA]

Thank you for this contribution - approved!