For example, a single invocation of this command can produce
BMC AMI Ops Monitor for CMF
reports for system activity during prime, swing, and graveyard shifts.
The SHIFT statement can appear in the general control statement set, the report control statement set, or both sets. In the general control statements, SHIFT defines the data selection start and end times used to produce all the reports requested in the report control statement set. A SHIFT statement for an individual report request overrides a global SHIFT statement for that one report request only.
The SHIFT statement can be used with the DATETIME, CYCLE, and PERIOD statements to produce monthly reports and basic history database trends.
| specifies a time-pair range that is equivalent to the duration of a shift These variables are expressed in the time format hhmmss. Up to 288 different shift ranges can be specified in one SHIFT statement; the ranges must be separated by commas and enclosed within parentheses. Data is included in a report if its recording time is equal to or greater than thestartshift value and less than theendshift value of any of the time-pairs specified. CMF does not check to ensure that the time pairs specified correspond to default or actual shift periods. When time ranges are specified, they should not overlap. If they do and if RPTS=SEPARATE is specified, some data is used in more than one report shift. If time-pair ranges are not specified, the following three default time pairs are used: - (080000,160000)—8:00 A.M. to 4:00 P.M., corresponding to shift 1
- (160000,240000)—4:00 P.M. to 12:00 A.M. (midnight), corresponding to shift 2
- (000000,080000)—12:00 A.M. (midnight) to 8:00 A.M., corresponding to shift 3
Important The default for RPTS=DAILY is no SHIFT ranges. Time-pair ranges are mutually exclusive with RPTS=INTERVAL. |
|---|
| allows you to specify up to 288startshift,endshift pairs of equal length by specifying a start time, number of intervals, and interval duration The DINTV parameter simplifies the specification of equal length time pairs, an alternative to specifying each time pair separately. This parameter specifies that reports be created from data obtained during multiple, evenly-spaced, sequential intervals. These three fields are all required, and commas must separate the three values. - starttime—contains the time you want the first interval to begin; this field must be specified in time format hhmmss
- intervals—specifies the number of time pairs to be generated; this field must be specified as a number from 1 to 288
- duration—specifies how long the interval lasts; this field must be specified in the format hhmmss
Important - Use of the DINTV parameter or manually coded startshift, endshift pairs increases the storage requirements for the Analyzer.
- While multiplestartshift, endshift pairs may be used to specify any combination of report collection intervals, using the DINTV parameter eliminates the need to specify multiple startshift, endshift pairs when data from evenly spaced sequential intervals is required.
- Specifying both the DINTV parameter and one or more startshift, endshift pairs results in an error message.
|
|---|
| defines how the SHIFT statement is used GLOBAL—valid in either the general or the report statement set This value defines the shift characteristics for all report requests that follow it, except single report requests associated with local SHIFT statements. If multiple global SHIFT statements are used, each succeeding global statement establishes new shift characteristics for the following report requests. GLOBAL is the default. LOCAL—valid only in the report statement set The local SHIFT statement defines the shift characteristics for the report request that immediately precedes it. A local SHIFT statement overrides any global SHIFT statement, but only for that one report.
|
|---|
| limits the scope of the input data by specifying from 1 to 7 days of the week The days can be listed individually or collectively by using the parameter values shown in the following table. The default is ALL, except when RPTS=INTERVAL and RPTS=DAILY, because these parameters are mutually exclusive with DAYS=ALL. Parameter values for DAYS | | |
|---|
| | | | | | | | | | | | | | | | | | | | | | | ALL or (SU,MO,TU, WE,TH,FR,SA) | | | | | | | | | WEEKLY or (SU,MO,TU,WE,TH, FR,SA) |
|
|---|
| requests one report for the entire SHIFT definition set or individual reports for each shift time pair - SEPARATE—One report is produced for each time pair of the SHIFT statement; SEPARATE is the default.
- COMBINED—One combined report is produced for all data gathered within the time ranges specified in the SHIFT statement.
INTERVAL—A complete set of reports is produced for each recording interval. Reasonable limitations should be exercised with this parameter, because it might produce a large volume of output, which uses more memory and requires a larger DMSSMAIN data set or greater use of hiperspace. Warning All other SHIFT statements are ignored if this parameter is used anywhere in the control statement set. When using the INTERVAL value, only one Control Card Log is printed to the //CMFLOG DD data set, and no Collection Phase Log reports are printed. Warning Data from multiple images must not be merged, and the records must be sorted by date and time. DAILY—A complete set of reports is produced for each day. Warning All other SHIFT statements are ignored if this parameter is used anywhere in the control statement set. When using the DAILY value, only one Control Card Log is printed to the //CMFLOG DD data set, and no Collection Phase Log reports are printed.
|
|---|
These examples illustrate the use of the SHIFT control statement in the general control statement set.
Example
All defaults are in effect. This statement is equivalent to specifying.
Example
SHIFT (080000,160000),(160000,240000),(000000,080000),
TYPE=GLOBAL,DAYS=ALL,RPTS=SEPARATE
Regardless of the number of days encountered in the data set, three reports are generated for each report request, based on the default time pairs. The reports reflect an average profile of each shift time-pair range.
Example
All defaults are in effect except DAYS. All Extractor data in the data set with a date that is a Monday is included for all report requests; data for all other days is excluded. The reports reflect a profile of an average Monday by each of the default shift time-pair ranges. If there is more than one Monday in the input data, a separate report is produced for each shift of each Monday.
Example
SHIFT DAYS=(MO,WE,FR),RPTS=COMBINED
All defaults are in effect except DAYS and RPTS. Data for Mondays, Wednesdays, and Fridays is collected into one report for each default shift time-pair range. Then all data collected under the default shift time-pair ranges is reported as a combined data group for all report requests. The result is one report for each report request containing data for Mondays, Wednesdays, and Fridays.
Example
SHIFT (100000,120000),(140000,160000)
All defaults are in effect except the shift time-pair ranges. Two reports for each report request are created. This feature can be used to break a shift into smaller reporting periods. Up to 288 ranges can be specified per SHIFT command, either as LOCAL shifts or as multiple GLOBAL shifts.
Example
SHIFT DINTV=(080000,32,001500)
All defaults are in effect except the shift time-pair ranges. For each report request, 32 reports are created. The first report contains data collected during a 15-minute interval beginning at 8:00 A.M. (from 8:00 to 8:15), the second report contains data collected from 8:15 A.M. to 8:30 A.M., and so on.
The following examples illustrate the use of the SHIFT control statement in the report control statement set.
Example
SHIFT (080000,120000),(130000,170000),RPTS=COMBINED
CPU
CHANNEL
DEVACT
SHIFT (000000,060000),(160000,220000),
TYPE=GLOBAL,DAYS=WORKWEEK
PERFSUM
SRM
DASD
The second SHIFT statement that is displayed in this example is designated as TYPE=GLOBAL, redefining the shift characteristics for the report requests that follow.
The CPU, CHANNEL, and DEVACT report requests that precede the SHIFT TYPE=GLOBAL statement conform to the shift characteristics set by the first SHIFT statement in the control statement set.
Example
All defaults are in effect except TYPE. Because LOCAL is specified, this SHIFT statement applies only to the I/O Queuing Activity report request. Three I/O Queuing Activity reports are generated, one for each of the default time-pair ranges.
Example
WLMGL
SHIFT TYPE=LOCAL,DAYS=WEEKENDS
All defaults are in effect except TYPE and DAYS. Because LOCAL is specified, this SHIFT statement applies only to the WLMGL report request. All workload summary-type data with a date of Saturday and Sunday is included in the Workload Summary report; all data from other days is excluded. Three reports are produced, one for each default time-pair range. Each report reflects an average profile for that shift for an average Saturday and Sunday.
Example
The SHIFT statement can be used with the DATETIME, CYCLE, and PERIOD statements to produce monthly performance evaluation reports; for example
DATETIME (1MAR03:000000,31MAR03:235959)
CYCLE DAILY
PERIOD CYCLE=DAILY,
RPTS=SEPARATE
SHIFT (080000,163000)
RECTYPE 240,
MONITOR=CPM
CPU
LCU
AUXSTOR
PERFSUM
.
.
.
This request produces reports for each prime shift (8:00 A.M. to 4:30 P.M.) for each day in March 2010. Thirty-one sets of reports are produced.
Example
The SHIFT statement can be used with DATETIME, CYCLE, and PERIOD to produce historical trend data for performance evaluation reporting; for example
DATETIME (1JAN03:000000,31MAR03:235959)
CYCLE WEEKLY
PERIOD CYCLE=WEEKLY,
RPTS=SEPARATE
SHIFT (080000,163000),
DAYS=(MO,WE,FR)
RECTYPE 240,
MONITOR=CPM
CPU
TSOPERF
SRM
PERFSUM
WLMGL
.
.
.
This request produces 14 sets of reports, for the first 13 weeks of 2010 and one for the last 6 days of March. Each week comprises data collected from Monday, Wednesday, and Friday between 0800 and 1630.
Average profiling of a day, week, and weekend can be accomplished by using Tabular Summary reports. The PROFILE parameter on the GRAPH command statement enables graphic measures to be represented in a profile manner similar to the Tabular reports.