|
|
|
This section explains how to specify the complex-level
database tailoring options and environmental parameters.
These parameters apply to all components installed in the
CA MICS database complex and are specified by parameters in
sharedprefix.MICS.PARMS(CPLXDEF).
Use the CPLXDEF member to define the following:
o Global database tailoring options: the essential data
element option, the derived data element option, and the
four-digit year data element option.
o Printed report and SAS log title text.
o Default values for unit database years timespan option,
weeks timespan option, the first day of the week, the
first week of the year, and fiscal calendar.
sharedprefix.MICS.PARMS(CPLXDEF) contains two required
statements:
o ESSENTIAL
o DERIVED
It contains seven optional statements:
o REPORT
o LOG
o YEAR4
o YEARS TIMESPAN
o WEEKS TIMESPAN
o WEEKSTART
o 13MONTHYEAR
Each of these statements is described in detail below.
THE ESSENTIAL STATEMENT
The ESSENTIAL statement is used to select the default
essential data element option. The format of the ESSENTIAL
statement is:
ESSENTIAL ALL/ONLY/INITIAL
where only one value (ALL, ONLY, or INITIAL) is specified.
The effect of coding each of these values is described next.
ALL All data elements defined in the component's
cccGENIN member on sharedprefix.MICS.GENLIB are
stored on the disk or are available through the
derived element macros.
ONLY Only the data elements essential for file key
structures, component standard reports, and CA MICS
analytic component feeds are stored on disk. All
other data elements are dropped from CA MICS
processing and are not available without
reprocessing raw DETAIL data. When ONLY is
specified, the DERIVED option determines whether
essential computed elements are stored on disk or
are available through the derived element macros.
INITIAL Like the ONLY option, only essential data elements
are stored on disk. When INITIAL is specified, the
DERIVED statement is ignored and the DERIVED option
is automatically forced to COMP. This means the
essential computed elements are available only
through the derived element macros. Additionally,
the WEEKS, MONTHS, and YEARS timespans of all user
and application unit identified files are disabled.
ESSENTIAL element options take effect after the CPLXDEF
member is changed, a complex-level JCLGEN job (for example,
JCLGEN0, JCLGENUC) or CPLXGEN job has been run, and a
component generation job (for example, RMFCGEN) has been run.
Running such generations to change the content of the
database usually requires JCL generations and other
installation modifications for each database unit in which
regenerated components have been installed.
The distributed value for the ESSENTIAL option in CPLXDEF is
ONLY. This uses the least DASD and CPU resources to support
a meaningful subset of the data available from each
component.
When changing from INITIAL to ONLY or ALL, several components
will have previously inactive files activated in timespans
(WEEKS, MONTHS or YEARS). To change from INITIAL to any other
ESSENTIAL option, it is necessary to reinstall the component
in all database units in which the component has been
installed. Use the checklist in Section 3.8.2, Adding a
Component to an Existing Database Unit, to reinstall the
necessary components.
THE DERIVED STATEMENT
The DERIVED statement is used to select the default derived
data element option. The format of the DERIVED statement is:
DERIVED DISK/COMP
where only one value (DISK or COMP) is specified. The effect
of coding each of these values is described separately below.
DISK Computed data elements, defined as type 'C' or 'CN'
data elements in component generation control
members named sharedprefix.MICS.GENLIB(cccGENIN),
are stored on disk (auxiliary storage) in the SAS
files for the CA MICS database. When a program
reads the SAS file on which such data elements
reside, the data elements are immediately available
for use.
COMP Computed data elements, defined as type 'C' or 'CN'
data elements in component generation control
members named sharedprefix.MICS.GENLIB(cccGENIN),
are not stored on disk, but are computed for each
use (such as in a user-written inquiry program).
CA MICS macros are available for performing the
calculations necessary to compute the derived data
elements.
DERIVED element options take effect after the CPLXDEF member
is changed and a complex-level JCLGEN (for example, JCLGEN0
or JCLGENUC) or CPLXGEN job has been run.
Note that setting the ESSENTIAL INITIAL option means that the
DERIVED statement is automatically forced to COMP. Only
essential computed elements are available through the derived
element macros. A DERIVED statement must always be coded,
even in the case where it is ignored.
Note that both the ESSENTIAL and DERIVED settings can be
overridden at the component and file level using the COMPOPT
and FOPT statements available in each components CCCGENIN
member. See the System Modification Guide section 4.2.4 for
more information.
The REPORT statement defines the CA MICS complex name to use
in the title for complex-level reports. It is an optional
statement. If used, the name text must be separated from the
keyword by one or more blanks. The maximum length of the
name string is 40 characters. Do not specify quotes around
the name string. For example, the following statement
results in all complex-level reports having the title, CA
MICS Production Complex:
REPORT CA MICS Production Complex
THE LOG STATEMENT
The LOG statement defines the title to write at the beginning
of the SAS log for complex-level jobs. It is an optional
statement. If used, the title text must be separated from
the keyword by one or more blanks. The maximum length of the
text string is 40 characters. Do not specify quotes around
the text string. For example, the following statement
results in all complex-level SAS logs having the title, CA
MICS Production Complex:
LOG CA MICS Production Complex
YEAR4 STATEMENT
The YEAR4 statement is used to generate macros that enable
the display/processing of data beyond the calendar year 2000
by adding a four-digit variable, YEAR4, to all CA MICS files.
The YEAR4 data element coexists with the two-digit YEAR data
element if YEAR4 is activated. You can use the YEAR4 data
element instead of YEAR in your user-written reports for code
clarity. For example, you can select data between 1998 and
2008 as follows:
IF 1998 < YEAR4 < 2008;
The YEAR4 data element is shipped inactive and is not defined
as a normal CA MICS data element in sharedprefix.MICS.GENLIB.
As a result, you cannot use the standard method of file
tailoring to turn YEAR4 on or off. You must activate or
deactivate this data element using the YEAR4 statement listed
next.
To activate the YEAR4 data element, specify the following:
YEAR4
To deactivate the YEAR4 data element, omit the YEAR4
statement.
Since the YEAR4 statement affects the operation of the entire
CA MICS complex, the YEAR4 data element will reside either in
every CA MICS file or no file at all.
After you modify CPLXDEF, you must run the corresponding
CPLXGEN job to generate the necessary keep, length, format,
and label specifications that are used by CA MICS operational
jobs.
Note: The CPLXDEF YEAR4/NOYEAR4 option activates or
deactivates the YEAR4 data element in all CA MICS
files; however, until you run the cccCGEN job for each
data integration product (including BASCGEN) installed
in the CA MICS complex, YEAR4:
o Does not appear in DIA guide file element lists or
in their data dictionaries.
o Is not available to MICF inquiries or to the
Document Access Dictionary Browse option.
Using this method allows you to implement your YEAR4
specification in the database as quickly as possible, while
delaying cccCGEN processing until a convenient time.
Note: The following parameters provide global default values
for all unit databases in the CA MICS complex. When
you specify unit database parameters, you have the
option to use the global default or you can override
the complex-level parameter values and specify unique
definitions for a single unit database.
In either case, parameter specifications are
implemented by running the individual unit database
BASPGEN jobs. Changes to CPLXDEF are not effective in
an individual unit database until you execute the
BASPGEN job for that unit database.
YEARS TIMESPAN ACTIVE/INACTIVE:
The files in the YEARS timespan are updated as part of the
MONTHLY processing job if the YEARS timespan is active at
your site.
The default unit database parameters are distributed as:
YEARS TIMESPAN INACTIVE
This saves both DASD space and processing time by not
updating the YEARS files.
If the CA MICS administrator decides that the YEARS timespan
should be used to update the YEARS file, either delete the
YEARS TIMESPAN parameter line or specify ACTIVE for this
option. The ACTIVE value will be effective for any any
database that does not override the complex-level default by
explicitly specifying the YEARS TIMESPAN option.
Note that CA MICS still maintains a prefix.MICS.YEARS data
set when the YEARS timespan is inactive. The files in this
data set contain zero SAS observations and are not updated
during MONTHLY processing. In this mode, the YEARS timespan
requires only a minimal amount of DASD space.
If the YEARS timespan is changed from ACTIVE to INACTIVE
after data is processed by CA MICS, any SAS observations in
the year-to-date files are dropped during the MONTHLY process
following the parameter change. Data in files other than the
year-to-date files are not affected by changing the parameter
to INACTIVE from ACTIVE.
WEEKS TIMESPAN ACTIVE/INACTIVE:
The files in the WEEKS timespan are updated as part of the
DAILY processing job if the WEEKS timespan is active at
your site.
By default, the unit database parameters are distributed
without the WEEKS TIMESPAN statement.
If the CA MICS administrator decides that the WEEKS timespan
is not used for reporting purposes and is therefore unneeded,
it can be deactivated for the entire complex by inserting the
WEEKS TIMESPAN parameter option as shown below:
WEEKS TIMESPAN INACTIVE
The INACTIVE parameter will be effective for any unit
database that does not override the complex-level default by
explicitly specifying the WEEKS TIMESPAN option.
Note that CA MICS still maintains a prefix.MICS.WEEKS data
set when the WEEKS timespan is inactive. The files in this
data set contain zero SAS observations and are not updated
during DAILY processing. In this mode, the WEEKS timespan
requires only a minimal amount of DASD space.
If the WEEKS timespan is changed from ACTIVE to INACTIVE
after data is processed by CA MICS, any SAS observations in
the week-to-date files are dropped during the DAILY process
following the parameter change. Data in files other than the
week-to-date files are not affected by changing the parameter
to INACTIVE from ACTIVE.
WEEKSTART Option (SUN MON TUE THU FRI SAT):
This option specifies the first day of the week, whose value
can be changed from SUN to one of the following: MON, TUE,
WED, THU, FRI, or SAT. Only use the WEEKSTART option if you
intend to change the default value (SUN). WEEKSTART is used
to compute the value of WEEK from a given date.
If you choose to specify the WEEKSTART parameter, you are
encouraged to make your specification here, at the
complex-level, and then allow the parameter to default in
each unit database. By doing so, your data will be
maintained in a consistent manner across all units.
Thirteen Month Fiscal Year Option (13MONTHYEAR):
The standard definitions used by CA MICS for DAY, WEEK,
MONTH, and YEAR are based on a calendar year beginning
January 1 and having 12 months, with the number of days per
month varying from 28 to 31 depending on the month. Data is
summarized in the CA MICS database according to these
standard definitions. If your organization operates on the
standard 12-month year and follows the common North American
understanding of the first week of a new year, DO NOT code
this option.
The default for this option is NO. Only use this option if
you intend to override the default. Before using it, we
strongly recommend that you review Section 4.7.2 in the
System Modification Guide for information about adjusting
algorithms and year-end boundary considerations.
13MONTHYEAR has been provided to offer non-standard
calendar-related options. In particular, it enables CA MICS
to summarize and store data for an organization that operates
on a 13-month fiscal year. It also allows a year to have up
to 380 days.
Note: The CA MICS Accounting and Chargeback component
includes facilities for defining a unique
accounting calendar separate from the global
CA MICS calendar definitions. This capability is
designed to help you meet your requirements for
chargeback and accounting, relative to your
company's fiscal calendar, while continuing to use
the standard 12-month calendar for the majority of
your CA MICS information. For more information on
altering the global CA MICS calendar, see the
CA MICS Accounting and Chargeback guides.
If you choose to define a fiscal calendar for your CA MICS
environment, you are encouraged to make your specification
here, at the complex-level, and then allow the parameter to
default in each unit database. In this way, your data will
be maintained in a consistent manner across all units.
This statement can be formatted in any of the following ways:
13MONTHYEAR NO
13MONTHYEAR NO #DWMY=memname
13MONTHYEAR YES ddmonyy ddmonyy ... ddmonyy
13MONTHYEAR YES #DWMY=memname ddmonyy ddmonyy ...
Note: Only one 13MONTHYEAR control statement is allowed.
Subsequent 13MONTHYEAR statements replace prior
13MONTHYEAR statements.
where:
13MONTHYEAR is the option keyword.
NO is specified if you use a standard 12-month year beginning
on January 1 and ending on December 31. The default value
shipped with CA MICS is NO. It causes the SOURCE member
#DWMY12 to be used.
YES is specified only if your organization operates on a
13-month year.
memname is a member that contains date macros. It MUST begin
with the characters #DWMY. For example: #DWMYUSR.
The ddmonyy keyword defines the year's starting date. Valid
values are:
dd 01 to 31, a day of the month
mon JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC, a
three-letter month abbreviation
yy two digits, representing the year
Dates must be in ascending order and a year cannot contain
more than 380 days. You cannot code two dates using the same
year value (that is, 01JAN08 and 28DEC08). You can specify a
maximum of eight dates (that is, the 13MONTHYEAR statement
can define no more than eight years).
Here is an example:
13MONTHYEAR YES 01OCT07 30SEP08
This is interpreted as fiscal year 2007 begins on October 1,
2007 and ends on September 29, 2008. Fiscal 2008 begins on
September 30, 2008 and ends on September 29, 2009.
The CPLXDEF member is distributed with the following options
specified:
ESSENTIAL ONLY
DERIVED COMP
LOG
REPORT
WEEKS TIMESPAN ACTIVE
YEARS TIMESPAN ACTIVE
WEEKSTART SUN
13MONTHYEAR NO
This means the following:
o Only essential data elements are kept in the database.
o Essential computed data elements are calculated using
derived element macros.
o YEAR4 is NOT kept in the database.
o The unit database definition defaults are
- The YEARS timespan is active.
- The WEEKS timespan is active.
- Weeks start on Sunday.
- CA MICS operates under the standard 12-month Gregorian
calendar.
Figure 2-8 provides a worksheet for collecting the
specifications used in the CPLXDEF member.
+--------------------------------------------------------------------------+ | INSTALLATION PREPARATION WORKSHEET: Complex Option Definitions | | | | PARMS Library Member is CPLXDEF | | Reference Section: 2.3.1.8 | +--------------------------------------------------------------------------+ | | | | | ESSENTIAL OPTION: | | ESSENTIAL _____________ (ALL, ONLY, or INITIAL) | | | | | | DERIVED OPTION: | | DERIVED _____________ (DISK or COMP) | | | | | | Title for complex-level report (optional): | | REPORT _____________ | | | | | | Title for complex-level log (optional): | | LOG _____________ | | | | Add 4-digit year variable to all CA MICS files (optional): | | YEAR4 _____________ | | | | YEARS TIMESPAN OPTION: | | YEARS TIMESPAN ________ (ACTIVE or INACTIVE) | | | | WEEKS TIMESPAN OPTION: | | WEEKS TIMESPAN ________ (ACTIVE or INACTIVE) | | | | | | WEEKSTART OPTION: (default is SUN) | | WEEKSTART ________ (MON TUE WED THU FRI SAT) | | | | | | 13MONTHYEAR OPTION: (default is NO) | | 13MONTHYEAR NO #DWMY=________ | | YES ________ ________ ________ | | | +--------------------------------------------------------------------------+ | ....5...10...15...20...25...30...35...40...45...50...55...60...65...70.. | +--------------------------------------------------------------------------+
Figure 2-8. Complex Option Definitions Worksheet
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |