What's New

CTM-9938

The Build service incorrectly executes the Deploy service. This occurs if the job was defined as a root object with a PathElement property.

CTM-9916

The Run service fails to order a z/OS folder if the version of the Control-M/Server is 9.0.21.200.

CTM-9858

The Alerts Listener is terminated when there is an overload of alerts on the sever side and the Alerts Listener client is unable to process them all.

As part of the resolution of this issue, the output of the Alert script is no longer included in the Alerts listener log. When listenerLogLevel is set to debug level, the exit status from the Alert script is included in the Alerts listener log.

CTM-9830

The config server:runasusers::get API command consumes a large amount of CPU when there are many Run as Users defined.

CTM-9730

The Alerts Listener process appears to be connected, even though the WebSocket gateway is experiencing a connection issue and no alerts are sent for up to two hours.

CTM-9692

Job deployment fails when the job contains an event and the job was defined as a root object with a PathElement property. This issue occurs when a site standard was applied to the folder that contains the job.

The following error message appears:

Out condition... already exists

CTM-9453

Job deployment fails for a job of type Job:Database:StoredProcedure, if the stored procedure does not have any defined parameters.

The following error message appears:

AGENT IS UNAVAILABLE

CTM-9391

The config server:runasusers::get API command exhibits bad performance when you run it as a non-Admin user.

CTM-9849

The config server:agent::ping command initiates too many internal polling requests to Helix Control-M, every 10 milliseconds instead every second.

CTM-9839

Provision actions fail when Automation API CLI sends requests through an HTTPS or HTTP proxy server.

CTM-9806

The deploy job::delete command fails to delete a job if the job name contains space characters, even though spaces are allowed in job names.

CTM-9494

The CVE-2023-45857 vulnerability was reported in axios 0.25.0, which is used by the Control-M Automation CLI. This vulnerability does not impact Control-M Automation API.

A newer version of axios is now packaged with Control-M Automation CLI.

CTM-9203

An API token does not grant proper permissions to the associated users after the name of the associated role is changed. API token details are not synchronized and the role name is not updated.

CTM-9218

Provision actions fail when Automation API CLI runs on AIX 7.3.

CTM-9675

The run ondemand API command ignores the specified Host property of a job in a sub-folder, and this might cause the job run to fail.

CTM-9517

The deploy jobs::get command fails to return the specified parameters in a Stored Procedure Database job.

CTM-9527

Deployment of a job that was obtained from a later version of Automation API (using the deploy jobs::get command) fails in an Automation API environment of an earlier version, due to unrecognized (new) job properties. The following error is issued:

<Name of new property> is an unknown keyword...

CTM-9442

Password-type fields are corrupted in Application Integrator connection profiles when you make changes to non-password fields.

CTM-9425

The run ondemand API command ignores the specified Host property, and this might cause the job run to fail.

CTM-9357

The deploy jobs::get command does not return an array of jobs from a sub-folder specified through the folder field in the search query, even though useArrayFormat=true was included in the search query.

CTM-9228

The deploy connectionprofile::test API command fails with the following error:

Failed to validate the connection with the selected Agent.

CTM-9404

Job deployment fails for a job of type Job:Database:StoredProcedure, if the job runs on a PostgreSQL database and the stored procedure has no return value.

CTM-9247

After an upgrade on AIX 7.2, Control-M Automation API fails to start.

CTM-9235

The config server:agent::update API command fails to update the sslState parameter on the Agent. In addition, the range of values for the maximumRetries parameter is too narrow (up to 10, where some users might need values up to 100).

CTM-9229

Agent provisioning fails if the Control-M Automation CLI version differs from the Automation API version on the Server.

CTM-9162

The default value for the Delimiter parameter under a Capture Output action (Action:CaptureOutput) is an empty value. It should be WhiteSpace.

CTM-8693

Non-default scheduling definitions are set to default values during deployment of a job that was defined as a root object with a PathElement property.

CTM-5592

The run variables::set API command fails when a named pool variable contains an underscore character.

CTM-8883

A return code of 500 (server internal error), instead of 404 (defined item not found), is issued when you attempt to GET details regarding objects in a folder that does not exist in Server.

CTM-7709

The deploy sitestandards::get API command returns a corrupt JSON when the list of Site Standard rules contains conditions. The Conditions array is not created, and condition details appear directly under the Rules object. Deployment of this JSON fails with a null pointer exception error.

CTM-8719

Deployment of an array of jobs fails with a java.lang.NullPointerException error when a validation error is detected in one of the job properties.

CTM-8823

Deployment fails with a "Table in use" error. This occurs if Control-M/Server attempts to synchronize folders at the same time as the deployment.

CTM-8524 CTM-5559

Control-M Automation API does not preserve memory settings during an upgrade, and instead resets them to default.

CTM-8337

Job deployment fails when the job contains an Action:Run and the job was defined as a root object with a PathElement property.

CTM-7634

Deployment fails for a job of type Job:DetachedScript with the RunAsDummy property set to true.