The system no longer collects record type 63 as of January, 2000
Note that because VSAM catalogs are no longer supported and no longer exist, the system does not collect record type 63. However if you are using downlevel versions of SMF files, these explanations may still be useful.
Record type 63 is written when an entry (a component, cluster, catalog, alternate index, path, or non-VSAM data set) in a VSAM catalog is defined by the DEFINE access method services command and when that definition is altered. For example, when an entry in a VSAM catalog is altered with new space allocation information (that is, when the VSAM End-Of-Volume (EOV) routine extends the entire object) or, if the entry is changed by the Alter Access Method Services command. One record type 63 is written for each newly created or altered entry. This record is not written when a VSAM catalog is renamed. In that case record type 68 is written.
The record's length includes the length of the catalog records required to describe the entry. The total length can be from 1000 to 4000 bytes or more, depending upon the sizes of the new and old catalog records (offsets 44 and 46 respectively). If you write this record to the SMF data set, you must include the sizes of these catalog records when estimating the additional storage required for the SMF buffer and the SMF data sets.
Record type 63 identifies the catalog in which the object is defined, gives the catalog record for the newly defined object, and, for an alteration, gives the parts of the old catalog record before they were altered. It identifies the job by job log identification and user identification. The job name and the 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 zeros.