Control-M/Server PACTV.9.0.22.084


Warning

Important

This Technical Bulletin is only relevant to you if you receive a maintenance notification on Sunday 1 March 2026.  Only a very small number of tenants are affected.

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:

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:

  • Control-M Web: The Date Selection run attribute is defined as Wait for a Selected Run Date and no time zone is defined.
  • Agent Utilities: The -odate_option parameter is defined as run_date and no time zone is defined when you run the job via the ctmorder or ctmudly utility.
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-14458Advanced 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-13373The 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-14552The 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-14591The ordering process fails due to the incorrect detection of an unsupported circular referencing sub-folder.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

Control-M SaaS