zPulse · Disk
How to read RMF 74.1 DASD response time: CONN, DISC, PEND, IOSQ
RMF 74.1 DASD response time is IOSQ, pending, disconnect and connect time added up. Learn what each part means and in which order to read them on z/OS.
zPulse · Tape
SMF 21 records each tape demount with its volume, drive and error counts. See what it brings to tape mount analysis on z/OS, and what you need beside it.
SMF 21 tells you that a tape volume was demounted, on which drive, and how many read errors, write errors and start subchannel operations it saw while mounted. For tape mount analysis on z/OS it gives a count per volume and drive, but not the wait of the job nor what happened inside a virtual tape library.
This article explains what an SMF 21 record contains, how to count mounts with it, where its limits are, and which other sources complete the picture.
SMF record type 21 (X’15’) is the Error Statistics by Volume record, or ESV. z/OS writes it when a data set on magnetic tape is demounted. It holds statistics for the whole volume over the time it was mounted, however many data sets were read or written and however many times they were closed.
The IFHSTATR utility formats and prints these records. Many sites also load them into their own performance database, next to the other SMF types.
One detail matters for counting: a type 21 record is also written when EREP runs and when EOD is issued. More than one record can exist for a single mount.
The record describes a volume and the drive it was mounted on. The table below groups its content by use.
| Content | What it tells you | Use in tape mount analysis |
|---|---|---|
| Volume serial | Which tape volume was mounted | The volumes mounted most often, repeated mounts of the same volume |
| Device number and unit type | Which drive, and which device type | Mounts per drive and per device type, real or virtual |
| Tape format | How the volume was recorded | Separating media generations |
| Temporary and permanent read and write errors | How the volume and drive behaved | Failing media or drives, before they cause job failures |
| Start subchannel (SSCH) count | How much I/O the mount carried | Short mounts with little I/O against heavy ones |
| Noise blocks, erase gaps, cleaner actions | The physical condition of media and drive | Maintenance of real tape drives |
| Record date and time | When the demount happened | Mounts per hour, and the peaks of the day |
Free study
See your own tape activity in zPulse
Send us your RMF or CMF tape reports, VEHSTATS files and tape catalogue reports. A Technical Storage expert runs them through zPulse Tape and walks you through mounts, cache and fill rates.
A mount count from SMF 21 is simple in principle: one demount, one record. In practice, four steps keep the count honest:
The result answers questions such as “how many mounts per hour during the night?” or “which volumes are mounted again and again?”. It is a good start for a tape mount analysis, and often the first evidence that a workload should move from real to virtual tape, or the other way round.
SMF 21 is about volumes and drives. Several questions of a full tape mount analysis need other data:
% MT PEND).| Source | What it adds |
|---|---|
| SMF 21 | Demounts per volume and drive, with error counts |
| SMF 30, 14 and 15 | The job and the data sets behind each mount |
| RMF Magnetic Tape Device Activity (CMF Tape Activity Report) | Activity and response time per tape device and interval |
| TS7700 statistics, retrieved with BVIR and reported by VEHSTATS | Virtual and physical mounts per cluster, cache use and throttling, virtual drives |
| Tape management catalogue (DFSMSrmm, CONTROL-T, CA-1) | Active and scratch volumes, file counts, capacity and fill rate |
The TS7700 keeps point-in-time and historical statistics. The BVIR facility retrieves them to the host, and the IBM Tape Tools utility VEHSTATS turns the historical statistics into reports on mounts, data transfer and use of the library.
Let us be precise: zPulse does not read SMF 21, nor any raw SMF record. zPulse Tape works from the reports that already summarise tape activity:
A scheduled tape study can send a standard report with the catalogue charts, a tape performance mail and a VEHSTATS mail, each with the covered period in its subject. The zPulse overview shows how tape fits with the Disk, CPU and Space modules.
To see this on your own data, request a free study: send your tape reports, VEHSTATS files and catalogue reports, and a Technical Storage expert walks you through the results.
Indirectly. SMF 21 is written when a tape volume is demounted, so counting the records approximates the number of mounts. It is also written when EREP runs or when EOD is issued, so remove those extra records before you count.
No. On virtual tape, SMF 21 describes the virtual volume seen by z/OS. Physical mounts and recalls inside the TS7700 come from its own statistics, retrieved with BVIR and reported with tools such as VEHSTATS.
SMF 21 is a volume and drive record. To link a mount to a job, correlate it with job and data set records such as SMF 30, 14 and 15, or with your tape management system.
No. zPulse reads no raw SMF records. For tape it reads the RMF or CMF tape device activity reports, TS7700 VEHSTATS files and tape management catalogue reports from DFSMSrmm, CONTROL-T or CA-1.
Founder, Technical Storage · z/OS storage performance
Founder of Technical Storage, the z/OS storage performance company behind zPulse. Measuring mainframe Disk, Tape and CPU workloads since 1997.
Keep reading
zPulse · Disk
RMF 74.1 DASD response time is IOSQ, pending, disconnect and connect time added up. Learn what each part means and in which order to read them on z/OS.
z/OS storage
A z/OS storage performance glossary: the measurement, disk, CPU, tape and space terms of RMF, CMF and DCOLLECT data, each defined in one plain sentence.
z/OS storage
A zPulse daily mail comes from a scheduled study, with charts in the body and the period in the subject. Learn to read the DASD, CPU, DCOLLECT and tape mails.