Load Analyzer Modernization Guide

Load Analyzer scans z/OS load libraries to identify the programming languages used within the modules. It also reports on compile and link-edit options.

Load Analyzer supports scanning load libraries containing modules written in Assembler, COBOL, PL/I, and other languages commonly used in the z/OS environment.

Load Analyzer uses JCL (Job Control Language) to specify the load libraries to be scanned and to define the output datasets. Configuration files are not typically used; instead, parameters are passed directly through JCL.

The primary output from Load Analyzer is a report dataset that lists the modules found in the scanned load libraries, along with their associated programming languages and compile/link-edit options.

Load Analyzer primarily operates as a batch utility. It does not expose APIs such as REST or SOAP. Integration with other tools typically involves parsing the output report dataset.

The core functionality involves executing the Load Analyzer program via JCL. There are no specific API endpoint patterns or method names, as it is not an API-driven application.

Load Analyzer's architecture consists of a main program module, data analysis routines, and report generation components. These components communicate internally through standard z/OS linkage conventions.

Load Analyzer reads load library datasets and writes to a report dataset. It does not use external databases. The report dataset is typically a sequential dataset.

By identifying the programming languages and compile/link-edit options used in load libraries, Load Analyzer helps organizations understand their application portfolio, plan modernization efforts, and ensure compliance with coding standards.

Load Analyzer can assist in identifying older or unsupported programming languages, allowing organizations to prioritize applications for remediation or replacement.

The reports generated by Load Analyzer can be used to track adherence to coding standards and identify inconsistencies in compile/link-edit options across different modules.

Load Analyzer operates within the security context of z/OS. It does not implement its own authentication mechanisms. It relies on z/OS security features such as RACF, ACF2, or Top Secret.

Access to load libraries is controlled by z/OS security. Load Analyzer inherits the access rights of the user ID under which it is executed.

Load Analyzer does not perform encryption. It processes load libraries and generates reports in plain text.

Load Analyzer's audit capabilities are limited to the standard z/OS SMF (System Management Facilities) records generated when the program is executed. It does not have built-in audit logging.

Load Analyzer is administered through JCL. Parameters are passed directly in the JCL EXEC statement. There is no separate administrative interface.

User management is handled by z/OS security. Load Analyzer uses the user ID under which it is executed to determine access rights.

The main configuration parameters are the names of the load library datasets to be scanned and the name of the output report dataset. These are specified in the JCL.

Load Analyzer's monitoring capabilities are limited to the standard z/OS monitoring tools and SMF records. It does not have built-in monitoring features.