

7. PARAMETERS › 7.2 VTS Component Parameters › 7.2.3 VTS Component Unit Level Parameters › 7.2.3.1 VTS Processing Options (VTSOPS) › 7.2.3.1.1 SMFTYPE Statement
7.2.3.1.1 SMFTYPE Statement
The SMFTYPE statement is optional. This statement is used to
restrict the SMF record types accepted by a unit to a subset
of the record types specified on the
sharedprefix.MICS.GENLIB(VTSGENIN) INPUTSOURCE statement.
See Section 7.2.2.1 for more information on the VTSGENIN
INPUTSOURCE statement.
By default, any unit containing the VTS component will accept
and process all SMF record types in the input data file that
match the SMF record types specified by the complex level
VTSGENIN INPUTSOURCE statement.
If you need to implement the VTS component in two or more
units, use the SMFTYPE statement to ensure that each unit
processes a specific set of SMF record types.
The SMFTYPE statement has the following format:
SMFTYPE nnn1 nnn2 ... nnn7
where:
nnn1-nnn7 Are any subset of the SMF record types specified
on the VTSGENIN INPUTSOURCE statement.
There is no default. If a SMFTYPE statement is not coded,
all SMF record types specified on the INPUTSOURCE statement
will be accepted and processed.
The SMF record types coded with the SMFTYPE statement in
prefix.MICS.PARMS(VTSOPS) must be a subset of the SMF record
types specified on the INPUTSOURCE statement in VTSGENIN. A
maximum of seven record types can be coded. Coding or
changing SMF record types on the SMFTYPE statement in VTSOPS
requires execution of prefix.MICS.CNTL(VTSPGEN).
Example:
A data center has recently consolidated three sites: one with
an IBM VTS (SMF type 94), and two with StorageTek VSM
systems. One of the sites with StorageTek is creating SMF
record type 253 and the other is creating SMF record type
254.
The site has created three separate units for processing data
from the consolidated sites, each with a VTS component step:
o Unit A will process the IBM VTS data.
o Unit B will process the StorageTek SMF type 253 records.
o Unit C processes the StorageTek SMF type 254 records.
The complex-level INPUTSOURCE statement must specify ALL
record types. The unit level subsetting is achieved using
the following SMFTYPE statements.
COMPLEX LEVEL
sharedprefix.MICS.GENLIB(VTSGENIN)
...
...
INPUTSOURCE SMF 94 253 254
...
...
UNIT LEVEL
prefix.MICS.PARMS(VTSOPS)
UNIT A
...
SMFTYPE 94
...
UNIT B
...
SMFTYPE 253
...
UNIT C
...
SMFTYPE 254
...
If SMF data is proactively filtered so that the records
presented to a VTS component are already restricted to the
record types that you want, no SMFTYPE statement is required.
The coding of an SMFTYPE statement, however, can act as an
insurance policy to protect against the accidental inclusion
of unwanted virtual tape SMF record types in the raw data
presented to a unit.
Copyright © 2014 CA.
All rights reserved.
 
|
|