Control-M/Server PACTV.9.0.22.084
1 March 2026
BMC Software is releasing a patch, PACTV.9.0.22.084, which corrects several problems in Control-M/Server.
The problems corrected by this patch affect a limited number of environments. If your environment is affected, you will receive a notification on the Control-M Trust Page.
Since Control-M/Server downtime is expected during patch deployment, you will receive a maintenance notification 14 days ahead of time, in accordance with the Control-M SaaS Notification Policy.
The maintenance notification will include details regarding the time and date of patch deployment. If you have any issues with the planned date and time, contact BMC Support to schedule an alternative date for patch deployment.
Notes:
- The Control-M SaaS web application will remain available throughout the update.
- Control-M/Server downtime is expected to last no longer than 20 minutes. Any job that is scheduled to begin execution during this period might not execute.
- To prepare for the upgrade and understand the impact during downtime, see What happens to scheduled jobs when the Control-M SaaS tenant is down for maintenance?
- Tenants will be upgraded during the standard upgrade and maintenance windows, as described in Control-M SaaS Upgrade and Maintenance Policy.
Corrected Problems
The following table describes the problems that are corrected in Control-M/Server PACTV.9.0.22.084.
Tracking Number | Description |
|---|---|
| CTM-13062 | Control-M/Server fails to submit jobs after the New Day procedure completes when jobs are defined in one of the following ways: |
| CTM-13504 | Control-M pods become unresponsive and reach 100% CPU usage when you ping the Agent or update Agent parameters for multiple Agents in the Configuration domain. |
| CTM-14458 | Advanced Scheduling definitions allow you to set Keep active to Forever even for non-cyclic jobs. This results in abnormally large amounts of data in the Active Jobs database. |
| CTM-13373 | The Parent Folder and Sub Application attribute fields show incorrect values every time a job workflow is ordered with the same referenced sub-folder multiple times in parallel after the first time the workflow is ordered. |
| CTM-14552 | The ordering process fails due to an incorrect count of nested referencing sub-folders. An error notifies you that the nesting limit is exceeded, even though the number of nested levels is below the allowed maximum of 9 levels of referencing sub-folders. |
| CTM-14591 | The ordering process fails due to the incorrect detection of an unsupported circular referencing sub-folder. |