7. PARAMETERS › 7.2 Complex Level Parameters › 7.2.5 Device Level I/O Activity Data Elements(SMFDEVS) › 7.2.5.2 SMFDEVS Keyword Definitions
7.2.5.2 SMFDEVS Keyword Definitions
The SMFDEVS member supports the following keywords used in
the definition of a set of I/O activity data elements:
+-----------------------------------------------------------+
| REQUIRED KEYWORDS |
+-----------------------------------------------------------+
| ELEMENTDEF - Keyword to specify last three alphanumeric|
| characters for the new data elements that |
| are to be generated |
| |
| DEVICECLASS - Keyword to specify the Device Class |
| |
|*---------------------------------------------------------*|
||DEVICETYPE - Keyword to specify the Device Type ||
|| ||
|| OR ||
|| ||
||DEVICEADDRESS - Keyword to specify the Device Address(es)||
|*---------------------------------------------------------*|
| |
| SEMI-COLON(;) - Indicates the END of a SET of keyword |
| statements if there is MORE THAN ONE SET |
| of keyword statements |
+-----------------------------------------------------------+
+-----------------------------------------------------------+
| OPTIONAL KEYWORDS |
+-----------------------------------------------------------+
| LABEL - Used to add additional meaning to the labels |
| of the new data elements that are being |
| generated |
| |
| TIMESPANS - Used to specify timespans where I/O activity |
| data elements are active |
| |
| FILES - Used to specify specific files where I/O |
| activity data elements are populated |
| |
| MAXDEF - Used to activate the 'max' data elements and |
| specify the last alphanumeric character of the|
| data element name. |
+-----------------------------------------------------------+
These keywords are described in detail below.
+----------------------------------------------------------+
| REQUIRED KEYWORDS |
+----------------------------------------------------------+
+-------------------+
| ELEMENTDEF XXX |
+-------------------+
Arguments: XXX (1 to 3 alphanumeric characters)
Default : None
Required : Yes
The ELEMENTDEF keyword specification will be used to define
the last three characters of the data element names.
The following are examples of generated sets of data
elements for the various I/O activity files:
BATJOB - Batch User Job Activity File
JOBAZXXX XXXXXXXX Data Set Allocations
JOBCZXXX XXXXXXXX Device Connect Time
JOBEZXXX XXXXXXXX EXCPS
JOBNZXXX XXXXXXXX Data Set Allocations
BATPGM - Batch User Program Activity File
BAT_ST - System Task Program Activity File
BAT_OE - Open Edition/MVS Program File
BAT_TP - APPC/MVS TP Activity File
BAT_TS - SMF User TSO Activity File
PGMAZXXX XXXXXXXX Data Set Allocations
PGMCZXXX XXXXXXXX Device Connect Time
PGMEZXXX XXXXXXXX EXCPS
PGMNZXXX XXXXXXXX Data Set Allocations
+----------------------+
| DEVICECLASS XXXXXXXX |
+----------------------+
Arguments: XXXXXXXX (up to 8 characters)
Default : NONE
Required : Yes
This keyword identifies the specific device class of the
devices you want to collect I/O statistics for. The value of
the keyword DEVICECLASS may be one of the following: DASD,
MASSTOR, TAPE, UNIT-REC, GRAPHICS, COMMGEAR, or CTC.
The DEVICECLASS keyword must be used in conjunction with
either the DEVICETYPE keyword or the DEVICEADDRESS keyword,
not both.
+----------------+
| DEVICETYPE XXX |
+----------------+
Arguments: XXX
Default : NONE
Required : Yes
This keyword identifies the specific device types of the
devices you want to collect I/O statistics for.
The DEVICETYPE keyword must be used in conjuction with the
DEVICECLASS keyword and may not be used with the
DEVICEADDRESS keyword.
+--------------------+
| DEVICEADDRESS XXXX |
+--------------------+
Arguments: XXXX (4 alphanumeric characters) OR
XXXX-XXXX to specify a range
Default : NONE
Required : Yes
This keyword identifies the physical addresses of the devices
you want to collect I/O statistics for. It is possible to
define more than one device address (up to 13 per
DEVICEADDRESS specification). When specifying more than one
address, you must separate the addresses with a comma or
space.
When specifying a range of device addresses, the beginning
device address specification must be less than the ending
device address specification. The beginning and ending
device address specifications must be separated by a hyphen
(-). Multiple range specifications may be used for a
DEVICEADDRESS statement but must be separated by a comma or
space. Single device address specifications and range
specifications may both be utilized in a single DEVICEADDRESS
statement. (Refer to Example 4, Section 7.2.5.3 of this
guide.)
Multiple DEVICEADDRESS statements may be used if necessary;
however, no more than five are allowed.
If a device address is less than four characters, you must
right justify and zero fill to the left for each entry.
The DEVICEADDRESS keyword must be used in conjunction with
the DEVICECLASS keyword and may not be used with the
DEVICETYPE keyword.
+----------------+
| SEMI-COLON (;) |
+----------------+
Arguments: NONE (semi-colon symbol)
Default : NONE
Required : Yes*
A semi-colon (;) indicates the END of a set of I/O device
activity keyword statements.
*************************************************************
* *If there is more than one set of keyword statements, a *
* semi-colon (;) is required. *
*************************************************************
+----------------------------------------------------------+
| OPTIONAL KEYWORDS |
+----------------------------------------------------------+
+-----------------+
| LABEL XXXXXXXX |
+-----------------+
Arguments: XXXXXXXX (1 to 8 alphanumeric characters)
Default : ELEMENTDEF Definition
Required : No
The LABEL keyword can be used to construct a more meaningful
data element label. If LABEL is not defined, the ELEMENTDEF
specification will be used as part of the default label.
+----------------------+
| TIMESPANS X X X X X |
+----------------------+
Arguments: X X X X X (Y OR N)
Default : Y Y Y Y Y
Required : No
TIMESPANS keyword is used to specify the timespans where the
I/O activity data elements will be active. If TIMESPANS is
not specified, these data elements will default to active at
all timespans.
If the DETAIL timespan is defined as N and higher timespans
are active (Y), then the SMFCGEN will abort.
The statement format is:
TIMESPANS X D W M Y
where:
X - (DETAIL)
D - (DAYS)
W - (WEEKS)
M - (MONTHS)
Y - (YEARS)
+----------------------------+
| FILES XXX XXX XXX XXX XXX |
+----------------------------+
Arguments: XXX XXX XXX XXX XXX
Default : Data elements in all files
Required : No
The FILES keyword is used to select which file(s) the data
elements will populate. More than one file can be specified
with one FILES statement. When specifying more than one
file, you must separate the file identifier with one space
and no commas.
If this keyword is specified, only those files listed will
have the new data elements. If the FILES keyword is not
specified, the default is for all step and job level program
files to be populated with the new data elements.
The statement format is:
FILES XXX
OR
FILES XXX XXX XXX XXX
where XXX:
XXX - (JOB PGM _OE _ST _TP _TS)
If JOB is specified, JOB must be accompanied with either
PGM, _OE, _ST, _TP, or _TS.
************************************************************
* NOTE: Although the files affected can be tailored, *
* certain files are always populated, i.e., SFS, *
* XCS and BAT_JS if JOB is selected. *
************************************************************
+----------+
| MAXDEF X |
+----------+
Arguments: X (1 alphanumeric character)
Default : NONE
Required : No
The MAXDEF keyword will be used to activate the fffMX* data
elements. The MAXDEF specification defines the last
character of the data element names for the fffMX* data
elements.
The following are examples of generated sets of fffMX* data
elements for the various I/O activity data elements:
BATJOB - Batch User Job Activity File
JOBMXZAX XXXXXXXX Max Data Set Allocations
JOBMXZNX XXXXXXXX Max Device Allocations
BATPGM - Batch User Program Activity File
BAT_ST - System Task Program Activity File
BAT_OE - Open Edition/MVS Program File
BAT_TP - APPC/MVS TP Activity File
BAT_TS - SMF User TSO Activity File
PGMMXZAX XXXXXXXX Data Set Allocations
PGMMXZNX XXXXXXXX Device Allocations
The statement format is:
MAXDEF X
where X:
X - (1-9, A-W, Y,Z NOT X)
