Overview:

The MVS Library Analysis Program is a knowledge-based power tool which allows you to do large-scale analysis of Link Edited Load Modules, Procedure Libraries and JCL Libraries. The Analysis program extracts vital and difficult to obtain information from these libraries then reports on the contents and relationships of that data.

The user controls what data is captured and what data is reported. Initially, captured data is preserved in an OIC database. This database is highly efficient and dramatically reduces reporting run times and manual effort when compared to traditional methods of extracting and reporting on data and data relationships from multiple Partition Data Sets (PDS or PDS-E).

The OIC Library Analysis program's intelligence extracts and links key information that would normally take days or even weeks to perform manually. Extracted data and relationships are then presented in easy-to-use reports for analysis.

Our product provides a comprehensive and easy to use standard ISPF Interface. We also provide a batch utility interface which may optionally be used to produce the same report data.

The OIC reports provide critical answers to questions that are posed in many large-scale environments:

• What Load Library members belong to my application?
• What JOBS execute these modules?
• What PROCS contain JOB steps for these modules?
• What JOB steps execute these modules?
• What other applications use my load modules?
• If multiple load modules with the same name exist in different PDS's, which one is used in my application in production?
• Do any of the load libraries contain orphaned Alias names?
• What is the most current load module used in an application and where does it reside?
• When was the load module Link Edited?
• What object modules are linked to a load module?
• What languages are the object modules?
• When was the object module compiled?
• Are these linked modules CSECT or ENTRY names?
• If the load module is an ALIAS, what is its member name?
• For a given member name, are there any Alias names?
• For a given load module name, what are its Link Edited attributes?

Using traditional MVS utilities to get this information would take extensive manual effort. Furthermore, the MVS utilities are limited and are not capable of extracting the detailed reporting and cross-reference information that the OIC tool provides. Finally, depending on the size and number of PDS's involved, and to the extent that naming conventions are used, the cost of human time and computer resources to provide answers to these questions make the OIC tool an efficient and cost-effective alternative.

The OIC tool can be used for a variety of reporting purposes, including the following:

• Fine tune Y2K legacy cleanup and/or provide Y2K Due Diligence Reporting.
• Resolve program development and testing problems (Locate affected modules and their characteristics).
• Facilitate coordinated changes to called modules used by multiple applications.
• Confirm Application program inventories (Identify affected modules, subroutines, and libraries).
• Confirm Application program upgrade and maintenance efforts (Identify affected modules, subroutines, and libraries).
• Support Data Center DASD Management.
• Facilitate Enterprise Naming Standards Implementation.

The OIC product also can be used as a regular tuning and maintenance tool to assist systems programmers and application managers and developers to identify and keep track of library and application information.

The OIC Library Analysis product will execute on any OS/390 or MVS/ESA system. There are no hardware requirements other than that required by the operating system. The use of the OIC product requires no system modifications or special authorizations other than the ability to read PDS information.

This product can read and analyze data from a Standard PDS format or from the Partitioned Data Set Extended (PDSE) format. Both PDS and PDS-E formats are supported for reading Load Modules and for reading JCL Members.