Is there a recommended guideline as to how often a bounce or recycle should be performed on CA Datacom MUFs outside of system changes? I would extend that same question for our CICS regions which are currently bounced weekly to avoid short on storage issues.
We are looking at reducing the frequency of recycles. Can we leave these regions running longer and still maintain high confidence that the systems are optimal?
Component : CA DATACOM/DB
Component : CA DATACOM/AD
Component : CA DATACOM CICS SERVICES
As with tuning, this question about when to recycle a MUF or CICS region is more of an art than a science, and I expect instinct will be more of a driver than experience. Below are some thoughts from the CA Datacom product team about this.
The next question that comes up here is what to monitor to see if a recycle is needed. This is difficult to say, since things like buffer utilization, Covered/Virtual definition, elapsed open time, etc. all need to be considered. Generally, there is no real need for special review of a given database for processing, and with the number of 24x7 tools available, most functions you need to do to a database can be accomplished without an outage. As an example, if your capacity management team need to take a volume offline, you can use the Online Area Move facility to create, initialize, and relocate the data from an area on this volume to a new volume - all while users are accessing that area.
So there is nothing special that a recycle of the MUF provides for application data, other than the deleterious effect of no longer having data in the buffers right away - they would need to be reloaded into memory again. In terms of system components, there may not be much gain from recycling the MUF, other than resetting internal statistical counters to prevent them from overflowing (although we have made most of the counters so large, it is not likely that this would happen). An IPL only would reload the PC module DBPCCPR, used for cross-memory communication, but this module can be reloaded at any time by running the CAIRIM program to redefine it - an IPL doesn't really provide any benefit here.
Consequently, if you wanted to go with a one-month cycle, that sounds fairly normal and we have no concerns for MUF processing. If you wanted to expand that to a two-month cycle, that also seems to be fine and somewhat typical.
As always, please contact Broadcom support for CA Datacom if you have further questions.