ConvTek converts your z/OS batch applications (MVS JCL streams and associated application code, data files, and catalogs) to new standards and naming conventions, and to a new production environment. The resulting JCL streams are easier to understand and maintain, which reduces the impact, labor, cost, time, and risk of production changes. The potential for service outages caused by JCL errors is diminished and the reaction time to such JCL errors or services outages is improved. The implementation of system-managed storage and production control tools is facilitated.  Job throughput is improved.  Software license costs are reduced.

Objective

Modify the JCL streams and associated application components to bring the batch applications in compliance with new and improved standards and naming conventions, and a new production environment.

Optionally deploy a production repository that:

• Documents the batch application jobs, files, and control cards
• Generates standardized JCL and related components for different production or test environments
• Manages the changes to batch application jobs, files, and control cards
• Integrates job maintenance and job scheduling

Justification

The reengineered JCL is easier to read, understand, and maintain, leading to:

• Simpler JCL maintenance practices
• Reduced labor, cost, implementation time, and risk of production changes
• Reduced potential for and faster reaction to service outages caused by JCL errors

The reengineered JCL is optimized for better performances leading to:

• Reduced execution times
• Increased job throughput

The reengineered JCL is fully standardized, leading to:

• Easier and more extensive system-managed storage (DFSMS) implementation
• Easier implementation of job scheduler, report manager, and automated console
• Elimination of obsolete or redundant utility programs, which eliminates redundant software license costs and simplifies technical support

Reengineering Tools

The JCL reengineering is based upon the following AXODI tools:

• AXODIT: execution-time JCL collector
• AXONORM: JCL/AXL editor
• AXODB: production repository
• AXL: job and file description language (“super” JCL)
• AXOCOMPARE: JCL comparator
• AXOFILE: file editor
• AXOJUMP: file and catalog migration
• AXOFLUX: external I/O manager

JCL Reengineering

The scope of JCL reengineering includes

• Structure of JCL streams
• Naming conventions: jobs, steps, procedures, DSN, etc
• Job header
• Usage of JOBLIB, STEPLIB, LOADLIB, etc
• Utility steps per functionality: file copy, backup, restore, FTP, etc
• DD statement structure and content
• Execution parameters and control cards
• Conditional JCL
• External input and output files
• Emails and FTP
• Print and output generation and management
• Backup and restore
• ISP-related JCL extension or features
• JCL coding patterns of interest

Production Environment Reengineering

The scope of the associated production environment reengineering includes:

• Job development and maintenance: certification and production rollout procedures
• Job preparation
• Job scheduling and submission
• Job execution control
• Operator interventions: dialog console, tape mounts, etc
• Production defects identification and resolution
• File recovery and job restart/rerun

Sample JCL Modifications

The following JCL modifications can be implemented regardless of JCL/file cross-references:

• Standardization of JCL names: job, procedure, include, parameter library, parameter library member, etc.
• Standardization of the storage of load-modules and JCL procedures/includes: JOBLIB, STEPLIB, JCLLIB, etc.
• Removal of non-required DCB attributes from DD statements that still contain them: AVGREC, BLKSIZE, etc.
• Standardization of the DISP attribute
• Replacement of JCL COND by IF
• Standardization of report management attributes and associated statements or JCL coding patterns
• Generalization and standardization of the usage of report-ids
• Standardization of SORT work files and SORT step coding patterns
• Elimination of utility steps that can be replaced by other functionally equivalent techniques, for example, replacement of IDCAMS DEL/DEF steps by JCL file allocation/deletion
• Replacement of IDCAMS REPRO by SORT COPY to improve performance
• Replacement of IEFBR14-based file deletion and un-cataloging by the use of a clean-up utility that has less system overhead and doesn't recall archived tape files (no tape mounts)
• Systematic step conversion to either eliminate obsolete or redundant products and techniques and/or to use a single coding pattern per function
• Insertion of return code setting or verification and ABEND steps for improved job execution control and restart
• Addition to all steps of a reference to a standardized JCL INCLUDE containing all references to compiler related technical files (SYS-PRINT, SYSUDUMP, etc) and elimination of any other references to those files
• Reformatting of all JCL statements to improve look, feel, and readability

Sample Program Modifications

The following program modifications are often associated with batch application reengineering:

• Resetting COBOL block sizes to zero
• Eliminating device dependence from COBOL SELECT statements

Sample Combined JCL/File Modifications

The following modifications must be coordinated based on JCL/file cross-references:

• DSN standardization
• Increased and standardized usage of GDG

Team and Logictics

The AXODI tools are initially installed on ConvTek-provided z/OS resources then reinstalled on the customer’s z/OS system when available.

ConvTek reengineering specialists work remotely.  The ConvTek project coordinator and test support team work onsite.

Pilot Analysis

Each project starts with a pilot analysis and proof of concept to:

• Get introduced to customer jobs and job reengineering requirements
• Demonstrate job reengineering capabilities
• Make initial job reengineering recommendation
• Budget and plan the job reengineering effort