Using the Inventory Analyzer Reports
The Inventory Analyzer produces several reports, during and as a result of the analysis procedure. These reports provide detailed information about specific portions of the analysis and summary information for the entire procedure.
You should review these reports carefully, as they can clarify what transpired throughout the analysis procedure and present concisely the results of the exercise.
The three rule-based reports are not included in this section.
Using the SET REPORT LEVEL statement in your ANALYZE requests, you indicate which reports you want to view. The following report options are available:
- SummaryParameter Syntax, Request Syntax, Output Mwilodel Definition Syntax, Final Request Interpretation, Analysis Summary Report, Load Module Summary Report, Execution Summary Report.
- DetailDefault report level. If you do not indicate a specific report level in the ANALYZE request, you receive all the summary reports and the Request Processing Report.
- AllAll the reports provided by the DETAIL option and the Rule Syntax, Rule Analysis, and Final Rule Interpretation reports.
Do not use the All option unless you are working with Technical Support and they instruct you to run this particular set of reports.
Parameter Syntax Report
This report reflects the data entered in the program parameter (PARM= ''), if any. If no program parameter has been coded, this report is not printed. For more information about the program parameter, see
Understanding the Execution JCL.
Request Syntax Report
This report echoes each input statement from the Analysis Requests input file and checks for proper syntax. Exceptions, such as member not found, are noted with warning messages. Errors in syntax are noted and cause processing to terminate.
Output Model Definition Syntax Report
This report displays the templates you want to use to define the output format. The report echoes exactly what was coded in the Output Model Definition input file. The output model definitions are provided with the Inventory Analyzer and you should not have to change them.
For more information about required changes, see the
How to Customize the Output Model Definitionsection under
Customizing the Inventory Analyzer.
Final Request Interpretation Report
This report lists each analysis request, in order, with all applicable parameters. Any information provided by SET and CLEAR statements is merged with each request. The individual SET and CLEAR statements are not printed on the report.
Request Processing Report
This report identifies each member to be analyzed, as well as the libraries to be used, and prints the results of the analysis. If a member fails to match exactly one type and processor group, all available information about the member source and output is printed, to help you determine why the failure occurred.
The RESULT entry indicates the result of the analysis, as follows:
- A result of TRUE indicates that the member matched the type and processor group specified. A single TRUE means that there is a unique type and processor group for the member.
- A result of FALSE indicates that there is no match between the member and the type and processor group combination.
- A result of UNRESOLVED indicates that the analysis for this rule could not be performed. For example, there may be conflicting attributes, such as when the same type has two different processor groups and both rules prove TRUE.
In this and similar situations, review the rules. One of the attributes in the rule may be unclear. Or, all attributes may be correct but the rule references another rule that does not exist. You can further clarify the information needed to classify a member by editing the SCL manually.
For more information about editing the SCL manually, see
Customizing the Inventory Analyzer.
A result of UNRESOLVED does not necessarily mean there is a problem. The rule simply may not apply to the particular request, in which case it is ignored.
Analysis Summary Report
This report contains one line of summary data for each member analyzed. The source (FROM) and output (USING) libraries used for analysis are listed, along with the type and processor group (if uniquely identified) associated with the member. The page number on which the detailed analysis of the member appears in the Request Processing report is also listed.
Load Module Summary Report
The Load Module Summary Report contains one line of attribute information for each load module member analyzed. This report appears only for load modules successfully classified, and prints in order by type and processor group.
The attributes listed for each member are associated with the processor group indicated. Processors need to be created accordingly, with link-edit parameters that should match those indicated on the report. By reviewing the report, you can determine whether there are any inconsistencies within the same processor group. If you find inconsistencies, you may need to create one or more new processor groups to accommodate the different types of load modules within that particular group.
Execution Summary Report
This report summarizes the results of the entire analysis procedure:
- The first section of the report indicates the number of members that matched each type and processor group combination.
- The second section indicates the number of members both successfully processed and unsuccessfully processed, and the DDname to which each set of members was directed.
- The third section of the report provides the following information:
- The total number of members processed.
- The number of members for which processing was bypassed.
- The number of processed members for which matches were found.
- The number of members that did not match any type and processor group combination.
- The number of members that matched more than one type and processor group combination.