An increase in workload in the CA Datacom MUF can sometimes come as a result of adding another CICS region or jobs that need to run concurrent with the existing workload. This might mean that the current number of TASKS used by the MUF is insufficient to support the planned workload.
In order to support the increase, the TASKS value should be increased, and there are other considerations and changes to make to support this change to TASKS.
In order to make this change, the MUF will need to be recycled. Therefore, this change should be made during a planned outage or a time of light activity.
- Just before stopping the MUF, execute DBUTILTY to SPILL the Log (LXX) to a Recovery file (RXX) if using logging (LOGRCV=NO).
- Shut down the MUF using your standard procedure.
- Make the change to the MUF Startup Option TASKS value as desired.
- Review the previous initialization of the Force Area (FXX), or execute the DBUTLTY INIT function, using a value for TASKS that is much higher than you plan to use for the MUF Startup Option TASKS setting. This will preclude running this INIT again if you change the TASKS value in the future.
- Review your MUF startup JCL to ensure that the REGION parameter is sufficient. We recommend that you use 0M (or some other “unlimited” value) so that the MUF can manage its memory usage most efficiently. If you use CA SYSVIEW, you can see the various memory amounts currently in use on the ACTIVITY screen related to CSA/ECSA, SQA/ESQA and Common storage.
For more information about the DBUTLTY functions listed – INIT FXX and SPILL – please refer to the CA Datacom/DB DBUTLTY Reference Guide.
As always, please contact CA Technologies support for CA Datacom if you have further questions.