Introduction › Performance of Open/Close Processing

Performance of Open/Close Processing

Performance was improved in handling the requirements to open and close data sets within a MUF. The changes were to enhance the 24x7 (always available) aspect of CA Datacom. It addresses the time for an enabled executing MUF to be recycled to a new MUF execution or to a Shadow MUF.

The three key changes being made to affect the feature are as follows:

• In prior releases, the open process was built to ‘expect’ data sets to have been archived and handle the time during an unarchive in an efficient manner. Since most data sets will not be archived, Version 15.0 is designed to work most efficiently for these data sets and if one is found as archived, drive the unarchive process in a new subtask built for the purpose (DBOC3PR). This saves open/close time for the normal path.
• In prior releases, MUF did every data set open and every close in a single TCB DBOC2PR. With Version 15.0, users are allowed to pick 1-20 sub-tasks to be used for open and close processing (default of 4). In effect, the data sets should mostly balance among the subtasks allocated. This allows up to 20 parallel opens or closes.
• Closing areas within a database are performed in a more parallel process in Version 15.0 to reduce the time to get a group of areas closed.

The option name to be used, at MUF startup only, is X_OPEN_CLOSE_SUBTASKS.