Appendix A: Description of output message content

Messages generated during batch processing are explained in detail here.

Inquisitor

For each request based on scanning one or more VTOCs, the z/OS Inquisitor produces a VTOC Statistics Report unless the NOVSR keyword appears in the program parameter string.

The following table describes each of the data item columns shown in the report.

Table 1. Volume Statistics Report column headings
Item	Description
VOLUME	Volume serial number.
MAP-TO	Logical volume mapped to if mapped.
DVNO	Device number.
STOGROUP	SMS storage group name.
TCBADR-ID	LPAR record.
START-&-STOP-TIME	Start and stop times of volume scan by subtask.
WT-DELAY	Main task idle time waiting for this volume scan to complete.
ERROR-CD	Subtask processing error indicator.
VOL-CYL	Number of cylinders provided by the volume.
VTOCTRK	VTOC size in tracks.
IOERR	VTOC I/O error count.
DSCB	VTOC size in DSCBs.
VOL-DS	Number of data sets on the volume.
SCAN-DS	Number of data sets on the volume selected for scanning.
SCAN-PGMS	Number of scanned programs on the volume.

ZCAT

When the VFY=Y setting is active, the ZCAT program reads the main output data set (which is allocated to the ZCATOUT DD) to ensure that it can be processed. This output verification phase was added to assist with tracking file corruptions as files are transferred from systems where the data is collected to systems where the data is processed.

The ZCATOUT Verification Report produces statistics about the contents of the ZCATOUT file and issues a message regarding the success or failure of the verification process.

The messages have the following format:

count record read of type type

where count is the record count and type is the first two characters of the record. After the subtotal of each record type is reported, the total number of records in the file is displayed.

An example of the report contents is:

       8 records read of type UM       
     151 records read of type *C       
    2531 records read of type *D       
      16 records read of type *E       
     287 records read of type *F       
     216 records read of type *L       
       8 records read of type *P       
     382 records read of type *R       
    3599 records read from ZCATOUT file   

** ZCATOUT file verify result: SUCCESS

If an error such as a record count mismatch is discovered, then other relevant messages may be issued, followed by this message:

** ZCATOUT file verify result: FAILURE

The step completion code is set to 16 to indicate verification failure.

Table 2. Current types of Usage Monitor records (in sequence written by Usage Monitor)
Record type	Description
UM	Header record.
*E	Header Extension record.
*F	Filter description record.
*P	Registered Product usage record.
*R	Registered Product state record.
*C	Capacity record.
*L	LPAR record.
*A	APF authorized library record.
*B	Linklist library record.
*U	User name record.
*D	Detail program usage record.

IQIMPORT

When each library is matched, several statistical messages are generated that tell you what has transpired during the matching process. See the following example:

modules(processed:8,ignored:0),matched(product:0,UNKNOWN:0,none:8),loaded(identified:
0,unidentified:8)


Item	Description
Modules	processed - Total number of modules processed by IQIMPORT in the library. ignored - Total number of modules ignored.
Matched	product - How many modules are matched to a product. UNKNOWN - If there are modules known in the GKB that are not matched to a product then this is the number of modules. If 0, then none of the modules are defined in the GKB. none - Number of modules in the library known in the GKB. If 0, then all modules are known in the GKB.
Loaded	Identified - This figure signifies how many modules are associated to a product. unidentified – This indicates how many modules are not identified in the library.

As each library is matched the log indicates each scorecard for a given GKB or LKB entry and the values associated with each match. See the following example:

 Initial scores                                                       
 ==============                                                                                          
 G , ProdVerID = 2123G, Num LMODs Matched = 286/292, Version Ident = 0%, Product Ident 
 = 97%, score = 79%


