This article introduces the
EndevorInventory Analyzer tool. The Inventory Analyzer automatically classifies existing software components:
- Physical classifications (types and processor groups), which can be used withinEndevor. Types and processor groups are product physical classification of components, such as JCL or COBOL for DB2. The Inventory Analyzer provides a standard set of types and processor groups. You can change the type and processor group names to meet the inventory naming conventions you want to use.
- Logical classifications (systems and subsystems). The Inventory Analyzer helps with this type of classification by allowing you to take advantage of library and member naming standards.
- Software components, which can reside inLibrarian,Panvalet, or partitioned data sets. The Inventory Analyzer can examine source, object, or load modules. Components that are not compiled or translated (such as JCL, CLISTS, and so forth) are analyzed on a source-only basis.
Endevoris initially implemented, the system creates an inventory structure that lets you classify your source logically by application.
Endevorcreates the inventory structure by examining the following components:
- Existing component source and executables to determine component types. This is physical classification.
- Library naming conventions, or other grouping criteria, or both to determine your components' logical classification.
The Inventory Analyzer is not designed to categorize all of your software components. For more information about the product inventory structure, see
To use this product, you need a working knowledge of the mainframe environment, the z/OS mainframe operating system, Time Sharing Option facility (TSO), and the Interactive System Productivity Facility (ISPF).
Endevormust be at your site.
Administrators and application developer managers benefit from using the Inventory Analyzer.
- Administrators use the Inventory Analyzer to plan for and set up the logical and physical components of your inventory structure.
- Application Developer Managers use the Inventory Analyzer to help the administrator plan the implementation of the inventory structure.
Inventory Analyzer and the Load Utility
The Inventory Analyzer creates syntax (SCL) that can be used as input to the Load Utility. The utility lets you directly load software components into
Endevorand, optionally, to footprint executables.
The following example shows the SCL generated by the Inventory Analyzer:
LOAD MEMBER APFLIST FROM DSNAME 'BST.UTILS2.SOURCE' TO ENVIRONMENT DEMO SYSTEM FINANCE SUBSYSTEM ACCTREC TYPE ASSEM OPTIONS CCID 'TESTCCID' COMMENT 'TEST COMMENT' PROCESSOR GROUP ASHNBL13 FOOTPRINT 'BST.UTILS2.LOADLIB' LOAD MEMBER APNCO FROM 'BST.UTILS2.SOURCE' TO ENVIRONMENT DEMO SYSTEM FINANCE SUBSYSTEM ACCTREC TYPE ASSEM OPTIONS CCID 'TESTCCID' COMMENT 'TEST COMMENT' PROCESSOR GROUP ASHNBL47 FOOTPRINT 'BST.UTILS2.LOADLIB'
The previous example shows the following information:
- The environment, system, subsystem, CCID, and comment were all assigned in analysis requests (in SET statements). The Request Syntax report reflects these request statements.For more information about the Request Syntax Report, see The Request Syntax Report.
- The library in which each member is to be footprinted defaults to the USING library in which the member is found, as is indicated in the Output Model Definition Syntax Report by the line:FOOTPRINT 'C1&USDN'
The Inventory Analyzer analyzes each of the USING data sets indicated in the analysis request until it finds the member. The FROM data set is analyzed to determine whether the member exists there also.
For more information about the Load Utility, see
This illustration shows the roles of the Inventory Analyzer and the Load Utility in relation to the
The illustration details the following information:
- The Analysis Requests File provides the member names and library names to be examined and analyzed by the Inventory Analyzer. Each member is individually processed, and can be specified singly or as part of a group. Symbolics are assigned values to be included in the output data sets. Global settings can be established and overridden on an individual request basis.
- The Output Model Definition provides templates that define the format of SCL syntax that can be used to load analyzed members intoEndevor. Several templates can be identified within one input file, each directed to a separate output DD statement.
- Several reports are created that let you review selected portions of the analysis. In addition, the Inventory Analyzer creates SCL that can be entered intoEndevor. The Inventory Analyzer produces reports that contain information pertinent to a particular part of the analysis process. The following list shows the available Inventory Analysis reports:
- Parameter Syntax
- Request Syntax
- Rule Syntax
- Rule Analysis
- Output Model Definition Syntax
- Final Request Interpretation
- Final Rule Interpretation
- Request Processing
- Analysis Summary
- Load Module Summary
- Execution Summary
You can review the Inventory Analysis reports using the following detail levels: summary, detail, and all. You select the amount of data that you want to see by using a control card that is part of your analysis request.
Use the SCL that is created to load the classified elements directly into
Endevor. The elements are loaded using the Load Utility.