To collect SMF records, the Execution Environment and Data Object Broker must each be executed from authorized library. They can run as either a started task or batch job.
The SMFRECORD Data Object Broker parameter is usually set at initialization. The SMFRECORD and SMF
nnINTERVAL parameters are defined in the //INITPARM DD of the Data Object Broker JCL.
If the parameter is not explicitly set (for example, if the default SMFRECORD=0 is still in effect), you can issue the following z/OS operator command to initiate the production of SMF records:
The SMFRECORD Execution Environment parameter must be set at initialization. The SMFTYPE, SMFDETAIL, and SMFPERFORMANCE parameters are defined in the //HRNIN DD of the Execution Environment JCL.
Users wanting detailed monitoring of Execution Environment SMF records can log in with the session parameter SMFDETAIL. The SMFDETAIL session parameter does not enable an individual user to turn off Execution Environment SMF monitoring.
If no Execution Environment monitoring is set up (that is, NOSFMDETAIL is specified for the Execution Environment), the session parameter has no effect.
Users wanting detailed monitoring of Execution Environment SMF records can set the session parameter SMFPERFORMANCE in addition to the SMFDETAIL session parameter. For more information about SMFPERFORMANCE, refer to
Performance Section.
If no Execution Environment monitoring is set up (that is, NOSFMPERFORMANCE is specified for the Execution Environment), the session parameter has no effect.
SMFDETAIL generates the subtype 52, 62, and 72 records and SMFPERFORMANCE generates the performance sections that can appear in these records.
TIBCO Object Service Broker for z/OS Installing and Operating for more information about Data Object Broker and Execution Environment SMF records.
TIBCO Object Service Broker Parameters for more information about individual parameters.