|
|
|
The DISPLAY SERVICE command provides information about enqueue requests being handled by CA MII. The data is unique to each CA MIM address space in your complex. Therefore, you should issue the DISPLAY SERVICE command on every system in the MIMplex, and examine the displays on each system. The most important information is the number of enqueue requests and the time per enqueue request. The following illustration shows the DISPLAY SERVICE data:
MIM1021 GDIF SERVICE DISPLAY REQUESTS TIME/REQUEST RATE/SECOND RATE/CYCLE SINCE 16,896,706 0.075351 59.900 1.180 08:00:37 2003.119
The key fields used in the control file tuning analysis phase have been bolded in the preceding illustration. The following describes each of these key fields:
The REQUESTS field represents the number of managed enqueue requests that have been handled by CA MII on the system. Examining this field on each system helps you determine which systems are your workload-intense systems in terms of enqueue processing. You will find that the number of enqueue requests on a system has a direct correlation to the AVG: CYC value (DISPLAY IO command) in that the more enqueue requests on a system, the more control file cycles per second that system will perform. Production systems will have more enqueue requests and control file cycles per second than test or development systems.
The TIME/REQUEST field represents the average number of seconds it takes CA MII to service an individual managed enqueue request. A wide variety of internal and external factors have an impact on the CA MIM enqueue service times. Acceptable values for this field are between .050 (50ms) and .070 (70ms). Tuned MIMplexes will have values lower than the acceptable standards, and many sites enjoy values in the single-digit range (6ms). Our example of 75.351ms is definitely not in the range of acceptable enqueue service times.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |