6. DATA SOURCES › 6.2 Data Collector and Processing Considerations › 6.2.1 SMF Recording Options › 6.2.1.1 SMF Record Type Specification

6.2.1.1 SMF Record Type Specification

Within the SMFPRMxx member of SYS1.PARMLIB, the TYPE/NOTYPE
option is used to describe the SMF records you want SMF to
collect.

The SYS parameter describes the SMF record options to be used
for all subsystems.  These include TSO, STC (started tasks),
and JES2 or JES3.  The TYPE option of the SYS parameter
specifies the record types and subtypes to be collected.  The
NOTYPE option specifies which records types are not to be
recorded.  Use either the TYPE or the NOTYPE option.
Examples of how to code the SYS parameter are found in the
System Management Facilities (SMF) documentation for the z/OS
version running at your site.

The SUBSYS parameter can be used to restrict or enhance the
SMF recording options for one or more subsystems running
under z/OS. The SUBSYS parameter not only affects collection
of SMF records written on behalf of the subsystem, but by the
subsystem as well.  Be careful when using the SUBSYS
parameter to modify record collection for started tasks
(STC).  Some started tasks (JES2, JES3, RMF, VTAM, TCAM,
NETVIEW, and so on.) generate their own SMF records.  Turning
off SMF type 6 records for started tasks would also prevent
the generation of type 6 records by JES2 or JES3.  Examples
of using the SUBSYS parameter to tailor SMF record collection
can be found in the System Management Facilities (SMF)
documentation for the z/OS version running at your site.

Note that any options specified in a SUBSYS parameter
override options specified in the SYS parameter for the
particular subsystem specified.