The system no longer collects record type 67 as of January, 2000
Note that because VSAM catalogs are no longer supported and no longer exist, the system does not collect record type 67. However if you are using downlevel versions of SMF files, these explanations may still be useful.
Record type 67 is written when an entry (a component, cluster, catalog, alternate index, path, or non-VSAM data set) in a VSAM catalog is deleted. A type 67 record is written for each entry affected by the DELETE access method services command. For example, three records are written for an indexed cluster: one for the relationship between the components of the cluster, one for the data component, and one for the index component.
Record type 67 identifies the deleted entry, the VSAM catalog in which the entry was defined and the deleted catalog records. A VSAM catalog record is contained in one or more physical catalog records (SMF67CRC). Field SMF67RSZ at offset 132 is the sum of the sizes of the physical catalog records that constitute the total logical VSAM catalog record. The length of this SMF record can be from 1000 to 4000 bytes or more, depending upon the sizes of the catalog records that describe the entry. If you are writing this record to the SMF data set, be sure to include the sizes of these catalog records when estimating the additional storage SMF will need for the buffers and the data sets. It identifies the job by job log identification and user identification.
The job name, time, and date that the reader recognized the JOB card (for this job) constitute the job log identification. If a system task caused the record to be written, the job-name and the user-identification fields contain blanks and the time and date fields contain zeroes.