CSI International z/OS

JCL Analyzer Modernization Guide

Tools and UtilitiesBatchSource Code

JCL Analyzer is a tools and utilities product by CSI International. Explore technical details, modernization strategies, and migration paths below.

Product Overview

JCL Analyzer is a z/OS batch utility designed to analyze JCL and provide detailed reports.

Configuration files are used to define report formats and filtering criteria.

Modernization Strategies

Rehost

Timeline:
6-12 months

Lift-and-shift to cloud infrastructure with minimal code changes. Fast migration with lower risk.

Refactor (Recommended)

Timeline:
18-24 months

Optimize application architecture for cloud while preserving business logic. Best ROI long-term.

Replatform

Timeline:
3-5 years

Complete rewrite to cloud-native architecture with microservices and modern tech stack.

Frequently Asked Questions

General

What kind of analysis does JCL Analyzer perform?

JCL Analyzer identifies all procedures, programs, JCLLIBs, and files referenced by JCL. It also reports on every job using a specific file, program, procedure, or JCLLIB. Reports are customizable through various formats and options.

What configuration files are used by JCL Analyzer?

JCL Analyzer uses configuration files to define report formats, filtering criteria, and output destinations. These files specify parameters for analysis and reporting.

Does JCL Analyzer expose an API?

JCL Analyzer primarily uses batch interfaces. Users submit batch jobs with specific parameters to generate the desired reports. There is no direct API exposure.

What are the main system components of JCL Analyzer?

JCL Analyzer's architecture includes components for JCL parsing, dependency analysis, and report generation. These components communicate through internal interfaces to process JCL and produce reports.

Technical

What are the most common operations performed by users?

Common operations include generating reports of all procedures called by a job, identifying all jobs that use a specific dataset, and listing all programs executed within a JCL.

What is the syntax for basic operations?

JCL Analyzer uses batch jobs with specific parameters to perform analysis. For example, to list all procedures called by a job, you would submit a batch job specifying the job name and the desired report type.

What types of APIs does this product expose?

JCL Analyzer does not expose APIs directly. Integration typically involves submitting batch jobs and processing the generated reports.

What are the main system components?

The main system components include the JCL Parser, Dependency Analyzer, and Report Generator. The JCL Parser analyzes the JCL syntax, the Dependency Analyzer identifies dependencies, and the Report Generator creates the output reports.

What configuration files are used?

JCL Analyzer uses configuration files to define report formats and analysis parameters. These files are typically specified as input to the batch jobs.

Business Value

How does JCL Analyzer reduce operational costs?

JCL Analyzer helps reduce operational costs by automating JCL analysis, identifying potential errors, and optimizing JCL structures. This leads to improved efficiency and reduced manual effort.

How does JCL Analyzer improve application availability?

By providing comprehensive JCL analysis, JCL Analyzer helps improve application availability by identifying and preventing JCL-related errors that could cause job failures.

How does JCL Analyzer help improve compliance?

JCL Analyzer helps improve compliance by providing detailed reports on JCL usage, ensuring adherence to standards and policies. This facilitates auditing and reporting.

Security

How is security handled in JCL Analyzer?

JCL Analyzer leverages the security features of the z/OS operating system. Access to JCL and the ability to run JCL Analyzer jobs are controlled through z/OS security mechanisms.

What authentication methods are supported?

JCL Analyzer relies on z/OS RACF or similar security systems for authentication. Users must be authenticated to the z/OS system to run JCL Analyzer jobs.

What access control model is used?

JCL Analyzer uses the z/OS access control model, which is typically based on RACF or similar security systems. Access to datasets and resources is controlled through RACF profiles and permissions.

Operations

What monitoring/logging capabilities exist?

JCL Analyzer provides logging capabilities through standard z/OS system logs. These logs capture information about job execution, errors, and other relevant events.

What administrative interfaces are available?

JCL Analyzer is administered through standard z/OS facilities, such as SDSF and other system utilities. Configuration files are managed through standard z/OS dataset management tools.

How is user management handled?

User management is handled through z/OS security systems like RACF. User access and permissions are defined and managed within RACF.

Ready to Start Your Migration?

Download our comprehensive migration guide for JCL Analyzer or calculate your ROI.

Calculate ROI