The commcfg file itself can be used to indicate to each client runtime how often the runtime should re-read the commcfg. To improve performance, each runtime creats a cache of the commcfg file. By default, caching is not performed and the file is re-read and re-parsed for each flow that is processed by the client process. Re-reading the commcfg for each flow lets any file changes be applied and used for the processing of the next flow that is serviced by the runtime. This default behavior cannot be ideal in all environments. Therefore, the CACHETIMEOUT statement can be used to control the number of seconds to wait between re-reading of the commcfg file. All flows that occur between the read and the timeout use the values that are located in the cached version of the commcfg file.
Note: Rereading of the commcfg takes place after the first flow that occurs after the specified timeout value has expired.
The following CACHETIMEOUT statements set the cache timeout value to 0 (the default behavior), 3 minutes, and never:
CACHETIMEOUT 0
CACHETIMEOUT 180
CACHETIMEOUT NEVER
The specified cache timeout only applies to the client process from which a cooperative flow is initiated. If the client process terminates, the cache that is associated with that process goes away. The NEVER setting requires the client process be stopped and the communications runtime be unloaded before the commcfg file is re-read.
For a sample listing of the three types of commcfg files, see Comm Config Files. The syntax that is used within each commcfg file type is followed when adding a CACHETIMEOUT statement. The comments that are provided in each commcfg file document the syntax to be used within that file.
|
Copyright © 2014 CA.
All rights reserved.
|
|