Item	Description
GKB entry	G - Indicates scorecard is taken from the GKB. L – Indicates entry comes from the LKB and is user defined.
ProdVerID	Each entry in the GKB has a unique id for each version of a product. This data is used by support to find out what happened during the matching process and why some entries were not taken.
Num LMODs Matched	Indicates how many load modules are matched to the data for the given PRODVER entry. In the above example, 286 modules out of 292 in the GKB are deemed to have been identified in the library out of 292 in total in the GKB.
Version Ident	Indicates the percentage of a match to a specific version. The higher the percentage the better the match.
Product Ident	In the above example, the figure indicates the product is identified but the version is not.
score	Overall score for the scorecard entry. This score is used by the match engine after all scorecards are matched to determine what product and version the modules in the library belong to.

At the end of IQIMPORT processing a summary report is created.

======================================================
IQ Import statistics for SID:OMU3                     
======================================================
New Libraries                                     42  
Library records - imported                        42  
Library records - ignored                         0   
Module records - imported                         5487
Module records - ignored                          0   
Modules matched (product)                         5412
Modules matched (UNKNOWN) - insufficient score    8   
Modules matched (none)    - not found in KB       67  
Modules migrated(identified)                      5420
Modules migrated(unidentified)                    67  
CSECTs migrated                                   319 
Channel Path records                              10  
Control Unit records


Item	Description
New Libraries	Number of new libraries processed during IQIMPORT.
Library records	imported – The number of libraries imported into the Repository. ignored – The number of libraries not imported into the Repository. These could be distribution libraries that are filtered out by the import process.
Module records	imported – The number of modules imported into the Repository. ignored – The number of modules not imported into the Repository. This could be because they are in a library that is filtered out.
Modules matched	product – The number of modules successfully matched to a product. UNKNOWN – insufficient score – The number of modules known, but not enough to register as a known version. none – The number of modules not found in the GKB.
Modules migrated	Identified – The number of modules identified to a product that are migrated to the Repository. unidentified – The number of module unidentified that are migrated to the Repository.
CSECTs migrated	Number of CSECTs migrated to the Repository. For CSECTs to be migrated, the IQ data must be scanned with parameter SCANPGM and keyword FULLIDR otherwise no CSECT data is collected.
Channel Path records	Number of channel paths found.
Control unit records	Number of Control units found. These records are collected using the SCANDEV command in the Inquisitor.

USAGE IMPORT

When usage data is imported into a Repository, all the data imported is displayed. Multiple usage data can be imported at the same time from the same system or multiple systems. As each data is imported, a key is generated for each period.

Unique ID key from input file: UIMP_IZP5_0320210808000000_0012
Processed:UIMP_IZP5_0320210808000000_0012 Elapsed time: 0 Hrs, 00 Mins, 01 Secs

The above example indicates that the data item is the 12th item being imported from the data file. This data is probably coming from a file that has been processed by ZCAT. The elapsed time shows you how long it takes to process the file.

At the end of Usage Import processing a summary report is created. See the below example.

Input Record Statistics                                 
Number of header records read                    =    8 
Number of user records read                      =  123 
Number of detail records read                    = 6015 
Number of product usage records read             =    0 
Number of hardware capacity records read         =    8 
Number of product registration records read      =  445 
Number of registered product usage records read  =   32 
Number of machine resource records read          =   24 
                                                   ---- 
Total number of input records read               = 6655 
                                                        
Earliest period in this usage file:   Dec-2018          
Latest period in this usage file:     Jun-2019

Usage Import run completed.


Item	Description
Number of header records read	Figure indicates number of LPARs processed during Usage Import.
Number of user records read	Figure indicates total number of individual user records collected. For example, TSO ID and STC ID.
Number of detail records read	Total number of usage records processed and imported into Repository.
Number of hardware capacity records read	Figure indicates number of LPARS capacity records read. Usually one per LPAR.
Number of product registration records read	Number of records read from Usage file containing registered products.
Number of registered product usage records read	Number of records read from Usage file indicating which products have been used.
Number of machine resource records read	Resource records read from the Usage Data showing what other resources are available on the machine.