ProbeVue is a long running command and
the
Vue script is run multiple times. The
Vue script might be referring to devices or resources to print
the statistics and those resources and devices can become temporarily unavailable or permanently
unavailable. Thus,
ProbeVue system statistics statements
have the following behaviors for different conditions:
Table 1. ProbeVue system statistics conditions and
behaviors
| Serial Number |
Conditions |
Behavior |
| 1 |
Resource indicated in the statement does not exist. |
During Vue script validation if
ProbeVue does not find resource specified in the Vue script, compilation fails. |
| 2 |
Device or resource is not open/active. |
- ProbeVue will print all zeros for the statistics.
- Device might get opened to run ioctl() function and then might get closed.
|
| 3 |
Device or resource moved from active state to inactive state. |
ProbeVue will print zeros or
stale data. |
| 4 |
Device gets closed during run time. |
Same results when resources are moved to inactive state. |
| 5 |
Asynchronous fetch API takes time more than fetch interval set by
user. |
ProbeVue will not be able to
guarantee the fetch interval if fetch takes more time than interval. |
| 6 |
Dynamic LPAR operation performed during run time and resource indicated by
Vue script are getting removed. |
ProbeVue will print all zeros or
stale data. |
| 7 |
Device statistic fetch call is blocked due to timeout in device
drivers. |
ProbeVue will not be able to
provide the guarantee of fetch interval and user might see the stale data. |