UIE - What does UIE error message UIE4420E indicate?

Version 1

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    BMC Capacity Management for Mainframes


    BMC Performance Analyzer for Mainframes


    What is the cause of the following messages in the UIE SYSPRINT and DEBUGPR reports?

              REFERENCE NUMBER 2316 IN DEBUGPR.                          
              REFERENCE NUMBER 2317 IN DEBUGPR.                          
    UIE4420E: FOR APPLICATION @@GM SUITE CICS_ON1_CICS HAS NO ACTIVITY.                                                              
              REFERENCE NUMBER 2316 IN DEBUGPR.                                                                                      
          2316 @@GM      ;SYSA    125      5      1      2      1      2      8                                                       
       REQ:  C SYSA CICSP01   EXEC:  C SYSA CICSP01                                                                                  
     VAL:   3.00E+00  3.00E+00  3.00E+00  3.00E+00  9.04E-03  0.00E+00  0.00E+00  0.00E+00  0.00E+00  0.00E+00  0.00E+00  3.37E-02   


              REFERENCE NUMBER NNNN IN DEBUGPR.                             
    Meaning:  For application AAAAAAAA, the SUITE BBBBBBBB has no activity. 
              The reference number refers to a message in the DEBUGPR file, 
              which contains additional diagnostic information.  As a       
              result of this message, no application data for the           
              application AAAAAAAA will be written to the XML or            
              Visualizer data sets.                                         
    Solution: UIE creates workloads, suites, and applications.  Workloads   
              are created primarily from RMF type 72 data and represent     
              collections of Performance Groups, Services Classes, and      
              Report Classes.  Suites are created primarily from the SMF    
              type 30 data and represent collections of jobs and address    
              spaces.  Applications are created primarily from the          
              various monitor data and represent collections of subsystem   
              transactions or jobs that execute in one or several workloads 
              (CICS or IMS regions, DB2 subsystems, and so on).             
              Applications perform internal resource management, sharing,   
              and pooling.  Even if it is possible to determine actual      
              resources used by a particular transaction, these              
              measurements can be misleading.  For example, a particular     
              transaction can require reading multiple data blocks from      
              DASD, and several subsequent transactions can reuse the data   
              from buffers without performing an I/O operations.  Also,      
              in some cases the monitor data may not provide a full          
              accounting of all the resources used by the subsystems.  For   
              example, CICS monitor data contains CICS application CPU but   
              it does not contain any overhead CPU.  Therefore,              
              applications are not represented by UIE as workloads but as    
              resource consumption profiles.  These profiles exist in        
              parallel with actual Suites, which is where the resources      
              for transactions are consumed.                                 
              In order for UIE to generate the application profiles, it      
              needs to match application data to the suites where the        
              actual CPU and I/O is consumed.  UIE matches the application   
              data to Suites based on the jobname found in the               
              application data and the SMF type 30 data.  If UIE does not    
              find a match between the application jobnames and the Suite    
              jobnames, it generates the UIE4420E message.  The same         
              message will be written to the DEBPUGPR file and will contain  
              additional diagnostic information, including the system ID        
              and the jobname for the application.                              
              The most likely causes of the UIE4420E message are:               
              1) Type 30 records were not found for the jobs or address         
                 spaces associated with the application for this interval.      
                 Verify that you are collecting type 30 records for all         
                 subsystem jobs/address spaces for all intervals.  To see       
                 which jobs/address spaces were found in the type 30            
                 records, add the SETDEBUG JOBS command to the UIE batch job    
                 in-stream commands and re-run the UIE job.  This command       
                 will generate a list of jobnames that were found in the        
                 data and write this list to the DEBUGPR file (make sure        
                 that the DEBUGPR DDname is not DD DUMMY - it should have       
                 a data set allocated or be set to SYSOUT=sysoutclass).         
              2) Review your batch job in-stream commands and verify that       
                 you have not excluded the subsystem type BBBB by the use       
                 of the SEPARATESUBSYS command or the SEP_SUBSYS parameter      
                 on the SUITE command.                                          

    Article Number:


    Article Type:

    Solutions to a Product Problem

      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles