Does Load Analyzer expose any APIs?

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.

What are the key operations and their syntax?

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.

What are the main system components?

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.

What databases or storage mechanisms are used?

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.

What business value does Load Analyzer provide?

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.

How does Load Analyzer help with risk mitigation?

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

How does Load Analyzer support compliance efforts?

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.

What authentication methods are supported?

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.

How is access to load libraries controlled?

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.

What encryption is used?

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

What audit/logging capabilities exist?

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.

What administrative interfaces are available?

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

How is user management handled?

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

What are the main configuration parameters?

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.

What monitoring/logging capabilities exist?

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.

Share Your Product Experience

Help the community by sharing your experience with mainframe products. Your insights help others make informed decisions.

Share Your Experience

Load Analyzer

Name: Load Analyzer
Availability: InStock

Prince Software Active z/OS

Program and Load Libraries Tools and Utilities

Vendor

Prince Software

Product Overview

Load Analyzer is a z/OS batch utility designed to analyze load libraries and provide a comprehensive view of their contents. The architecture consists of the following components: 1. **Main Program Module:** The primary executable that orchestrates the analysis process.

2. **Data Analysis Routines:** These routines identify programming languages (COBOL, Assembler, PL/I) and extract compile/link-edit options from the load modules. 3.

**Report Generation Component:** This component formats the analysis results into a report dataset. These components communicate internally through standard z/OS linkage conventions. The utility is configured via JCL, specifying input load library datasets and the output report dataset.

Security is provided by z/OS security mechanisms (RACF, ACF2, Top Secret). Load Analyzer reads load library datasets and writes to a sequential report dataset. It does not use external databases.

The utility operates within the security context of z/OS and relies on its security features for access control. Competing products may offer similar functionality, but Load Analyzer is designed for simplicity and efficiency within the z/OS environment.

Frequently Asked Questions

What information does Load Analyzer provide about load libraries?

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.

Which programming languages does Load Analyzer support?

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

How is Load Analyzer configured to scan specific load libraries?

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.

What type of output does Load Analyzer produce?

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.

Help Improve This Directory

Notice outdated information? Have insights about this product? Help the mainframe community stay informed with accurate, current data.

Report Issue Suggest Product Share Event

Share Your Product Experience

Help the community by sharing your experience with mainframe products. Your insights help others make informed decisions.

Share Your Experience

Share Your Product Experience

Load Analyzer

Product Overview

Frequently Asked Questions

What information does Load Analyzer provide about load libraries?

Which programming languages does Load Analyzer support?

How is Load Analyzer configured to scan specific load libraries?

What type of output does Load Analyzer produce?

Does Load Analyzer expose any APIs?

What are the key operations and their syntax?

What are the main system components?

What databases or storage mechanisms are used?

What business value does Load Analyzer provide?

How does Load Analyzer help with risk mitigation?

How does Load Analyzer support compliance efforts?

What authentication methods are supported?

How is access to load libraries controlled?

What encryption is used?

What audit/logging capabilities exist?

What administrative interfaces are available?

How is user management handled?

What are the main configuration parameters?

What monitoring/logging capabilities exist?

Related Products

More from Prince Software

EMT

MHT Compare

MHtran-2

Quickload

Translate R/W

Similar Products

_beta access admin

_beta access audit

_beta access easy

_beta doc|z plus

_beta doc|z transform

(E)JES

Help Improve This Directory

Share Your Product Experience