What's new in this version
New developments in this version are divided into the following categories:
The following new features were introduced in the specified versions:
Support for the AWS job type, enabling you to automate a select list of AWS services and manage the Control-M for AWS connection profile.
|184.108.40.206||Code Reference > Connection Profiles||ConnectionProfile:Aws|
|A new type of Database job enables you to run an embedded query.||220.127.116.11||Job types||Job:Database:EmbeddedQuery|
Two new API commands are now available for management of Site standards defined in Control-M. One of these commands retrieves a list of allowed values defined for a restricted-text field in a Site standard, and the other replaces the defined values with a new set of values. These commands are supported in Control-M environments with Control-M/Enterprise Manager version 9.0.19.000 or later. Currently, the API commands support only the application field in a Site standard.
|18.104.22.168||Services > Deploy service||deploy sitestandard:fieldRestriction::get|
|The new CustomPath parameter was introduced in Hadoop-type connection profiles, for use by jobs that run Spark programs.||22.214.171.124||Code Reference > Connection Profiles||ConnectionProfile:Hadoop > Job:Hadoop:Spark|
|The new NumberOfRetries parameter was introduced in File Transfer job types, to define the number of connection attempts after a connection failure.||126.96.36.199||Code Reference > Job types||Job:FileTransfer|
The Control-M Workbench can now be installed and used as a Docker image.
The Control-M Workbench was tested on Docker version 19.03.1.
|188.8.131.52||Installation||Installing the Control-M Workbench on Docker|
|The new SSHCompression parameter was introduced in the SFTP File Transfer connection profile, enabling you to compress the file before file transfer.||184.108.40.206||Code Reference > Connection Profiles||ConnectionProfile:FileTransfer:SFTP|
You can now use the new run job::modify command to modify the settings of an active job that is currently held (that is, a job for which processing has been stopped), based on job settings that you define through a Job Definitions file.
In addition, the new run job::get command enables you to obtain the details of an active job. The output of this command is especially useful as the basis for your Job Definitions file when performing a Modify action.
|220.127.116.11||Services > Run service|
You can now include an additional header in login requests sent by the CLI using the new additionalLoginHeader property in the environment update command.
This is useful, for example, if your connection with the API server goes through an API Gateway that requires an additional authorization header during login actions.
|18.104.22.168||Services > Environment service||environment update|
File Transfer jobs now support file transfers from the local filesystem to an AS2 server using the AS2 protocol. A new AS2 connection profile is available for use by such File Transfer jobs.
|22.214.171.124||Code Reference > Connection Profiles|
|File Transfer jobs now support the FTPS (FTP over SSL) communication protocol. A new type of connection profile is available for use by such File Transfer jobs.||126.96.36.199||Code Reference > Connection Profiles||ConnectionProfile:FileTransfer:FTPS|
|The new config item::recycle command enables you to recycle (that is, restart) a specific Control-M component. Currently, this command supports recycling of Control-M/Agents.||188.8.131.52||Services > Config service||config item::recycle|
The RerunIntervals and RerunSpecificTimes properties now support folders, in addition to jobs.
|184.108.40.206||Code Reference > Job Properties|
File Transfer jobs now support file transfers from the local filesystem to Amazon S3 storage or S3-compatible storage and vice versa. For such file transfers, the new S3BucketName parameter must be included in the job definitions. New S3 connection profiles are also available for use by these File Transfer jobs.
|220.127.116.11||Code Reference > Connection Profiles||ConnectionProfile:FileTransfer:S3:Compatible|
The following changes were made in existing features in the specified versions:
Date and time formats in the response to the run job:log::get command have changed to match the formats in other API calls. The following formats are applied:
|The response to the |
|Services > Config service||config servers::get|
The following table lists issues that have been corrected in the most recent releases:
Deployment of a folder fails due to a problematic calendar definition, and returns the error "external validator 'TagSelectionsValidator' is not found."
If a flow is deployed in XML format and it fails to deploy, the tempPasswdFile file, which contains sensitive connection details, is not deleted after completion of the deployment action.
Validation of site standards for a deployed folder is always set to strict.
Resolution: Validation of site standards during folder deployment/build is set to match the DefaultNewFolderStrictness system parameter.
When a folder contains a confirmation calendar with a rule-based calendar defined under it, the deploy jobs::get command returns an error:
|CAD-2696||If no port is specified in a connection profile, the deploy connectionprofiles::get command returns a port number 0 for the connection profile. Deployment of such a connection profile fails with the error message "Port must be a number between 1 to 65535."||18.104.22.168|
|DRDEV-67||In Control-M Automation API version 22.214.171.124, the run events::get command fails to return the list of events when no date filter is specified.||126.96.36.199|
|DRDEV-64||The Swagger-based REST API reference for Control-M Automation API does not display in Internet Explorer 11 (IE11).||188.8.131.52|
When folder definitions contain the RerunLimit property, the deploy jobs::get command fails, and an error is issued: "Folder has an unsupported property "max_rerun"..."
If annotation is enabled in Control-M, annotations are required also in API commands. Annotations cannot be set to optional in API commands.
For information about changing the default behavior and setting annotations as optional in API commands, see the Control-M Administrator Guide in the Control-M Online Help.
The run job::modify command returns an error, "No site standard set to folder F." This occurs when site standards are activated, Control-M Workload Change Manager is active, and the Control-M/EM system parameter DefaultNewFolderStrictness is set to R (activated).
|DRDEV-55||In the output returned by the run job:status::get command, the end time is incorrect and is the same as the start time.||184.108.40.206|
|DRDEV-48||Provisioning operations fail due to insufficient permissions for the temporary directory created during the provisioning process in the TEMP directory.||220.127.116.11|
The deploy jobs::get API command returns the following error: "Failed to get Folder data from Control-M... For input string: \"\""
When deploying a folder that is defined in XML, the new folder is not synchronized in Control-M/Server.
When deploying a folder that is defined in XML, special characters for the local language are not encoded correctly.
When deploying a folder that is defined in XML on an environment that requires annotations, the annotations are not set correctly.
Configuration actions performed by the config service do not work on Solaris and AIX.
Deployment of a job in XML format times out after a minute, with no user control over the timeout definitions.
To resolve this issue:
|DRDEV-43||When deploying a job that uses a site standard with a rerun interval, the job fails to validate and issues an internal validation error.||18.104.22.168|
|DRDEV-41||When more than one API session use the same token, after one session logs out, the other sessions might receive a null pointer exception error.||22.214.171.124|