Control-M SaaS Releases
This topic presents information about BMC Control-M SaaS releases.
What's New
The following table lists what's new in Control-M SaaS releases.
Corrected Problems
The following table lists corrected problems in Control-M SaaS releases.
Known Issues
Product | Description |
|---|---|
SaaS Agent | (CTM-11671) Installation of SaaS Control-M/Agent 9.0.21.300 fails when a directory mount contains /tmp in its path and has the noexec option. For more information, see Knowledge Article 000429203. |
| Control-M SaaS | The list of Control-M/Servers enables you to set the desired state of a self-hosted Control-M/Server to Down, but does not enable you to set the desired state to Up. To start up a self-hosted Control-M/Server that is currently down, you must log in to the Control-M/Server account and run the start_ca and start_ctm Control-M/Server utilities commands. |
| Control-M SaaS | Generation of an SSH key with 3072 bits takes a considerable amount of time, and the following error message is issued: The SSH key might still generate successfully. Therefore, wait several minutes and check the list of SSH keys to determine whether the new SSH key appears in the list. |
| SaaS Agent | The Agent Installation pane does not contain information or guidance for the installation of an Agent on a Debian operating system. Workaround: Follow the instructions provided for the Ubuntu operating system. |
SaaS Agent Control-M Automation API | The Agent upgrade with the provision agent::update API command fails for Agent versions earlier than 9.0.20.280 and for Agents that were upgraded to Agent 9.0.20.280 from an earlier version (see KA 000402673). To prevent this issue from occurring, use the ctmcfg utility to update the SAASCONF.dat configuration file, as follows:
|