Running the Analyzer in online mode

The primary reporting facility in IBM Z Software Asset Management is the Analyzer. You can use the Analyzer in online mode to view reports, run queries, and drill down to related reports.

About this task


Note: The V8.3.1 Analyzer will support only V8.3/V8.3.1 repositories. Repositories from V8.2 are NOT supported and will not appear in the V8.3.1 Analyzer.

Note:

Db2 only: It is recommended that not more than 50 repositories be defined in a Db2 subsystem that is referenced by each Analyzer. This is to prevent overload to the Analyzer and also for easier management of repositories.

Some Analyzer reports may require extensive searches and sorts. For performance reasons, increase the sizes of the tablespaces belonging to the work file database and, also consider using different definitions for the Bufferpool (instead of the default BP0 or BP32K).

Db2 only:

The Db2 subsystem must first be active before starting up the Analyzer. After the Analyzer starts, it needs to access the Db2 Catalogs to obtain the list of repositories. If the Db2 subsystem is not active, the error message below appears in the Analyzer job log.

13:15:09(0) COULD NOT QUERY SYSIBM.SYSTABLES FOR REPOSITORY - 
SQLAllocHandle for connection handle failed - rc -1                                                      
{DB2 FOR OS/390}{ODBC DRIVER}  SQLSTATE=58004  ERRLOC=2:56:9  
  CAF "CONNECT" failed using DB2 system:DSN1                  
  RC=08 and REASON=00f30012

The Db2 subsystem can be stopped while the Analyzer is still active, but it will remain in a wait state. If a user logs in and tries to access a repository, the error message below will appear on the Analyzer report. When the Db2 subsystem is next started, users can login again and will automatically re-establish connection to Db2.
```
SQLAllocHandle for connection handle failed
 - rc -1
{DB2 FOR OS/390}{ODBC DRIVER}  SQLSTATE=58004  ERRLOC=2:56:9
  CAF "CONNECT" failed using DB2 system:DSN1
  RC=08 and REASON=00f30012         
```

HSISANLO job in the JCLLIB is used to run Analyzer in online mode as a batch job.

//HSISANLO EXEC HSIJANLO,TPARAM=HSISANP1

To run the Analyzer in online mode as a Started Task, copy the HSIJANLO from the JCLLIB to a system PROCLIB data set. Here is a sample for running the started task in a Db2 subsystem.

//HSIJANLO PROC TPARAM='HSISANP1',       TPARAM input parms   
//             CUST='HSISANCQ',                               
//             CLI='HSISCLI'     
//*                             
//ANALYZER EXEC PGM=HSICANLZ,REGION=0M,TIME=NOLIMIT
//STEPLIB  DD DISP=SHR,DSN=&DB2EXIT                
//         DD DISP=SHR,DSN=&DB2LOAD                
//         DD DISP=SHR,DSN=&HSI..SHSIMOD1          
//         DD DISP=SHR,DSN=&CEERUN                 
//         DD DISP=SHR,DSN=&CBCDLL                 
//SYSPRINT DD SYSOUT=*,LRECL=500                      
//HSIANL1  DD DISP=SHR,DSN=&HSI..SHSIANL1             
//HSIANL2  DD DISP=SHR,DSN=&HSI..SHSIANL2             
//HSICUST  DD DISP=SHR,                               
//       DSN=&HSIINST..&DB..PARMLIB(&&CUST)           
//*HSINLS   DD DISP=SHR,DSN=&HSI..SHSIANL1(HSINLSJP)  
//TPARAM   DD DISP=SHR,                               
//       DSN=&HSIINST..&DB..PARMLIB(&&TPARAM)         
//DSNAOINI DD DISP=SHR,                               
//       DSN=&HSIINST..&DB..PARMLIB(&&CLI)            
//WORK0    DD DISP=(NEW,DELETE),                      
//            UNIT=SYSALLDA,SPACE=(CYL,(100,50),RLSE) 
//APPSTATS DD SYSOUT=*,LRECL=1000                     
//APPTRACE DD SYSOUT=*

When the Analyzer is run with online mode, configuration options must be defined in the TPARAM DD, including the communication port, security mode, and inactivity timeout.