Activating SMF and CMF RMF parameters


To collect performance data, the following requirements must be met:

  • SMF and CMF or RMF must be active.
     
  • SMF must have the IEFU83 and IEFU84 exits specified for the areas for which data collection is desired.
     
  • The SMF global recording interval should be specified unless the system default of 30 minutes is acceptable. The SMF global recording interval should be synchronized with some part of the hour unless the system default of 00 is acceptable.
     
  • The CMF or RMF recording interval duration must be equal to or an even multiple of the SMF recording interval duration. For example, if the SMF recording interval duration is 30 minutes, the CMF or RMF recording interval may be 5, 10, 15, or 30 minutes.
     
  • The CMF or RMF recording interval must be synchronized to the same part of the hour as SMF.
     
  • Generally SMF types 30, 42, 73, 74, and 78 records must be collected. However, the SMF type 73 and 78 records are not required when running on a VM guest. The SGP_SMF42 system parameter in the SMMSYSxx member can control the actual recording of the type 42 records in the SMF data set.
     
Warning

Due to limitations in RMF and CMF, BMC Software cannot gather channel activity and I/O queuing statistics about a VM guest. Therefore, the performance collector data will be incomplete when running on a VM guest.

For more information, see:

CMF requirements for data collection

The recording interval of either CMF or RMF must be equal to or an even multiple of the SMF recording interval.

The following parameters are the minimum required for CMF:

RECORD INTERVAL=xx,RUNTIME=1440,SMF=YES,SYNCH=yy
CHANNEL
DEVICE class="DASD"

In this example, xx is equal to or an even multiple of the SMF recording interval duration; yy is equal to the SMF recording interval part of the hour synchronization value.

The following table lists the keywords required in the CMFCPMxx member to collect the specified records.

 

Record type

Required keyword

Data collected

Type 73

CHANNEL

Channel activity

Type 74-1

DEVICE

Device activity

Type 74-2

XCFDATA

Cross-system coupling facility (XCF)

Type 74-3

OMVS

Open edition IBM MVS

Type 74-4

CFDATA

Coupling facility

Type 74-5

CACHE

Cache data records

Type 78-1

IOQ

I/O queuing data for 4381 and 3080 processors

Type 78-2

VSMDATA

Virtual storage data

 

RMF requirements for data collection

If you are running RMF, the PARMLIB member must specify the following measurement, timing, and recording options:

 

Measurement

CHAN

DEVICE(DASD)

Timing

SYNC(SMF) (synchronizes SMF/RMF intervals)

Recording

RECORD

 

To create RMS post processor-compatible 74-5 records, you must stipulate the following in CMFCPMxx:

CACHE CMFREC=74

CACHE CMFREC=74 generates 74-5 SMF records and 240-27 records, whereas, the CACHE keyword used alone generates 240-27 records for the BMC Software proprietary cache reports.

SMF requirements for data collection

The following example shows how to set up SMF for the proper exits and recording of SMF records:

INTVAL(15)                   /*GLOBAL INTERVAL)*/
SYNCVAL(15)                  /*Synchronization value*/
ACTIVE                       /*ACTIVE SMF RECORDING*/
DSNAME(SYS1.MAN1,SYS1.MAN2,SYS1.MAN3)  /* THREE DATA SETS */
NOPROMPT                    /*DO NOT PROMPT OPERATOR FOR OPTIONS*
REC(PERM)                   /*TYPE 17 PERM RECORDS ONLY*/
MAXDORM(3000)               /* WRITE AN IDLE BUFFER AFTER 30 MIN*
STATUS(010000)              /* WRITE SMF STATS AFTER 1 HOUR*/
JWT(0800)                   /* 522 AFTER 8 HOURS   */
SID(SYSG)                   /* SYSTEM ID IS SYSG */
LISTDSN                     /* LIST DATA SET STATUS AT IPL*/
LASTDS(MSG)                 /*DEFAULT TO MESSAGE          */
NOBUFFS(MSG)                /*DEFAULT TO MESSAGE          */
SYS(EXITS(IEFU83,IEFU84,IEFACTRT,IEFUJV,
 IEFUSI,IEFUJI,IEFUTL,IEFU29),INTERVAL(SMF,SYNC),
 NODETAIL
SUBSYS(STC,EXITS(IEFU29,IEFU83,IEFU84,IEFUJP,IEFUSO),
 INTERVAL(SMF,SYNC))
SUBSYS(xxxx,EXITS(IEFU29,IEFU83,IEFU84,IEFUJP,IEFUSO),
 INTERVAL(SMF,SYNC))    /*xxxx IS SUBSYSTEM CMF TASK IS USING */

Note

The performance collector uses data spaces. Whenever you use large MVS/ESA data spaces, you should ensure that sufficient auxiliary storage is available on your system to support any related MVS/ESA paging activity. You might also need to increase the size of your SYS1.DUMP data sets.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*