Systems Programming (Application Development Procedures)
Part Three - Challenge #12

Background:

A Systems Programmer does not know it all. However, they get very good at knowing which professional manuals to reference and figuring things out. The more they are required to figure out, the more effective they are in their Systems Programmer role.

When a Systems Programmer installs a new release of Enterprise COBOL for z/OS, they become familiar with "need to know" facts such as the COBOL target library data set names, the Enterprise COBOL for z/OS supplied compile JCL Procedures, etc.

DevOps is a popular clipped compound that emphasizes the collaboration and communication between business application developers and other IT professionals where Dev represents development and Ops represents the other IT professionals. Quite commonly the other IT professionals is the Systems Programmer in z/OS environments. This relationship has existed for many decades in the mainframe environment, long before the clipped compound, DevOps, was created as a result of implementing an "Agile Infrastructure".

Developers (Dev) are dependent upon procedures created and maintained by a Systems Programmer (Ops).

An example would be a JCL PROC (Procedure) used by developers to compile COBOL.

Your challenge:

You installed a new release of Enterprise COBOL for z/OS. You need to modify the IBM supplied JCL PROC (Procedure) that development will use to compile COBOL source code using the new release of the z/OS COBOL compiler.

The development staff requested assembler-language expansion produced in the new COBOL compiler source listings.

You are aware the COBOL compiler benefits from newer and faster machine instructions in current z System hardware.

The challenge is to modify the IBM supplied JCL PROC shipped with the new release of Enterprise COBOL for z/OS to include assembler-language expansion in the COBOL compiler source listing and specify the current z System hardware architecture for the new COBOL compiler to benefit from newer and faster machine instructions in you current z System hardware.

Things you currently know as the Systems Programmer to accomplish the challenge:

  • CC#####.JCL(COBCLG) is the new JCL PROC that business application developers will eventually use to compile COBOL source code with the new release of Enterprise COBOL for z/OS.
  • CC#####.JCL(COBTEST) is JCL that executes the COBCLG JCL PROC.
  • Enterprise COBOL for z/OS Customization Guide is SC14-7380-03
  • Chapter 2. in the Customization Guide lists the compiler options.
  • COBCLG PROC needs PARM=(options) to include assembler-language expansion in the COBOL compile source listing and to include the hardware architecture level to benefit for the current hardware faster machine instructions.
  • COBCLG PROC only has VBREF compiler option and needs two more options that can be found in Chapter 2. of the Enterprise COBOL for z/OS Customization Guide.
  • z/OS command D M=CPU will display the z System hardware number that can be used to specify the PARM=(options) architecture level in the new Enterprise COBOL for z/OS compile.

submit jcl(cobtest)

Review cobtest COMPILE SYSPRINT DDNAME

Edit CC#####.JCL(COBCLG) PARM=options to include 1) assembler-language in the COBOL COMPILE SYSPRINT and 2) z System hardware level of the contest z System.

Use Chapter 2. in the Customization Guide to find needed COBOL compiler options.

submit jcl(cobtest) to test added options

Once the COBOL COMPILE SYSPRINT includes the needed compile option changes, then tso submit jcl(cobtest#) to direct the compile sysprint output to P3.OUTPUT(#12)

Next: Challenge #13