SMF data collection for job analysis
SMF monitoring of BMC ThruPut Manager activity
A BMC ThruPut Manager facility is provided for an installation to gather statistical information about BMC ThruPut Manager's activity while analyzing jobs. An SMF record containing this information is generated for each job.
The data collected includes:
- CPU time used to interpret job.
- CPU time used to analyze job.
- Number of catalog LOCATEs.
- Number of DD statements.
- Number of DASD volumes and tape volumes.
Activating data collection
JEF data can be collected and made available automatically. To activate SMF data collection, you must include an initialization statement:
Syntax | Description |
|---|---|
smf-record | Specifies a value from 128 to 255, representing the SMF record number to be used. |
ANALYZER | Specifies the job analyzer to collect the default SMF data. For more information, see the SMF Performance Recordtable. |
ANALYZER(table-id[,subtable-id]) | Specifies the Job Analyzer to collect data in addition to the default data.
|
DBS | Specifies that the DBS application is to collect SMF data. For more information, see Drive-Booking-Services-System-Programming-guide. |
DCS | Specifies that the DCS application is to collect SMF data. As of release 22.4, DCS SMF data collection is enabled by default and is not required to be specified. For more information, see Dataset-Contention-Services-System-Programming-Guide. |
SLM | Specifies that SLM data is to be recorded. As of release 22.4, SLM SMF data collection is enabled by default and is not required to be specified. For more information, see Setup Guide to BMC AMI Ops Automation for Batch ThruPut Essentials. The mapping macro DTMSMFPR is provided to assist you in analyzing the collected data. |
JOB_HIST | Specifies that Job History SMF records are to be collected. JOB_HIST SMF data collection is enabled by default and is not required to be specified. For more information, see Part-10-Job-History-SMF-data-collection. |
Summary of BMC ThruPut Manager SMF record
The following table is intended for use as a guide only. If there is a discrepancy between this summary and the mapping macro DTMSMFPR, the macro is correct. This table reflects only the data collected by default.
BMC ThruPut Manager SMF Performance Record | |||
|---|---|---|---|
For specific mapping, refer to macro DTMSMFPR | |||
Name | Type | Length | Description |
SMFTMLEN | binary | 2 | Record length |
SMFTMSEG | binary | 2 | Segment descriptor |
SMFTMFLG | binary | 1 | System indicator |
SMFTMRTY | binary | 1 | Record type |
SMFTMTME | binary | 4 | Time since midnight (in 100ths of seconds) record was sent to SMF writer |
SMFTMDTE | packed | 4 | Date (in the form yyddd) record was sent to SMF writer |
SMFTMSID | char | 4 | System identification |
SMFTMWID | char | 4 | Subsystem identifier |
SMFTMSTP | binary | 2 | Record subtype: 15 for BMC ThruPut Manager 6 for DCS |
SMFTMJBN | char | 8 | Job name |
SMFTMRST | binary | 4 | Reader start time (in 100ths of seconds) |
SMFTMRSD | packed | 4 | Reader start date (yyddd) |
SMFTMJNM | char | 8 | JES job identifier |
SMFTMINT | binary | 4 | CPU time used by interpreter and Job Ana- lyzer initiation |
SMFTMJAT | binary | 4 | Total CPU time used by Job Analyzer |
SMFTMCTA | binary | 4 | Number of catalogs allocated during Job Analysis |
SMFTMLRQ | binary | 4 | Number of catalog locates required |
SMFTMLCM | binary | 4 | Number of catalog locates using catalog management |
SMFTMLCA | binary | 4 | Number of catalog locates using catalog lookaside |
SMFTMNDD | binary | 4 | Number of DD statements |
SMFTMNDA | binary | 4 | Number of DASD volumes |
SMFTMTC | binary | 4 | Number of tape cartridge volumes |
SMFTMJST | char | 4 | Job status (OKAY, FAIL, or FLSH) |
SMFTMACS | char | 1 | ACS support indicator (Y for active, N for inactive) |
SMFXFENO | binary | 4 | Number of XFE extensions |
SMFTMELP | binary | 8 | Elapsed time in Analyzer |
SMFTMNOM | binary | 1 | Number of this record |
SMFTMNON | binary | 1 | Total number of records |
If the field SMFTMNON is greater than 1, there is more than one SMF record for this job. If the records are sorted in ascending order by SMFTMNOM, the last record has been processed when SMFTMNOM equals SMGTMNON, which is m of n records.
Record Subtypes
Some BMC ThruPut Manager applications allow you to collect SMF data specific to the application. The primary BMC ThruPut Manager SMF record mapped by DTMSMFPR contains a subtype indicator in the field SMFTMSTP:
- 15 indicates a BMC ThruPut Manager Analyzer record.
- 6 indicates a DCS record. For details about the use of this subtypes. For more information, see Dataset-Contention-Services-System-Programming-Guide.
- 19 indicates a BMC ThruPut Manager Job History record. For more information, see Part-10-Job-History-SMF-data-collection.
Collecting more than default JEF data
The TM SMF initialization statement allows you to collect more than the default JEF data. The additional data is added to the SMF record in XFE format, except that the field XFENEXT is an offset, not an address. The offset is relative to the start of the SMF record, including the RDW.
To extract the additional data, you must create a BMC ThruPut Manager table containing the tokens you wish to extract. BMC ThruPut Manager tables are described in the Table (TBL) Function section.
The table is defined in the usual manner, except that any Token name containing the underscore (_) character must be enclosed in quotes.
Here is a sample table:
SUBTABLE(SMFDATA)
$JOBNAME,$INCLASS
$INSYSID
JLSLIMIT
‘$UNIT_CART_ALL’
If this table were called table 9 to match the SMF exit number, the load statement could look like this:
Now modify the TM SMF initialization statement to point to the table:
The XFEs are appended to the end of the standard BMC ThruPut Manager SMF data. The DTMSMFPR macro has been updated to reflect this.