IBMSystem Management Facility is a component of IBM's z/OS for mainframe computers, providing a standardised method for writing out records of activity to a file. SMF provides full "instrumentation" of all baseline activities running on that IBM mainframeoperating system, including I/O, network activity, software usage, error conditions, processor utilization, etc. One of the most prominent components of z/OS that uses SMF is the IBM Resource Measurement Facility. RMF provides performance and usage instrumentation of resources such as processor, memory, disk, cache, workload, virtual storage, XCF and Coupling Facility. RMF is technically a priced feature of z/OS. BMC sells a competing alternative, CMF. SMF forms the basis for many monitoring and automation utilities. Each SMF record has a numbered type, and installations have great control over how much or how little SMF data to collect. Records written by software other than IBM products generally have a record type of 128 or higher. Some record types have subtypes - for example Type 70 Subtype 1 records are written by RMF to record CPU activity.
SMF record types
Here is a list of the most common SMF record types:
RACF type 80 records are written to record security issues, i.e. password violations, denied resource access attempts, etc. TopSecret, another security system, also writes type 80 records. ACF2 provides equivalent information in, by default, type 230 records but this SMF record type can be changed for each installed site.
SMF type 89 records indicate software product usage and are used to calculate reduced sub-capacity software pricing.
DB2 writes type 100, 101 and 102 records, depending on specific DB2 subsystem options.
CICS writes type 110 records, depending on specific CICS options.
Websphere MQ writes type 115 and 116 records, depending on specific Websphere MQ subsystem options.
WebSphere Application Server for z/OS writes type 120. Version 7 introduced a new subtype to overcome shortcomings in the earlier subtype records. The new Version 7 120 Subtype 9 record provide a unified request-based view with lower overhead.
Evolving records
The major record types, especially those created by RMF, continue to evolve at a rapid pace. Each release of z/OS brings new fields. Different processor families and Coupling Facility levels also change the data model.
The standard and classical way: Using buffers the SMF address space, together with a set of preallocated datasets to use when a buffer fills up. The standard name for the datasets is SYS1.MANx, where x is a numerical suffix.
The relatively new way: Using log streams. SMF utilizes System Logger to record collected data, which improves the writing rate and avoids buffer shortages. It has more flexibility, allowing the z/OS system to straightforwardly record to multiple log streams, and allowing z/OS to read a set of SMF data once and write it many times.
Both the two ways can be declared for the use, but only one is used at a time in order to have the other as a fallback alternative. This data is then periodically dumped to sequential files using the IFASMFDP SMF Dump Utility . IFASMFDP can also be used to split existing SMF sequential files and copy them to other files. The two dump programs produce the same output, so it does not involve changes in the SMF records elaboration chain, other than changing the JCL with the call of the new dump utility.
