(1) (2) (3) 2008/07/13 14:06 CA MII QNAME Enqueue/Reserve Report PAGE 1 (4) System: SYSA (5) Jobname: MIMGR (6) Release: 11.9 (7)Service Level: 0000 (8) From: 2003/10/25 00:00 (9) Each: RECORD (10)To: 2008/03/12 10:52 (11)Shift: 00:00 24:00 (13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23) (12) Total Average Failures Conflict ENQs ENQs RESERVEs RESERVES Proc. Proc. Interval Start Requests Serv Time Prevented QNAME Count Received Processed Received Converted /Sec /Cyc ---------------- ---------- --------- --------- --------- ---------- ---------- ---------- ---------- ---------- ------ ------ 2008/03/07 16:58 3,084 .007582 130 * OTHERS 0 0 0 0 0 $RXQUEUE 0 0 0 0 0 ACTLIB 0 0 0 0 0 ADRPRDCT 0 0 0 0 0 APTSYS 0 0 0 0 0 ARCBTAPE 0 0 0 0 0 ARCDSN 0 0 0 0 0 ARCENQG 8 20 20 0 0 .02 .01 *ARCGPA 0 0 0 5 0 ARCHBKLG 0 0 0 0 0 ARCLOG 0 0 0 0 0 ASM 0 0 0 0 0 ASM2.IXR 0 0 0 0 0 ASM2SYSA 0 0 0 0 0 ASM2SYSB 0 0 0 0 0 ASTEXMM 0 0 0 0 0 BUNDL 0 0 0 0 0 CA-ENF 0 0 0 0 0 CADB2 0 0 0 0 0 CADTCM01 0 0 0 0 0 CAIMSMF 0 0 0 0 0 CAJ$SCE1 0 0 0 0 0
|
Field |
Description |
|---|---|
|
(1) |
Date and time the report was created. |
|
(2) |
Report title. |
|
(3) |
Report page number. |
|
(4) |
System name of the CA MII image as defined by the DEFSYS statement. |
|
(5) |
Name of the CA MII started task. |
|
(6) |
The CA MII release number. |
|
(7) |
The CA MII service 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. |
|
Total Requests (13) |
The total number of managed ENQ/RESERVE requests that CA MII intercepted and processed during the reporting interval. This number is similar to the REQUEST column of the MIM1021 message generated by the DISPLAY GDIF SERVICE command. Note that it is possible and quite probable that the number in this column differs from the sum of the numbers in the ENQ/PROC column and the RESV/CONV column. This is due to the fact that the managed ENQ/RESERVE count is incremented once for every occurrence of an SVC 56 that is intercepted that contains at least one managed QNAME in its parameter list. The ENQ/PROC count and the RESV/CONV count is incremented for every respective managed QNAME encountered in the SVC 56 parameter list. Since the SVC 56 parameter list supports the occurrence of multiple QNAME/RNAME combinations in a single invocation of SVC 56 (the SYSDSN ENQ done by that initiator is a good example of this), it is not expected that these columns will be equal. |
|
Average Serv Time(14) |
The average time, in seconds, that CA MII took during the reporting interval to perform global processing for a given ENQ or RESERVE request. This number is similar to the TIME/REQUEST column of the MIM1021 message generated by the DISPLAY GDIF SERVICE command. |
|
Failures Prevented (15) |
The number of integrity failures prevented, from the viewpoint of the system being reported on, due to outstanding activity on external systems. This count represents the number of times that a requester in the local system issued a request for a QNAME/RNAME combination that was already owned on a remote system, and would have caused a potential integrity exposure were it not for global resource integrity protection. This number is similar to the first value displayed in the MIM1015 message generated by the DISPLAY GDI BENEFITS command. |
|
QNAME (16) |
ENQ or RESERVE QNAME encountered by CA MII during the reporting cycle. If the QNAME is preceded by an asterisk (*), then CA MII does not manage the QNAME. This number is similar to the RESOURCE column in the MIM1016 message generated by the DISPLAY GDIF COUNTS command. |
|
Conflict Count (17) |
The number of global conflicts encountered for the QNAME, from the standpoint of the local system, which occurred during the reporting interval. This number is similar to the GLOBAL CONFLICTS column in the MIM1016 message generated by the DISPLAY GDIF COUNTS command. |
|
ENQs Received (18) |
The number of times the QNAME was encountered in an ENQ request that was intercepted by CA MII. This number is similar to the ENQS ISSUED column in the MIM1016 message generated by the DISPLAY GDIF COUNTS command. The column total on the total line reflects the number of managed and non-managed ENQ requests. |
|
ENQs Processed (19) |
The number of times the QNAME was processed as a managed QNAME in an ENQ request that was intercepted by CA MII. This number is similar to the ENQS PROCESSED column in the MIM1016 message generated by the DISPLAY GDIF COUNTS command. |
|
RESERVEs Received (20) |
The number of times the QNAME was encountered in a RESERVE request that was intercepted by CA MII. This number is similar to the RESERVES ISSUED column in the MIM1016 message generated by the DISPLAY GDIF COUNTS command. The column total on the total line reflects the number of managed and non-managed RESERVE requests. |
|
RESERVEs Converted (21) |
The number of times the QNAME was processed (converted to a global ENQ request) as a managed QNAME in a RESERVE request that was intercepted by CA MII. This number is similar to the RESERVES CONVERTED column in the MIM1016 message generated by the DISPLAY GDIF COUNTS command. |
|
Proc./Sec (22) |
The average number of managed requests (or requests for the named QNAME) that CA MII received in one second. This number is similar to the RATE/SECOND column of the MIM1021 message generated by the DISPLAY GDIF SERVICE command. Note that this value is for managed requests only; non‑managed requests display as zeros. |
|
Proc./Cyc (23) |
The average number of managed requests (or requests for the named QNAME) that CA MII processed in one control file cycle. This number is similar to the RATE/CYCLE column of the MIM1021 message generated by the DISPLAY GDIF SERVICE command. Note that this value is for managed requests only; non‑managed requests display as zeros. |
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |