|
|
|
Data in the CA MICS database are associated with and
summarized according to the computing system that produced
the raw data used to create the observations in the CA MICS
database.
Computing systems are identified by their SMF system
identifiers (SYSIDs), which are generally unique to specific
systems. For example, SYSID=P390 might be the Model 3090
Production system. The SYSID parameter enables you to map
SMF system identifiers (CA MICS data element ORGSYSID), which
will probably change over time, to the business work that
takes place on your systems (CA MICS data element SYSID).
You can code information about the systems used at your
installation in sharedprefix.MICS.PARMS(CPLXSID) and/or
prefix.MICS.PARMS(SYSID). For this unit database,the
unit-level parameter specifications in
prefix.MICS.PARMS(SYSID) override the complex-level parameter
values from sharedprefix.MICS.PARMS(CPLXSID).
Use the worksheet in Figure 2-9 to collect the data needed to
code this parameter member.
There are three keyword parameters:
- COMPLEXSYSIDPARM IGNORE/USE
- UNDEFINEDSYSID ABORT/EXCLUDE
- SYSIDCHECK ABORT/AUTODEFINE
You can code one line containing seven parameter values for
each SYSID:
- SMF SYSID (CA MICS data element ORGSYSID)
- logical SYSID (CA MICS data element SYSID)
- CPU model
- system control program name
- RMF conversion factor
- adjustment factor
- system name
Lines beginning with '*' are comments and are ignored.
Blank statements are allowed.
Both the keyword and SYSID definition parameters are
described in greater detail later in this section. You can
begin your customization by modifying the sample SYSID member
in prefix.MICS.PARMS(SYSID).
Example System Definition Entry
-------------------------------
P390 PROD '3090-200' OS/390 . 14.6 'TSO PRODUCTION SYSTEM'
This sample entry specifies an SMF system of P390, which is
translated to the logical system PROD. The processor is a
3090-200 running OS/390; the RMF CPU conversion factor is
left as a missing value because the RMF data provides this
value, the Adjustment Factor is 14.6 (per internal
processor), and the reporting name to be displayed for this
system is TSO PRODUCTION SYSTEM. (The values used in this
example are for illustration purposes only. DO NOT assume
that they are correct for your 3090-200 processor).
Considerations for Coding SYSID
-------------------------------
By default, CA MICS terminates with a user abend if input
data comes from an SMF system that is not defined in the
unit-level parameter library. You can modify this default
behavior through control parameters.
To change unit-level SYSID parameter information after
CA MICS is in use, first change the SYSID member in
prefix.MICS.PARMS and then execute the job BASPGEN in the
prefix.MICS.CNTL library.
Considerations for Analyzers
----------------------------
Refer to the individual product guides for specific
considerations relative to specific CA MICS data integration
applications. Refer to the CA MICS System Modification
Guide for considerations relative to MTI components and Field
Developed Applications.
| INSTALLATION PREPARATION WORKSHEET: System Identifiers | | | | PARMS Library Member is SYSID | | Reference Sections: 2.3.2.2 | +--------------------------------------------------------------------------+ | | | COMPLEXSYSIDPARM ________________________ (IGNORE or USE) | | UNDEFINEDSYSID _________________________ (ABORT or EXCLUDE) | | SYSIDCHECK _____________________________ (ABORT or AUTODEFINE) | | | | | | SMF Logical CPU RMF Adjust. | |SYSID SYSID Model SCP Factor Factor System Name | +---------------------------------------------------------------------- | | P390 PROD 2817-615 z/OS . 14.6 'SAMPLE TSO PRODUCTION SYSTEM' | | | | ____ ____ ________ ____ _____ _____ '______________________________' | | | | ____ ____ ________ ____ _____ _____ '______________________________' | | | | ____ ____ ________ ____ _____ _____ '______________________________' | | | | ____ ____ ________ ____ _____ _____ '______________________________' | | | | ____ ____ ________ ____ _____ _____ '______________________________' | | | | ____ ____ ________ ____ _____ _____ '______________________________' | | | | ____ ____ ________ ____ _____ _____ '______________________________' | | | | ____ ____ ________ ____ _____ _____ '______________________________' | | | | ____ ____ ________ ____ _____ _____ '______________________________' | | | | ____ ____ ________ ____ _____ _____ '______________________________' | | | | ____ ____ ________ ____ _____ _____ '______________________________' | | | | ____ ____ ________ ____ _____ _____ '______________________________' | | | | ____ ____ ________ ____ _____ _____ '______________________________' | | | | ____ ____ ________ ____ _____ _____ '______________________________' | | | | | +--------------------------------------------------------------------------+ | ....5...10...15...20...25...30...35...40...45...50...55...60...65...70.. | +--------------------------------------------------------------------------+
Figure 2-9. System Description Worksheet
Control Parameters:
COMPLEXSYSIDPARM
Defaults to IGNORE if keyword is not specified.
Specify IGNORE to limit system definitions for this unit
database to just those systems defined in
prefix.MICS.PARMS(SYSID). With IGNORE, this unit database
is completely independent of your global (complex-level)
sharedprefix.MICS.PARMS(CPLXSID) specifications.
Specify USE to apply your global (complex-level)
sharedprefix.MICS.PARMS(CPLXSID) specifications to this
unit database.
o Use this option to define common systems once, in
sharedprefix.MICS.PARMS(CPLXSID), and avoid the
effort and risk of repeating the same information in
multiple unit databases.
o This option also helps you to react more quickly to
configuration changes by updating a single member and
running a single complex-level generation job
(CPLXGEN) rather than having to update a member and
run a BASPGEN in EACH unit database.
o You can override complex-level system definitions or
control parameter values for a specific unit database
by coding the override in prefix.MICS.PARMS(SYSID)
and running BASPGEN.
UNDEFINEDSYSID
Defaults to ABORT if keyword is not specified and you are
not using the complex-level specification for the default
value.
Specify ABORT to terminate database update processing
with a U310 abend if data comes from an SMF system that
is not defined either at the unit-level in
prefix.MICS.PARMS(SYSID) or at the complex-level in
sharedprefix.MICS.PARMS(CPLXSID).
Specify EXCLUDE to automatically drop the data that comes
from an SMF system that is not defined.
o With this option, you keep data from unexpected
systems out of your CA MICS database, as well as
avoid parameter changes, BASPGEN executions, and
database update job restarts caused by data from
unexpected sources such as test systems.
o Use the EXCLUDE option for "permanent" changes.
o To address temporary or one-time situations, specify
EXCLUDEORGSYSIDS UNDEFINEDSYSID
in prefix.MICS.PARMS(EXECDEF) to override an
UNDEFINEDSYSID ABORT specification.
SYSIDCHECK
Defaults to ABORT if keyword is not specified and you are
not using the complex-level specification for the default
value.
Specify ABORT to terminate cccPGEN processing if ORGSYSID
or SYSID values appear in a CA MICS product parameter
member (e.g., CICOPS, SMFOPS, PRFGP, etc.) but are not
defined either at the unit-level in
prefix.MICS.PARMS(SYSID), or at the complex-level in
sharedprefix.MICS.PARMS(CPLXSID).
Specify AUTODEFINE to have BASPGEN or ALLPGEN
automatically create new prefix.MICS.PARMS(SYSID) entries
for previously undefined ORGSYSID and/or SYSID values
found in CA MICS product parameter members (e.g.,
CICOPS, SMFOPS, PRFGP, etc.). With this option, the
following happens:
o BASPGEN, ALLPGEN, and product cccPGEN jobs (e.g.,
SMFPGEN, CICPGEN, etc.) continue to issue MICSLOG
warning messages when ORGSYSID or SYSID values appear
in CA MICS product parameters without corresponding
entries in prefix.MICS.PARMS(SYSID) or
sharedprefix.MICS.PARMS(CPLXSID).
o Product cccPGEN jobs (e.g., SMFPGEN, CICPGEN, etc.)
issue MICSLOG warning messages instructing you to run
BASPGEN in order to create required entries in
prefix.MICS.PARMS(SYSID).
o BASPGEN and ALLPGEN save the original, unmodified
SYSID member as prefix.MICS.PARMS(SYSIDnnn), where
nnn is a generated, unique identifier, and then
append new entries to prefix.MICS.PARMS(SYSID). You
can delete the SYSIDnnn member at any time as it is
created only to give you a "before image" of
automatic changes.
o Autodefined SYSID entries are created as follows.
- SMF SYSID (ORGSYSID) is set to the new
ORGSYSID/SYSID value from the CA MICS product
parameter member.
- Logical SYSID (SYSID) is set to match ORGSYSID.
- CPU model is set to UNKNOWN.
- System control program name is set to UNKNOWN.
- RMF conversion factor is set to missing value
('.').
- Adjustment factor is set to missing value ('.').
- System name is set to the string "SYSTEM "
followed by the ORGSYSID value.
o You can correct/revise autodefined SYSID entries by
editing the new prefix.MICS.PARMS(SYSID) and running
BASPGEN.
SMF SYSID: the Original or Input System Identifier
First, identify all of the SYSIDs currently being used.
(These are contained in SMF records and are referred to as
original system IDs.) Verify that the SYSIDs are unique.
If the SYSIDs are not unique, work with your site's system
programmers to assign unique SYSIDs to each system.
Logical SYSID: the Logical System Identifier
The logical system identifier is the key under which almost
all measurement data in the CA MICS database is stored. This
value, which is kept in the CA MICS common data element
SYSID, is the highest key in almost all CA MICS files.
You can specify that the original and logical system
identifiers have to be identical. If, however, you have a
current system identifier that may change, we urge you to
implement a unique logical system identifier.
*** Warning ***
You cannot assign two concurrently used SYSIDs to the
same logical SYSID. If a logical SYSID is specified more
than once, the CA MICS generation process will flag the
condition as an error. Contact CA Technical Support for
advice on how to handle a situation where both the
original machine and its successor run side-by-side for a
transition period.
CPU Model
Some data sources do not identify the CPU model on which the
data was produced. To help ensure that this information is
available in your CA MICS database, you can provide a CPU
model identifier in the SYSID parameter.
Code this parameter as 1-20 characters in quotation marks
(e.g., '3090-400J') with no blanks inside the quotes.
While CA MICS does not process data based on this value, it
is available to a SAS program written to run in the CA MICS
environment via a SAS macro.
SCP: the System Control Program Level
The SCP keyword provides the level of MVS currently being
run on the system described by this parameter statement.
Code this parameter as 1-10 characters with no imbedded
blanks (e.g., OS/390).
While CA MICS does not process data based on this value, it
is available to a SAS program written to run in the CA MICS
environment via a SAS macro.
RMF Factor: the RMF Service-Units-to-CPU-Time Conversion
Factor (Optional)
The RMF factor keyword asks for the value that CA MICS should
use to convert TCB and SRB service units, reported by RMF,
into CPU times.
The releases of RMF supported by CA MICS provide this value,
so code a period (translated as a SAS missing value) for this
keyword. Your "missing value" will be overridden by the
value found in the Workload Activity Record.
Note that any value other than '.' will be ignored during
processing.
Adjustment Factor (Optional)
The CA MICS database enables you to retain information about
CPU consumption in units of time. This information is
retained in elements whose names take the form fffxxxTM,
where fff is the file identifier, xxx is file-specific, and
TM stands for time.
Over time, the validity of time as a measure of CPU use
becomes questionable due to hardware environment changes.
(For example, one second of ES/9000 time is not the same as
one second of 3033 time.)
To compensate for this difference, CA MICS enables you to
retain the number of instructions executed. This information
is retained in elements whose names take the form fffxxxNI,
where fff is the file identifier, xxx is file-specific, and
NI stands for number of instructions.
The number of instructions executed is computed from the
measured CPU time and an adjustment factor you choose, such
as a MIPS rating for an MVS system. The adjustment factor is
optional. If you code a zero, the fffxxxNI elements will
have a zero value.
In choosing an adjustment factor, consider these sources:
- Conduct a hardware monitor study to determine your
processor's rating. This method yields the most
reliable results, but is costly to implement.
- Ask the hardware manufacturer for a normalized rating,
such as a MIPS rate. (If your site operates in a
multiprocessor environment, ask for the rate for a
single processor.)
- Contact a hardware monitor manufacturer and request
normalized ratings.
- Ask colleagues if they have information that they are
willing to share.
- Review the RMF Service-Units-to-CPU-Time Conversion
Factor MVS uses to normalize cpu times across different
processor models.
System Name: the Descriptive Name of the System
With this keyword you supply a 1-30 character name for the
system identified on the parameter card. This keyword must
be enclosed in single quotes.
The value you specify is used to identify the system in
certain CA MICS standard reports. It is not carried in the
database, but is available to user-written routines by means
of a SAS macro created when the CA MICS system is generated.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |