(1) (2) (3) 2004/07/13 14:07 CA MIM Control File I/O Report PAGE 1 (4)System: SYSA (5)Jobname: MIMGR (6)Release: 11.6 (7) Service Level: 0000 (8)From: 2003/10/25 00:00 (9)Each: RECORD (10)To: 2004/03/12 10:52 (11)Shift: 00:00 24:00 (13) (15) (17) (19) (21) (23) (12) CF (14) Average (16) Average (18) Average (20) Average (22) Average Interval Start Cycles BLKS RD BLKS RD BLKS WR BLKS WR XACT RD XACT RD XACT WR XACT WR XACT PR XACT PR ‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑ ‑‑‑‑‑‑‑ ‑‑‑‑‑‑‑ ‑‑‑‑‑‑‑ ‑‑‑‑‑‑‑ ‑‑‑‑‑‑‑ ‑‑‑‑‑‑‑‑‑‑ ‑‑‑‑‑‑‑‑‑ ‑‑‑‑‑‑‑‑‑‑ ‑‑‑‑‑‑‑‑‑ ‑‑‑‑‑‑‑‑‑‑ ‑‑‑‑‑‑‑‑‑ 2004/03/07 16:58 3970 5664 1.427 5265 1.326 819297 206.372 5709 1.438 123842 31.194 2004/08/29 15:58 11 15 1.364 19 1.727 8 0.727 10 0.909 8 0.727 (24) ***Migrate from: Master=SYSA VOL=****** DSN=******** ***Migrate to: Master=SYSB VOL=****** DSN=******** 2004/08/29 15:58 22 26 1.182 26 1.182 10 0.455 2 0.091 10 0.455 (24) ***Migrate from: Master=SYSB VOL=****** DSN=******** ***Migrate to: Master=SYSA VOL=****** DSN=******** 2004/08/29 15:58 11 12 1.091 11 1.000 8 0.727 10 0.909 8 0.727 (24) ***Migrate from: Master=SYSA VOL=****** DSN=******** ***Migrate to: Master=******** VOL=MIMX01 DSN=MIM.CF01 2004/08/29 15:58 10 11 1.100 11 1.100 4 0.400 8 0.800 4 0.400 (24) ***Migrate from: Master=******** VOL=MIMX01 DSN=MIM.CF01 ***Migrate to: Master=SYSB VOL=****** DSN=******** 2004/08/29 15:58 12 16 1.333 16 1.333 8 0.667 2 0.167 8 0.667 (24) ***Migrate from: Master=SYSB VOL=****** DSN=******** ***Migrate to: Master=SYSA VOL=****** DSN=******** 2004/08/29 15:59 60 60 1.000 60 1.000 8 0.133 2 0.033 8 0.133 (25) ***Current CF: Master=SYSA VOL=****** DSN=********
|
Field |
Description |
|---|---|
|
(1) |
Date and time the report was created. |
|
(2) |
Report title. |
|
(3) |
Report page number. |
|
(4) |
System name of the CA MIM image as defined by the DEFSYS statement. |
|
(5) |
Name of the CA MIM started task. |
|
(6) |
The CA MIM service number. |
|
(7) |
The CA MIM PTF level. |
|
(8) |
Date and timestamp of the earliest record in the reporting interval. |
|
(9) |
Summary level for the data line. In this example, each RECORD is displayed in the detail line. If each HOUR was specified, then the detail line would be a summary of the hour's activity. |
|
(10) |
Date and timestamp of the latest record in the recording interval. |
|
(11) |
Range of records included in the report. |
|
INTERVAL START(12) |
Start date and timestamp that the report line interval data covers. |
|
CF CYCLES (13) |
The total number of control file accesses made by CA MIM during the reporting interval. This number is similar to the COUNT: CYC value displayed in the MIM0039 message generated by the DISPLAY MIM IO command. |
|
BLKS RD (14) |
The total number of control file blocks read by CA MIM during the reporting interval. This number is similar to the COUNT: BLOCKS READ value displayed in the MIM0039 message generated by the DISPLAY MIM IO command. |
|
AVERAGE BLKS RD (15) |
The average number of control file blocks read per control file access by CA MIM during the reporting interval. This number is similar to the AVG: BLOCKS READ value displayed in the MIM0039 message generated by the DISPLAY MIM IO command. |
|
BLKS WR (16) |
The total number of control file blocks written by CA MIM during the reporting interval. This number is similar to the COUNT: BLOCKS WRITTEN value displayed in the MIM0039 message generated by the DISPLAY MIM IO command. |
|
AVERAGE BLKS WR (17) |
The average number of control file blocks written per control file access by CA MIM during the reporting interval. This number is similar to the AVG: BLOCKS WRITTEN value displayed in the MIM0039 message generated by the DISPLAY MIM IO command. |
|
XACT RD (18) |
The total number of control file transactions read by CA MIM during the reporting interval. This number is similar to the COUNT: XACT READ value displayed in the MIM0039 message generated by the DISPLAY MIM IO command. |
|
AVERAGE XACT RD (19) |
The average number of control file transactions read per control file access by CA MIM during the reporting interval. This number is similar to the AVG: XACT READ value displayed in the MIM0039 message generated by the DISPLAY MIM IO command. |
|
XACT WR (20) |
The total number of control file transactions written by CA MIM during the reporting interval. This number is similar to the COUNT: XACT WRITTEN value displayed in the MIM0039 message generated by the DISPLAY MIM IO command. |
|
AVERAGE XACT WR (21) |
The average number of control file transactions written per control file access by CA MIM during the reporting interval. This number is similar to the AVG: XACT WRITTEN value displayed in the MIM0039 message generated by the DISPLAY MIM IO command. |
|
XACT PR (22) |
The total number of control file transactions processed by CA MIM during the reporting interval. This number is similar to the COUNT: XACT PROCESSED value displayed in the MIM0039 message generated by the DISPLAY MIM IO command. |
|
AVERAGE XACT PR (23) |
The average number of control file transactions processed per control file access by CA MIM during the reporting interval. This number is similar to the AVG: XACT PROCESSED value displayed in the MIM0039 message generated by the DISPLAY MIM IO command. |
|
(24) |
When a control file migration takes place during the reporting interval, this report line is generated to show that a control file migration has taken place. It shows the prior control file location (first line) as well as the active control file location (second line) at the end of the reporting interval. |
|
(25) |
The location of the control file at the end of the reporting interval. CF and VOLSER are the data set name and volser, respectively, of the active DASD control file, or asterisks (*), if the active control file is a virtual control file. MASTER is the name of the current master system that is maintaining the virtual control file, or asterisks, if the current control file is on DASD. This information is similar to that displayed in the MIM0039 message generated by the DISPLAY MIM IO command. |
|
Copyright © 2014 CA.
All rights reserved.
|
|