See also Routing restiction on vxWorks systems.
+acctst <PV name> [progress logging level] [channel duplication count] + [test repetition count] [enable preemptive callback]+ +
Channel Access Client Library regression test.
+ +Test failure is indicated if the program stops prior to printing "test +complete". If unspecified the progress logging level is zero, and no messages +are printed while the test is progressing. If unspecified, the channel +duplication count is 20000. If unspecified, the test repetition count is once +only. If unspecified, preemptive callback is disabled.
+ +catime <PV name> [channel count] [append number to pv name if true]+ +
Channel Access Client Library performance test.
+ +If unspecified, the channel count is 10000. If the "append number to pv +name if true" argument is specified and it is greater than zero then the +channel names in the test are numbered as follows.
+ +<PV name>000000, <PV name>000001, ... <PV name>nnnnnn
+ +casw [-i <interest level>]+ +
CA server "beacon anomaly" logging.
+ +CA server beacon anomalies occur when a new server joins the network, a +server is rebooted, network connectivity to a server is reestablished, or if +a server's CPU exits a CPU load saturated state.
+ +CA clients with unresolved channels reset their search request schedualing +timers whenever they see a beacon anomaly.
+ +This program can be useful to verify that configuration problems have not +resulted in false beacon anomalies that might cause CA to use unnecessary +additional network bandwidth and server CPU load when searching for +unresolved channels.
+ +caEventRate <PV name> [subscription count]+ +
Connect to the specified PV, subscribe for monitor updates the specified +number of times (default once), and periodically log the current sampled +event rate, average event rate, and the standard deviation of the event rate +in Hertz to standard out.
+ +ca_test <PV name> [value to be written]+ +
If a value is specified it is written to the PV. Next, the current value +of the PV is converted to each of the many external data type that can be +specified at the CA client library interface, and each of these is formated +and then output to the console.
+See Dynamic Changes in the CA Client Library Search Interval.
+Many Berkley UNIX derived Internet Protocol (IP) kernels use a memory +management scheme with a fixed sized low level memory allocation quantum +called an "mbuf". Messages about "ENOBUFS" are an indication that your IP +kernel is running low on mbuf buffers. An IP kernel mbuf starvation situation +may lead to temporary IP communications stalls or reduced throughput. This +issue has to date been primarily associated with vxWorks systems where mbuf +starvation on earlier vxWorks versions is rumored to lead to permanent IP +communications stalls which are resolved only by a system reboot. IP kernels +that use mbufs frequently allow the initial and maximum number of mbufs to be +configured. Consult your OS's documenation for configuration procedures which +vary between OS and even between different versions of the same OS.
+ +ca_current_context()
-acctst <PV name> [progress logging level] [channel duplication count] - [test repetition count] [enable preemptive callback]- -
Channel Access Client Library regression test.
- -Test failure is indicated if the program stops prior to printing "test -complete". If unspecified the progress logging level is zero, and no messages -are printed while the test is progressing. If unspecified, the channel -duplication count is 20000. If unspecified, the test repetition count is once -only. If unspecified, preemptive callback is disabled.
- -catime <PV name> [channel count] [append number to pv name if true]- -
Channel Access Client Library performance test.
- -If unspecified, the channel count is 10000. If the "append number to pv -name if true" argument is specified and it is greater than zero then the -channel names in the test are numbered as follows.
- -<PV name>000000, <PV name>000001, ... <PV name>nnnnnn
- -casw [-i <interest level>]- -
CA server "beacon anomaly" logging.
- -CA server beacon anomalies occur when a new server joins the network, a -server is rebooted, network connectivity to a server is reestablished, or if -a server's CPU exits a CPU load saturated state.
- -CA clients with unresolved channels reset their search request schedualing -timers whenever they see a beacon anomaly.
- -This program can be useful to verify that configuration problems have not -resulted in false beacon anomalies that might cause CA to use unnecessary -additional network bandwidth and server CPU load when searching for -unresolved channels.
- -caEventRate <PV name> [subscription count]- -
Connect to the specified PV, subscribe for monitor updates the specified -number of times (default once), and periodically log the current sampled -event rate, average event rate, and the standard deviation of the event rate -in Hertz to standard out.
- -ca_test <PV name> [value to be written]- -
If a value is specified it is written to the PV. Next, the current value -of the PV is converted to each of the many external data type that can be -specified at the CA client library interface, and each of these is formated -and then output to the console.
-