|
|
|
Certain parameters that affect the execution of the standard
CA MICS jobs can be altered at any time without regenerating
the CA MICS system. These parameters let you specify whether
CA MICS will run some, all, or none of the exception modules
for the installed system. They also let you specify report
options, weekend scheduling options, and certain data
retention options.
These parameters are specified by changing the EXECDEF member
of MICS.PARMS. A sample EXECDEF member is listed below,
followed by an explanation of each parameter statement.
Note: We strongly recommend that you use the default member
when CA MICS is first installed. After some experience is
gained with the system, the parameters can be adjusted as
needed using the worksheet in Figure 2-43. Note that changes
made to EXECDEF take effect with the next CA MICS job and do
not require any generation process.
*
* EXECUTION OPTION DEFINITIONS
*
CREATE EXCEPTIONFILES NONE
REPORT EXCEPTIONS NONE
REPORT MBODAILY ALL
REPORT MBOWEEKLY ALL
REPORT MBOMONTHLY ALL
REPORT WORKSPACE NO
SCHEDULE WEEKEND NO
INPUTLOGLIMIT 99
SMFDJHLLIMIT 99
SPCUTILLIMIT 99
EXCLUDEORGSYSIDS T168 T033
TITLE CA MICS PRIMARY DATABASE
Figure 2-42. Sample EXECDEF Member
CA MICS supports a separate exception module for each of its
products. Exception modules read newly-created cycles,
looking for observations that meet exception criteria. Each
site defines its own exception criteria. (For detailed
information about tailoring exceptions, see the Standard
Reports Guide.) When exception modules detect what they
consider to be an exceptional condition, they record it in a
record in the DAYS.ADMEXC file. The following statement
allows you to control this process.
CREATE EXCEPTIONFILES:
Specify NONE, ALL, or a list of one or more CA MICS
products to define if the DAILY exception modules should
be run. For more information on generating exceptions
in the DAILY update job, see Chapter 2, "Exception
Reports," in the Standard Reports Guide.
Whether any exceptions that are found are reported is
determined by the REPORT EXCEPTIONS parameter below or
by your MICF inquiry production reporting definitions.
You can choose to create the exception files, but not
activate daily reporting in order to have exceptions
available for online inquiry using MICF.
NONE - Do not run any exception modules (the
DAYS.ADMEXCnn files will exist, but will always
be empty).
ALL - Run the exception modules for all installed
CA MICS products.
list - Run the exception modules for the listed CA MICS
products. Product IDs are separated by blanks.
Note that all exceptions identified by all exception
modules go into a single CYCLE of the DAYS.ADMEXC file
with one record per exception detected. The INFOAREA
field of the records indirectly identifies the product.
REPORT EXCEPTIONS:
Specify NONE or a list of one or more levels of
exception reporting that should be done for all CA MICS
products whose exception modules were run in the DAILY
update job. See the CREATE EXCEPTIONFILES discussion
above for more information on creating exceptions.
Specify NONE if you are using MICF inquiry production
reporting facilities to generate daily CA MICS exception
reports. For more information on executing daily MICF
inquiry production reports with the CA MICS DAILY
database update, see the MICF Reference Guide.
NONE - Do not produce any Daily Exception Reports.
OVERVIEW - Produce the Daily Exception Report Overview.
SEVERITY - Produce the Daily Exception Report list of
exceptions by severity level (Critical,
Impacting, and Warning).
MGMTAREA - Produce the Daily Exception Report list of
exceptions by Management Area (Performance,
Security, Standards, Workload, and so on).
DETAIL - Produce the Daily Exception Report detail
list of exceptions.
The standard report options control the production of the
Daily, Weekly, and Monthly management objective (MBO) reports
(see the Standard Reports Guide). Each report option must
specify NONE for no reports, ALL for MBO reports from all
installed products, or a list of one or more CA MICS product
names. For more information, see the COMPONENTS statement in
Section 2.3.3.2.1.1, Control Definitions.
Specify NONE if you are using MICF inquiry production
reporting facilities to generate Daily, Weekly, and Monthly
MBO reports. For more information on executing daily,
weekly, and monthly MICF inquiry production reports with the
CA MICS daily, weekly, and monthly production processing, see
the MICF Reference Guide.
REPORT MBODAILY:
Specify NONE, ALL, or a list of one or more CA MICS
products to define if the standard Daily Management
Objective Reports should be produced.
NONE - Do not produce any Daily Management Objective
Reports.
ALL - Produce the Daily Management Objective Reports
for all installed CA MICS products.
list - Produce the Daily Management Objective Reports
for the CA MICS products listed. Product IDs are
separated by blanks.
REPORT MBOWEEKLY:
Specify NONE, ALL, or a list of one or more CA MICS
products to define if the standard Weekly Management
Objective Reports should be produced.
NONE - Do not produce any Weekly Management Objective
Reports.
ALL - Produce the Weekly Management Objective Reports
for all installed CA MICS products.
list - Produce the Weekly Management Objective Reports
for the CA MICS products listed. Product IDs
are separated by blanks.
REPORT MBOMONTHLY:
Specify NONE, ALL, or a list of one or more CA MICS
products to define if the standard Monthly Management
Objective Reports should be produced.
NONE - Do not produce any Monthly Management Objective
Reports.
ALL - Produce the Monthly Management Objective Reports
for all installed CA MICS products.
list - Produce the Monthly Management Objective Reports
for the CA MICS products listed. Product IDs are
separated by blanks.
REPORT WORKSPACE:
Specify YES or NO to control whether or not the MICS
Work Space Utilization Report is to be generated. If
left blank or unspecified, the default is NO. For more
information refer to section 4.3.15.
SCHEDULE WEEKEND:
A process for automatically scheduling the required
weekly, monthly, and yearly processes is provided
through the Job Scheduling Facility. A specification of
YES for this parameter allows the Job Scheduling
Facility to schedule weekly, monthly, or yearly
operations on a weekend; a specification of NO will
ensure that THEY ARE NOT SCHEDULED ON THE WEEKEND.
The rationale for this option is that the weekly,
monthly, and yearly processes are more complex than the
daily one, especially with respect to their tape
processing. This results in a greater chance that they
will malfunction and require human intervention, which
might not be available on a weekend.
INPUT HISTORY LOG RETENTION LIMIT (INPUTLOGLIMIT):
The Input History Log file of the Administrative
Information Area (DAYS.ADMIHL01) provides the system
administrator with an audit trail (by original SYSID and
CA MICS product) of the types and volume of data that
have been used to update the CA MICS database. The
audit trail data is maintained for a given number of
days; the number of days is defined through this option.
The number of days can range from a minimum of 7 days to
a maximum of 99 days. Although, the space required for
each cycle of this information is small, we recommend
that you use a large number of days for the audit trail
data. If this statement is omitted or invalid, a
default of 99 days is used.
CA SMF DIRECTOR INPUT HISTORY RETENTION LIMIT (SMFDJHLLIMIT):
The Split Index File of the Administrative Information
Area (DAYS.ADMJHL01) is only populated when input is
provided using the CA SMF Director interface to CA MICS.
This file serves a dual purpose. First, it is input
into each CA MICS incremental update and DAILY input
processing step to eliminate split files previously
processed within the same CA MICS component that would
otherwise be considered eligible for input based on
standard date/time selection criteria. Second, it
provides the system administrator with an audit trail of
the split files processed by each CA MICS component to
update the CA MICS database. The audit trail data is
maintained for a given number of days; the number of
days is defined through this option. The number of days
can range from a minimum of 7 days to a maximum of 99
days. Since CA MICS uses this file to avoid processing
previously processed split files, we recommend that you
use a large number of days for the audit trail data. If
this statement is omitted or invalid, a default of 99
days is used.
Note: The SMFDJHLLIMIT value should coincide with the
CA SMF Director INDEXLIM parameter. If the INDEXLIM
value is set higher than the CA MICS SMFDJHLLIMIT, the
CA SMF Director index will contain entries that CA MICS
has already discarded. This could potentially cause CA
MICS to input split files that were previously processed
but still remain eligible for input based on the
standard date/time selection criteria. While CA MICS
has safeguards built-in to eliminate this duplicate
data, processing previously processed data will add to
the overall processing time and should be avoided.
SPACE UTILIZATION FILE (ADMSPC) RETENTION LIMIT
(SPCUTILLIMIT):
The Space Utilization file of the Administrative
Information Area (DAYS.ADMSPC01) provides the system
administrator with a snapshot (by CA MICS product step,
and type) of the space usage of the INCRccc and DAILY
jobs. This includes work space as well as unit database
space utilization. Data is maintained for the number of
days defined through this option. The number of days
can range from a minimum of 7 days to a maximum of 99
days. If this statement is omitted or invalid, a
default of 99 days is used.
EXCLUDE ORIGINAL SYSIDS (EXCLUDEORGSYSIDS):
This statement can be used to exclude data from selected
original SYSIDs from CA MICS processing. Data for any
ORGSYSID specified will not be added to the CA MICS
database, and will not be checked against the table of
original SYSIDs defined to CA MICS in the SYSID
(unit-level) or CPLXSID (complex-level) parameter
members.
The statement is specified by providing the keyword and
a list of one or more original SYSIDs separated by
blanks. For example:
EXCLUDEORGSYSIDS TST1 TST4 SYST
Use the keyword, UNDEFINEDSYSID, to override an
UNDEFINEDSYSID ABORT parameter you may have specified or
accepted by default in sharedprefix.MICS.PARMS(CPLXSID)
or prefix.MICS.PARMS(SYSID). Specify the following
statement to automatically exclude data for any ORGSYSID
value NOT defined in either prefix.MICS.PARMS(SYSID) or
sharedprefix.MICS.PARMS(CPLXSID).
EXCLUDEORGSYSIDS UNDEFINEDSYSID
Note: The EXCLUDEORGSYSIDS UNDEFINEDSYSID option is
intended to address temporary or isolated situations.
Use the CPLXSID or SYSID control parameters for
"permanent" changes.
TITLE
The TITLE statement will cause a title to be written at
the beginning of the SAS log for any processing step
that uses #BASMSTR. This feature is primarily intended
for identifying jobs using CA MICS special databases,
but can be used for any database. If used, the title
text must be separated from the TITLE keyword by a blank
and must not contain any semicolons. The title does not
need to be enclosed in quotes. A TITLE statement must
be only one line, but multiple TITLE statements can be
specified.
ACCOUNTING
Specify ACTIVE or INACTIVE to define the status of the
Accounting product in this database unit. This
statement will turn the Accounting product on or off for
all files it uses in this unit. This statement does not
need to be specified if Accounting is not installed in
this database unit.
SD_ACTIVE
Specify YES to activate or NO to disable CA MICS Abend
Reporting. When activated, CA MICS will generate call
tickets in Service Desk for most abends in CA MICS
operational jobs. See Section 4.9 for more information.
USERDEF
This parameter allows you to define a symbol and a value
that can be substituted at SAS execution. This
substitution can only occur in CA MICS jobs that invoke
the SETGBLS SAS routine to input the USERDEF statements
in EXECDEF, such as DAILY, WEEKLY, MONTHLY, and YEARLY.
The CALL GBLFCN function is used to retrieve the value
of the symbol in SAS code and assign the value to a
user-supplied SAS element. The USERDEF parameter can be
used in a user modification to provide user-supplied
parameter values, and the user modification code can
perform specific functions based on the USERDEF
parameter setting for a specific database unit.
For example, the SMF Analyzer Account Routine in
sharedprefix.MICS.PARMS(ACCTRTE) could use different
input logic to assign the Account Code (ACCTNOn)
elements depending upon the unit database being updated
by the DAILY job. The CA MICS database unit being
processed in the DAILY update job can be determined by
setting a unique value for a specific USERDEF parameter
symbol in prefix.MICS.PARMS(EXECDEF) for each database
unit that contains the SMF Analyzer.
Several USERDEF symbols can be defined. The only
restriction is that the symbol on each USERDEF statement
must be different from those on all others and different
from all symbols currently used by SETGBLS. Also, the
value must end before column 73 of the record. It cannot
be continued and must contain no imbedded blanks.
Here is an example:
USERDEF CLIENT GROUP1
This defines a symbol, CLIENT. This symbol can be
accessed using the CALL GBLFCN function to substitute
the symbol value for CLIENT as coded in EXECDEF. For
more information, see Chapter 4 of the System
Modification Guide.
There are additional statements that can be specified in the
EXECDEF parameter member. These statements are used for the
CA MICS special database facility. They include the
COMPONENT, FORCE, SELECT, and ORGSYSID statements. These
statements are discussed in Appendix A.3.
+--------------------------------------------------------------------------+ | INSTALLATION PREPARATION WORKSHEET: Dynamic Execution Options | | PARMS Library Member is EXECDEF | | Reference Section: 2.3.5 | +--------------------------------------------------------------------------+ | | | | | | | CREATE EXCEPTIONFILES _________ (NONE, ALL, list) | | REPORT EXCEPTIONS _________ (NONE, category) | | | | REPORT MBODAILY _________ (NONE, ALL, list) | | REPORT MBOWEEKLY _________ (NONE, ALL, list) | | REPORT MBOMONTHLY _________ (NONE, ALL, list) | | REPORT WORKSPACE _________ (YES, NO) | | | | SCHEDULE WEEKEND _________ (YES, NO) | | | | INPUTLOGLIMIT __ (7 - 99) | | SMFDJHLLIMIT __ (7 - 99) | | EXCLUDEORGSYSIDS ____ ____ ____ (UNDEFINEDSYSID, list) | | | | TITLE _______________________________ | | | | ACCOUNTING ________ (ACTIVE, INACTIVE) (if required) | | | | SD_ACTIVE ________ (YES, NO) (if required) | | | | | +--------------------------------------------------------------------------+
Figure 2-43. Dynamic Execution Options Worksheet
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |