Sending SMF data to CPExpert


There are three steps in sending SMF data to be analyzed by CPExpert: (1) extracting the required SMF records into a separate temporary file, (2) changing the temporary file format to be RECFM=U, and (3) sending the temporary file to Computer Management Sciences, Inc. 

STEP 1: EXTRACTING THE REQUIRED SMF RECORDS

The SMF records that are used by CPExpert depend on the CPExpert component that is to be used. The following table lists the SMF records required for a basic performance analysis by the specified CPExpert component (more advanced analysis might require additional SMF records):

WLM Component

SMF RECORD TYPE DESCRIPTION
Type 23 (Subtype 2) SMF status statistics
Type 30 (Subtype 2) Interval accounting statistics

Type 41 (Subtype 3)

Virtual lookaside facility (VLF) statistics

Type 70 (Subtype 1)

RMF processor activity statistics (see NOTE)

Type 71

RMF paging activity statistics

Type 72 (Subtype 3)

RMF Workload activity

Type 73

RMF Channel path statistics

Type 74 (Subtype 1)

RMF device statistics

Type 74 (Subtype 2)

XCF statistics

Type 74 (Subtype 4)

Coupling Facility statistics

Type 74 (Subtype 5)

Cache Subsystem statistics

Type 74 (Subtype 7)

FICON Director statistics

Type 75

RMF page data set statistics

Type 77

Enqueue statistics

Type 78 (Subtype 2)

Virtual Storage activity statistics

Type 78 (Subtype 3)

I/O queuing activity and HyperPAV activity statistics

Type 88

System logger activity statistics

Type 90 System status statistics

DB2 Component

SMF RECORD TYPE DESCRIPTION

Type 70 (Subtype 1)

RMF processor activity statistics

Type 100 DB2 statistics
Type 102 (Subtype 106) ZPARMS information - optional
Type 102 (Subtype 172) Deadlock trace records - optional
Type 102 (Subtype 196) Timeout trace records - optional
Type 102 (Subtype 225) DBM1 storage trace records - optional

CICS Component

SMF RECORD TYPE DESCRIPTION

Type 70 (Subtype 1)

RMF processor activity statistics

Type 88 System logger activity statistics - optional
Type 110 (Subtype 2) CICS performance statistics
Type 110 (Subtype 3) CICS Temporary Storage Data Sharing statistics - optional
Type 110 (Subtype 4) CICS Coupling Facility Data Table statistics - optional
Type 110 (Subtype 5) CICS Named Counter statistics - optional

WebSphere MQ Component

SMF RECORD TYPE DESCRIPTION

Type 70 (Subtype 1)

RMF processor activity statistics

Type 115 WebSphere MQ Accounting statistics
Type 116 WebSphere MQ Detailed Accounting statistics
Type 74 (Subtype 4) Coupling Facility statistics (if using shared queues)

DASD Component

SMF RECORD TYPE DESCRIPTION

Type 70 (Subtype 1)

RMF processor activity statistics

Type 73 RMF Channel path statistics
Type 74 (Subtype 1) RMF device statistics
Type 74 (Subtype 4) Coupling Facility statistics
Type 74 (Subtype 5) Cache Subsystem statistics
Type 74 (Subtype 7) FICON Director statistics
Type 75 RMF page data set statistics

Type 78 (Subtype 2)

Virtual Storage activity statistics

Type 78 (Subtype 3) I/O queuing activity and HyperPAV activity statistics
 

NOTE: If you wish CPExpert to analyze PR/SM, IRD, or HiperDispatch areas, please include SMF Type 70 records for all systems in your sysplex.

You will get the most benefit from CPExpert's analysis if you select one day's data from a single system (preferably when you are at a peak in your workload or when you know that you have problems).

STEP 2:  CHANGING THE TEMPORARY FILE FORMAT TO BE RECFM=U

For development and demonstration purposes, CPExpert runs on an ascii platform (running under Microsoft Windows, and using SAS/PC).

The SMF file to be downloaded MUST be copied into a file with a specification of RECFM=U and BLKSIZE=32760. This specification preserves the VBS characteristics of the SMF file. If the VBS characteristics are not preserved, SAS/PC will not be able to process the file.

The below example shows using PGM=IEBGENER to convert the SMF file with RECFM=VBS specification to a file with RECFM=U specification.

Sample JCL to specify RECFM=U 

// EXEC PGM=IEBGENER

//SYSPRINT DD SYSOUT=*

//SYSIN DD DUMMY

//SYSUT1 DD DSN=cpexpert.SMFDATA.ORIGINAL,DISP=SHR,

//                      DCB=(RECFM=U,BLKSIZE=32760)

//SYSUT2 DD DSN=cpexpert.SMFDATA.RECFMU,DISP=(NEW,CATLG),

// UNIT=DASD,VOL=SER=CPEXPERTNNN,SPACE=(CYL,(60,5)),

// DCB=(RECFM=U,BLKSIZE=32760)

 

 

 

 

 

You should replace the "cpexpert" value with your installation-dependent specification. However, DO NOT REMOVE the RECFM=U,BLKSIZE=32760 from either the //SYSUT1 DD statement or the SYSUT2 DD statement. These attributes MUST be on BOTH the SYSUT1 and SYSUT2 statement, or the output data set will be unreadable by SAS on an ascii platform!

 

 

STEP 3: SENDING THE TEMPORARY FILE

You can send the file resulting from the above JCL as an email attachment if you wish. The email should be sent to Don_Deese@cpexpert.com.

If you are downloading the SMF data to your PC, please remember to download to your PC as a BINARY file. Otherwise the data will be converted to ascii and cannot be processed by SAS/PC.

If sending via email, you might consider zipping the file unless your installation firewall prevents sending zipped files. If the zip file is too large for email, you can use ftp to transmit the file. In this case, please request ftp instructions by sending an email to Don_Deese@cpexpert.com.

Return to main page