Importing Subcapacity reporting data with the SCRT Import utility

The SCRT (Subcapacity Reporting Tool) Import utility imports data (CSV files) which are generated from the HCL Subcapacity Reporting Tool. The import tool now also supports the importing of Tailored Fit Pricing (TFP) data. New reports to show TFP data are available in the Analyzer under the Asset tab.

MSU vs Container consumption

You need to be aware of the differences between MVM SCRT and TFP SCRT. If you want to see MSU consumption by Product, then you need to import SCRT as MVM. That way you can use the Asset reports to view MSU consumption at the product level. Be certain you choose the Metric SCRT MSU in the relevant Asset reports. If you just want to see MSU consumption at the container level, then import TFP data. TFP data does not have MSU consumption by Product. TFP has its own reports in the Analyzer.

Running the SCRT Import utility

To run the SCRT import utility, use the job HZASSCRT in the JCLLIB. This job is generated from the HZASCUST post-installation customization job.

Data input

DDNAME CSVIN contains the CSV output from the HCL ® SCRT tool which can be from a data set with DSORG of PS or PO. Binary uploaded CSV files are supported. DDNAME SIDMAP maps duplicate SMFIDs to a unique SID. The SCRT Import utility handles data where the same SMFID is used on multiple machines concurrently. DDNAME PIDMAP allows users to use SCRT data from HCL products and associate the same usage to an ISV product.

Data input example

Map SMFID on specific machines to your desired SID. As described in this example, when processing data for machine serial 11111, SMFID of IP01, assign a SID value of QIP1, where QIP1 is a SID found in the repository. More than one SMF ID can be entered. Ignore this example if there is no SMFID to map.

//SIDMAP   DD *   
11111-IPO1=QIP1
11111-IPO2=QIP2
11111-IPO3=QIP3   
/*

CPU serial: 5 alphanumeric characters
SMFID: 1 to 4 alphanumeric characters
Unique SID: 1 to 4 alphanumeric characters. This must be a SID value found in the repository.

Example for PIDMAP

To allow ISV products to use the same SCRT as an IBM product this DD allows you to map the different PID’s. Please make sure that you use the correct ISV and IBM PID’s when using this DD.

//PIDMAP DD * 
5615-DB2=ISV-001 
5694-A01=ISV-099
/*

HCL PID

The HCL PID in the SCRT that will map to the ISV PID.

ISV PID

ISV PID that will be mapped to from the HCL PID.

Data output

Several Db2® tables are populated from the data contained in CSVIN, including NODE, NODE_CAPACITY, and PRODUCT_NODE_CAPACITY. Ensure that the CSVIN DD points to the .CSV output file created by the SCRT tool. This may be a DSORG=PO or PS data set.

TPARAM parameters

COMMIT=: Default is 1000. Number of records stored before issuing a COMMIT.
DSN=: Db2® location. Value assigned, as defined in job HZASCUST.
GKBSCHEMA=: Global Knowledge Base qualifier for z/OS. Name of qualifier is &GKBZSCHM_GKB7.
REPSCHEMA=: Repository qualifier. Name of qualifier is &REPZSCHM.