|
|
|
The definition of time zones may be one of the most important
made in terms of tailoring the database to your
installation's requirements because the facility to summarize
data by zone provides the ability to evaluate, both short-
term and long-term, service, availability, and load according
to the service periods established. For instance, in
evaluating online service, management's attention is focused
on the activity of the peak load zones, and little, if any,
attention is directed at the non-peak zones.
You have the option to use the complex-level zone definition
specified in sharedprefix.MICS.PARMS(CPLXZONE), or to define
a unique zone definition for this unit database in
prefix.MICS.PARMS(ZONE). As a general rule, you should use
the complex-level parameter to establish a consistent time
zone definition for all units. In this way, you can maintain
your holiday and special shift definitions in a single
parameter member, and implement changes with a single CA MICS
parameter generation. In using this approach, the individual
unit database prefix.MICS.PARMS(ZONE) members will contain
the single parameter line,
COMPLEXZONEPARM USE
Use the unit-level time ZONE parameters to override the
complex-level time zone definitions to address special
requirements for different time zone definitions for
different units of work. For example one database unit may
support a remote data center, or you may have unique shift
differential requirements for online transaction workloads
separate from standard TSO and batch workloads. In these
situations, you isolate the special workloads to a unique
unit database and fully specify a unique time zone definition
in prefix.MICS.PARMS(ZONE) for that unit database. Please
note, the unit-level ZONE definition completely replaces and
overrides the complex-level ZONE definition for this unit
database. You control this choice with the COMPLEXZONEPARM
USE/IGNORE parameter described in more detail below.
To use the complex-level time zone definition, specify,
COMPLEXZONEPARM USE
as the only parameter in prefix.MICS.PARMS(ZONE). See
section 2.3.1.10 for more information on complex-level time
zone definition.
To override the complex-level time zone definition for this
unit database, follow the instructions in the remainder of
this section to specify a complete unit-level time zone
definition in prefix.MICS.PARMS(ZONE). After completing the
time zone definition, execute prefix.MICS.CNTL(BASPGEN) to
implement your specifications.
In prefix.MICS.PARMS(ZONE), you are asked to define up to
nine service periods (time zones) for your installation.
Time zones are defined once and apply to all Information
Areas within a database. It is not possible to have a time
zone for TSO and another time zone for RMF in the same
database. These service periods, which are also sometimes
referred to as "shifts," are applied over all batch and
online work examined by CA MICS.
The time zone, which is identified by the data element ZONE
in the database, is used for summarizing data in the WEEKS,
MONTHS, and YEARS timespans (it becomes part of the key of
the files, replacing DAY, HOUR, and End Time-Stamp). The
ZONE data element also improves the user's ability to select
or extract data easily from files in the DETAIL and DAYS
timespans where it exists but is not part of the key.
The number of zones defined impacts the projected space
requirements of the database since the data element ZONE is
used for summarization (is part of the key of the files) in
the WEEKS, MONTHS, and YEARS timespans. The more zones, the
larger the online DASD space requirements for the database.
We recommend that the number of standard zones defined be
four or fewer, with one zone for holidays.
CA MICS supports two kinds of ZONEs:
Standard zones are periods that recur in each week. For
example, a standard zone can be defined as "9 a.m. to 5
p.m. on Mondays through Fridays, except for holidays".
Holiday zones are periods that are precisely identified
by date and time. For example, "9 a.m. to 5 p.m. on
New Years Day, January 1, 1993". In addition, some
installations have used holiday zones to identify "super
peak" periods such as end-of-month closings.
In determining the ZONE into which a specific date/time
combination found in a measurement record falls, CA MICS
first checks the holiday zones for an exact match. If one is
found, the corresponding zone number is used. If there is no
match against a holiday zone, the standard zones are checked.
A standard zone can always be assigned to any date/time
because CA MICS requires you to assign every one of the 168
hours in a week to a standard zone (no overlapping is allowed
for standard zones).
A sample definition of time zones follows:
+-----------------------------------------------------------+
| Time Zone | Time Included in Zone Definition |
| Number | Days of the Week Start-End Hours |
|--------------+--------------------------------------------|
| 1 | Monday through Friday 8 a.m. - Noon |
| 1 | Monday through Friday 1 p.m. - 5 p.m. |
| 2 | Monday through Friday 6 a.m. - 8 a.m. |
| 2 | Monday through Friday Noon - 1 p.m. |
| 2 | Monday through Friday 5 p.m. - 8 p.m. |
| 3 | Monday through Friday Midnight - 6 a.m. |
| 3 | Monday through Friday 8 p.m. - 12 p.m. |
| 3 | Saturday and Sunday All day |
| 4 | Holiday 12/25/93 All day |
| 4 | Holiday 01/01/94 All day |
+--------------+--------------------------------------------+
Figure 2-10. Time Zone Definition Example
Figure 2-10 illustrates that time zones are simply periods or
"windows" within a given week (standard zones) or specific
calendar dates (holiday zones).
Figure 2-11 is a worksheet for collecting the data with which
to complete prefix.MICS.PARMS(ZONE). It asks you to do the
following:
1. Identify the number of standard zones to be defined.
Up to nine are allowed. They need not be defined in
sequential order, nor need the numbers be contiguous.
2. Define the hours and days of week that each standard
zone will include.
3. Define the holiday dates, for as many years as is
necessary (holiday zone definition for three years is
suggested).
4. Define the hours and days of week that each holiday
date will include. In most cases, this is 00 to 23.
5. Define a descriptive name to be used with each zone.
The first entries on the worksheet are completed with sample
information. The entry at the top of the form specifies that
standard zone 1 includes the hours from 08 (8 a.m.) to 15 (up
to, but not including 4:00 p.m.) on weekdays (Monday through
Friday). For many sites, this is the definition of "prime"
shift, and, indeed, the reporting name assigned to this zone
is PRIME TIME. The entry on the second part of the form
defines New Years Day as being part of the holiday zone,
number 4.
+--------------------------------------------------------------------------+ | INSTALLATION PREPARATION WORKSHEET: Time Zone Specification | |--------------------------------------------------------------------------| | | | COMPLEXZONEPARM_____________________USE/IGNORE | | | |--------------------------------------------------------------------------| | PARMS Library Member is ZONE | | Reference Sections: 2.3.1.10, 2.3.2.3, 2.3.2.3.1, and 2.3.2.3.2 | +--------------------------------------------------------------------------+ | | | STANDARD ZONES | | ZONE START END START END SERVICE | | NO DAY DAY HOUR HOUR FACTOR ZONE NAME | +--------------------------------------------------------------------------| | 1 MON FRI 08 15 1 'PRIME-TIME' | | (sample) | | _ ___ ___ __ __ ___ '______________________________' | | _ ___ ___ __ __ ___ '______________________________' | | _ ___ ___ __ __ ___ '______________________________' | | _ ___ ___ __ __ ___ '______________________________' | | _ ___ ___ __ __ ___ '______________________________' | | _ ___ ___ __ __ ___ '______________________________' | | _ ___ ___ __ __ ___ '______________________________' | | _ ___ ___ __ __ ___ '______________________________' | | _ ___ ___ __ __ ___ '______________________________' | | _ ___ ___ __ __ ___ '______________________________' | | _ ___ ___ __ __ ___ '______________________________' | +--------------------------------------------------------------------------| | HOLIDAY ZONES | | ZONE START END SERVICE | | NO YEAR MONTH DAY HOUR HOUR FACTOR ZONE NAME | +--------------------------------------------------------------------------| | 4 94 01 01 00 23 1 'HOLIDAY SAMPLE' | | (sample) | | _ __ __ __ __ __ ___ '______________________________' | | _ __ __ __ __ __ ___ '______________________________' | | _ __ __ __ __ __ ___ '______________________________' | | _ __ __ __ __ __ ___ '______________________________' | | _ __ __ __ __ __ ___ '______________________________' | | _ __ __ __ __ __ ___ '______________________________' | | _ __ __ __ __ __ ___ '______________________________' | | _ __ __ __ __ __ ___ '______________________________' | | _ __ __ __ __ __ ___ '______________________________' | | _ __ __ __ __ __ ___ '______________________________' | | _ __ __ __ __ __ ___ '______________________________' | | _ __ __ __ __ __ ___ '______________________________' | +--------------------------------------------------------------------------+ | ....5...10...15...20...25...30...35...40...45...50...55...60...65...70.. | +--------------------------------------------------------------------------+
Figure 2-11. Time Zone Specification Worksheet
The following shows you how to code the parameters required
in prefix.MICS.PARMS(ZONE). The planning issues are
discussed in more detail in the sections that follow.
For the COMPLEXZONEPARM USE/IGNORE option:
o If you defined your zones in
sharedprefix.MICS.PARMS(CPLXZONE), then specify
COMPLEXZONEPARM USE to apply this definition to this
unit database. Remember to comment out all of the
zone and holiday parameters if you specify
COMPLEXZONEPARM USE.
o If you did not define your zones in
sharedprefix.MICS.PARMS(CPLXZONE), or if you want to
override the common zone definition with a unique zone
definition for this unit database, omit the
COMPLEXZONEPARM statement or specify
COMPLEXZONEPARM IGNORE.
If you are defining ZONE at the unit level:
o The member contains one line per standard zone (ZONE)
entry and one line per holiday zone entry (HOLIDAY).
Comments may be coded by beginning the statement with
an asterisk (*).
o The format of the statements is free-form but
positional. All parameters are required. The
parameter placement for a standard zone is:
KEYWORD (ZONE)
ZONE NUMBER (1 through 9)
STARTING DAY (SUN MON TUE WED THU FRI SAT)
ENDING DAY (SUN MON TUE WED THU FRI SAT)
STARTING HOUR (00 to 23)
ENDING HOUR (00 to 23)
SERVICE FACTOR (.1 to 99.9)
ZONE NAME (1- to 40-character name in quotes)
The parameter placement for a holiday zone is:
KEYWORD (HOLIDAY)
ZONE NUMBER (1 through 9)
YEAR (00 through 99 or %%)
MONTH (01 through 12)
DAY (01 through 31)
STARTING HOUR (00 to 23)
ENDING HOUR (00 to 23)
SERVICE FACTOR (.1 to 99.9)
ZONE NAME (1- to 35-character name in quotes)
o For holidays that occur on the same calendar date
regardless of the year, the characters "%%" are
specified in place of a year value, thereby treating
all occurrences of the date as the holiday regardless
of the year. For example, New Years Day is January 1
regardless of the year, so %% is coded in place of a
year value.
One or more statements may be required to fully describe a
zone. Remember the following points when specifying time
zones.
o The parameters for standard zones must account for all
168 hours of the week with no overlapping permitted.
o The ending day must follow the starting day within the
order specified. (To CA MICS, a week begins on Sunday
and ends on Saturday so you may not "wrap" over the
weekend. The WEEKSTART parameter of
prefix.MICS.PARMS(SITE) and
sharedprefix.MICS.PARMS(CPLXDEF) does not affect ZONE
specification. The only exception to this rule is that
a weekend zone may be specified as starting on Saturday
and ending on Sunday.)
o The ending hour must be greater than or equal to the
starting hour (note that "15" means 3 p.m. when
specified as a starting hour, but means 3:59:59.99 p.m.
when specified as an ending hour).
o Day and/or time splits (e.g., a shift which spans
midnight or a zone which includes Saturday and Sunday
and other days) must be defined with multiple
statements.
o The ending day and starting day are the same when the
statement defines a single day.
You should modify the prefix.MICS.PARMS(ZONE) member that is
generated by the COPYLIBS job to reflect your installation
needs.
The following sections describe in detail the parameters
mentioned above and the planning considerations involved in
correctly specifying them:
1 - Standard Time Zones
2 - Holiday Time Zones
NOTE: If you determine that the standard CA MICS ZONE
definition facilities can not meet your installations
requirements, an exit is available where you can
override and redefine the ZONE value assigned through
the standard definition facility. See the System
Modification Guide, Section 4.3.2.1, for more
information on the ZONE definition exit. Please
consider use of this exit very carefully as changes in
the CA MICS ZONE construct can have serious
implications, including, but not limited to, total
database corruption.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |