Helix Control-M Releases

Control-M for AWS Mainframe Modernization version 1.0.00 is now available.

Control-M for AWS CloudFormation version 1.0.00 is now available.

Control-M for Azure Resource Manager version 1.0.00 is now available.

Control-M for GCP Deployment Manager version 1.0.00 is now available.

Control-M for GCP Functions version 1.0.00 is now available.

Control-M for Tableau version 1.0.00 is now available.

Control-M for Web Services REST version 1.0.00 is now available.

Control-M for Web Services SOAP version 1.0.00 is now available.

Control-M for AWS Athena version 1.0.00 is now available.

Control-M for AWS ECS version 1.0.00 is now available.

Control-M for Azure Backup version 1.0.00 is now available.

Control-M for DBT version 1.0.00 is now available.

Control-M for GCP Dataprep version 1.0.00 is now available.

You can now determine how events appear in Tile View in the Planning Workspace and Monitoring Viewpoint with the Display Events section in the new Tile Settings feature. This enables you to control whether to display the Event to be deleted or Event raised by If-Action options, or both, in Tile View.

The default hierarchical flow of jobs now appears differently in the Planning Workspace and Monitoring Viewpoint. Events raised by an if-action no longer automatically appear arranged in hierarchical dependencies. You can now toggle between different views in Tile Settings.

• Red Hat on Windows
• Microsoft on Linux
• AWS Corretto Service on Windows and Linux
• SuSE
• Debian
• Ubuntu

Helix Control-M now supports the emdef xml-based utilities. For more information, see emdef Utility for Jobs and emdef Utility for Folders and Calendars.

Note:

• The emdef utility suite is now deprecated. It is no longer enhanced and support will be discontinued in version 9.0.22. For more information, see emdef Utility Suite Deprecation (a Technical Bulletin for on-prem Control-M).
• Typical usage of the emdef utility in Helix Control-M is during a migration from Control-M (on-prem) to Helix Control-M, to ensure that you can continue to use your existing emdef scripts after the migration. 

• A separate application menu, which gives you easier access to the different product domains.
• A new action toolbar in the Planning domain.
• The context menu now allows you to paste a folder or job with their respective events when you plan a Workspace.
• The context menu now allows you to add a folder or job with a right-click on a designated location when you plan a Workspace.
• The context menu now allows you to define links between events and use a set target or source when you plan a Workspace.

• Control-M components now support Java version 17 in addition to 11.
• The installation process now identifies the Java path and sets it accordingly. You do not need to define the Java environment variable before a regular installation.

All Apache Log4j1 issues that were flagged by scanning tools (namely, CVE-2022-23302, CVE-2022-23305, CVE-2022-23307, CVE-2021-4104, CVE-2019-17571, and CVE-2017-5645) have been removed from all Helix Control-M components, even though they did not affect Helix Control-M.

You can now do any of the following:

• Install Helix Agent and Agent, versions 9.0.21.100 or higher, on the same Windows machine.
• Install two or more instances of Helix Agent, versions 9.0.21.100 or higher, on the same Windows machine.

The variable $$PGP_RECIPIENT$$ now resolves for Encrypt and Decrypt commands.

IF-801

Control-M Integrations

Control-M for GCP BigQuery version 1.0.00 is now available.

IF-1051

Control-M Integrations

Control-M for Communication Suite version 1.0.00 is now available.

IF-820

Control-M Integrations

Control-M for GCP Batch version 1.0.00 is now available.

IF-1082

Control-M Integrations

Control-M for Micro Focus version 1.0.00 is now available, with separate plug-ins for Linux and for Windows.

IF-861

Control-M Integrations

Control-M for AWS Step Functions has been updated to version 1.0.01, with the Region field value now based on the {{AWSRegion}} attribute.

WSI-1856

Control-M Integrations

Control-M for Azure Functions has been updated to version 1.0.02, with new fields Verification Poll Interval and Failure Tolerance, and with a new Durable option in the Function Type attribute.

IF-761
IF-961

Control-M Integrations

Control-M for Snowflake and Control-M for Snowflake IdP have been updated to version 1.0.01, with a new Copy into Table action that replaces the Create Snowpipe action.

IF-340

Control-M Integrations

Control-M for Azure Databricks has been updated to version 1.0.04, with the removal of the Job Name attribute, which is not used by any job step.

IF-21

Control-M Integrations

Control-M for Databricks has been updated to version 1.0.04, with the removal of the Job Name attribute, which is not used by any job step.

IF-286

Control-M Integrations

Control-M for AWS Glue has been updated to version 1.0.02, with a new Failure Tolerance job attribute.

IF-358

Control-M Integrations

Control-M for Azure Data Factory has been updated to version 1.0.03, with fixes in the abort operation for REST API steps.

IF-900

Control-M Integrations

Control-M for AWS QuickSight version 1.0.00 is now available.

IF-861

Control-M Integrations

Control-M for AWS Step Functions version 1.0.00 is now available.

IF-941

Control-M Integrations

Control-M for Azure Machine Learning version 1.0.00 is now available.

IF-838

Control-M Integrations

Control-M for AWS SageMaker version 1.0.00 is now available.

IF-125

Control-M Integrations

Control-M for Automation Anywhere version 1.0.00 is now available.

IF-783

Control-M Integrations

Control-M for AWS Batch version 1.0.00 is now available.

IF-1027

Control-M Integrations

Control-M for AWS Data Pipeline version 1.0.00 is now available.

IF-514

Control-M Integrations

Control-M for AWS EC2 version 1.0.00 is now available.

IF-589

Control-M Integrations

Control-M for AWS EMR version 1.0.01 is now available.

IF-642

Control-M Integrations

Control-M for AWS Glue DataBrew version 1.0.00 is now available.

IF-27

Control-M Integrations

Control-M for Azure Batch version 1.0.01 is now available.

IF-553

Control-M Integrations

Control-M for Azure HDInsight version 1.0.00 is now available.

IF-923

Control-M Integrations

Control-M for Azure Logic Apps version 1.0.00 is now available.

IF-532

Control-M Integrations

Control-M for Azure Synapse version 1.0.01 is now available.

IF-394

Control-M Integrations

Control-M for Azure VM version 1.0.00 is now available.

IF-211

Control-M Integrations

Control-M for Google Cloud VM version 1.0.00 is now available.

IF-743

Control-M Integrations

Control-M for Qlik Sense version 1.0.01 is now available.

IF-761
IF-961

Control-M Integrations

Control-M for Snowflake version 1.0.00 is now available. This integration uses token-based authentication.

Control-M for Snowflake IdP version 1.0.00 is now available. This integration authenticates using an Identity Provider (IdP).

IF-51

Control-M Integrations

Control-M for Talend Data Management version 1.0.01 is now available.

IF-724

Control-M Integrations

Control-M for Alteryx Trifacta version 1.0.00 is now available.

IF-340

Control-M Integrations

Control-M for Azure Databricks has been updated to version 1.0.03, with a new job icon and a new job parameter for selection of the job name.

IF-21

Control-M Integrations

Control-M for Databricks has been updated to version 1.0.03, with a new job parameter for selection of the job name.

IF-286

Control-M Integrations

Control-M for AWS Glue has been updated to version 1.0.01, with a new job icon and a change in the name of a connection profile parameter.

IF-358

Control-M Integrations

Control-M for Azure Data Factory has been updated to version 1.0.02, with a new job icon.

IF-46

Control-M Integrations

Control-M for Informatica CS has been updated to version 1.0.02, with a new job icon and several new job parameters.

WSI-1401

Helix Control-M

You can now maintain and troubleshoot Agents from the Configuration domain using the following capabilities:

• Change the Agent debug level and communication trace.
• Collect Agent logs from a specified time period for troubleshooting purposes.
• Perform communication tests and analyses from Helix Control-M to the Agent to troubleshoot unavailable Agents.

WSI-1402

Helix Control-M

You can now configure Agent system parameters from the Configuration domain in Helix Control-M.

WSI-1403

Helix Control-M

You can now provide Reports and API secrets authorization through a Role from the Configuration domain.

WSI-1293

Helix Control-M

Role-Based Administration support is now available for host groups. Teams can view and manage host groups based on their Agent tags. You can add only Agents with the host group tag to the host group.

WSI-1691

Helix Control-M

The cipher suites on Helix Control-M are now updated to only contain ciphers that have a high level of encryption.

WSI-1394

Helix Control-M

You can now create the following new types of reports:

• Notify by Mail Actions​: Lists the folders and jobs that are defined with a Notify by Mail action.
• Change Status or Run Settings Actions​​: Lists the folders and jobs that are defined with one of the following actions:
  • Set to OK.
  • Set to Not OK.
  • Rerun Job.
  • Stop Cyclic Run.
• Run Job Actions: Lists the folders and jobs that are defined with a Run Job action.
• Add/Delete Events Actions: Lists the folders and jobs that are defined with an Add/Delete Events action.
• Set Variable Actions​: Lists the folders and jobs that are defined with a Set Variable action.
• Handle Output Actions: Lists the jobs that are defined with a Handle Output action.

WSI-1660

Helix Control-M

The authorization rule value length is increased to 2,048 characters in the following domains:

• Planning: In folders, jobs, and Run As.
• Tools: In all available tools, such as Calendars, Events, Lock Resources, Pool Variables, Resource Pool, Site Standards, and User Views.

WSI-1593

All Control-M components now use AES256-GCM encryption.

CTM-4306

Run As can now be managed by an authorized User in the Configuration domain of Helix Control-M.

WSI-1509

Helix Control-M

You can now set the Adjust Event field to Bridge on folders, which instructs Helix Control-M to bridge the missing prerequisite Events automatically.

WSI-1508

Helix Control-M

You can now define dynamic folders and jobs post processing logic based on variable values in If-Action.

WSI-1507

Helix Control-M

You can now define the Run Job and Ignore Scheduling Criteria Action in folders and jobs to Run as an independent flow.

CTM-1699

Helix Control-M

You can now create Notifications if the calculated future cyclic submission of a job or folder is late by <x> minutes.

WSI-1510

Helix Control-M

You can now create a dedicated sub-folder that references an existing folder or a specific job within a folder or sub-folder.

WSI-1668

Helix Control-M

Site Standards now allows you to define default values for Conditional Rules.

WSI-1010

Helix Control-M

You can now apply and manage Site Standards across multiple folders and Servers with Site Standards Policies. For more information, see Site Standards.

Control-M Automation API

2022-10 (October)

Jackson Databind is upgraded to version 2.9.10.8, which resolves the following vulnerabilities: CVE-2019-16942, CVE-2019-16943, CVE-2019-17531, CVE-2019-20330, CVE-2020-10672, CVE-2020-10673, CVE-2020-10968, CVE-2020-10969, CVE-2020-11111, CVE-2020-11112, CVE-2020-11113, CVE-2020-9548 and CVE-2020-9547 (see 000366964), CVE-2020-9546, and CVE-2020-8840.

WSI-1557

Control-M Automation API

You can now transfer alerts to an external client for monitoring through external tools, such as an event management system. New API commands enable you to manage a reliable stream of alerts from Helix Control-M and to manage the listener process on your client.

WSI-1291

Control-M Automation API
Agent

The new provision agent::update API command enables you to perform an automatic upgrade. This API command downloads and installs the latest version of Control-M/Agent and any installed plug-ins to the agent machine that runs the command. 

To run this command, the current version of Agent must be 9.0.20.280 or higher.

WSI-1264

Helix Control-M/Agent

2022-10 (October)

The following operating systems are now supported:

• Windows 2022
• Windows 11
• AWS Linux 2022
• Red Hat Linux 9
• Debian 11

WSI-1621

Helix Control-M/Agent

Application Integrator and Automation API CLI are now included in each Agent. This makes Application Integrator based plugins more accessible and provides immediate support for Application API.

WSI-1643

Helix Control-M/Agent

Control-M now requires an external JRE when you install or upgrade your Agents, Control-M MFT, and Plug-ins. To ensure that Java remains updated, JRE deliveries are now decoupled from Control-M and are no longer part of the installation. This reduces installation size and enables you to use the JRE that is common within your organization. You must ensure that Java 11 is available on the Control-M/Agent host machines. For a list of supported Java vendors, see Compatibility with External Java Vendors.

CTM-5003

Helix Control-M/Agent

PowerShell, Perl, Python, and VBS embedded scripts are now supported, as described in OS Job.

CTM-6160

Helix Control-M/Agent

(UNIX Only) You can now restrict the executables that can be run using sudo. For more information, see set_agent_mode Options.

WSI-1434

Control-M Application Integrator

A new Application Integrator user interface simplifies the development of plug-ins and enhances the user experience.

WSI-1670

Control-M Application Integrator

The Google Cloud Platform (GCP) authentication that uses identity tokens is now supported.

WSI-1671

Control-M Application Integrator

File uploads in job definitions are now supported, which enables you to include pre-defined configuration in job definitions by uploading a configuration file, such as a YAML file.

WSI-1672

Control-M Application Integrator

You can now add JSON objects to REST calls.

CTM-5909

Control-M Application Integrator

Google-Cloud-Platform-(GCP)-based integrations are now supported.

CTM-4297

Control-M Application Pack

The Tomcat Web Server is upgraded to version 9.0.58.

WSI-1606

Control-M for AWS

The Identity and Access Management (IAM) role for accessing AWS is now supported, which is reliant on temporary security credentials.

WSI-1663

Control-M for AWS

You can now connect to AWS via proxy.

WSI-1354

Control-M for Airflow

The new Control-M for Airflow plug-in enables you to trigger, schedule, and monitor Airflow DAG runs, view DAG task names, status, and any defined task variables.

WSI-1337

Control-M for SAP

You can now import SAP calendars from your SAP computer to your Control-M environment for use when defining batch jobs.

WSI-1657

Control-M for SAP

The following new actions are now supported for SAP jobs:

• SAP R/3 Jobs
  • Monitor a scheduled job.
  • Run a pre-defined SAP job.
  • Watch for an SAP event.
  • Trigger an SAP event.
  • Run a batch input session.
  • Activate/Deactivate an SAP profile.
• SAP BW Jobs: You can now run InfoPackages in addition to (the previously supported) Process Chains.
• SAP Data Archiving Job (New)
  • Write job.
  • Detect delete job.
  • Detect store job.

CTM-4377

Control-M for SAP

You can now add the SAProuter string parameter when you connect to SAP.

CTM-44

Control-M Managed File Transfer

TLS protocol version 1.3 (IETF RFC8446) is now supported.

CTM-55

Control-M Managed File Transfer

The transferred file name can now contain the full Dataset name in z/OS.

For more information, see the description of the com.bmc.aft.configurable.zos.useFullDatasetName parameter in aft_configurable.properties File Parameters.

CTM-4040

Control-M Managed File Transfer

You can now select the PGP operation (encrypt/decrypt) in job definitions when you transfer from local file system to local file system or between local file system and remote hosts.

CTM-6341

Control-M Managed File Transfer

You can now limit access to a specific set of users. Multiple users and user groups that are based on filter patterns are added to a list of allowed and blocked users, such as jdoe or user*.

CTM-5336

Control-M Managed File Transfer

The SFTP connection profile supports the generation and authentication of the following additional key types:
ECDSA (256, 384, and 521 bits)

CTM-5225

Control-M Managed File Transfer

File Transfer Server key authentication now supports the following additional SSH key formats:

• ECDSA (256, 384, and 521 bits)
• Ed25519 (256 bits)

CTM-5888

Control-M Managed File Transfer

Integration with Azure Data Lake Storage (ADLS) Gen2 is now supported.

CTM-376

Control-M Managed File Transfer

The File Transfer Server now generates an Access Log file.

CTM-2163

Control-M Managed File Transfer

You can now create a unique name for a file if another file with the same name is detected during a file transfer.

CTM-4658

Control-M Managed File Transfer

You can now change file permissions in either the source host or the destination host after a file transfer to or from a UNIX system.

CTM-6353

Control-M Managed File Transfer

You can now perform multipart downloads of files between Azure Blog Storage and the local file system using the new com.bmc.aft.configurable.azure.useMultipartDownloadOnDownloadToLocal parameter.

CTM-5755

Control-M Managed File Transfer

The following parameters now enable you to resolve file names or rename files in the destination path:

• $$AFTFILE$$
• $$AFTFILE_ALL$$
• $$AFTFILE_EXT$$
• $$AFTFILE_NAME$$

CTM-5363

Control-M Managed File Transfer

Installation now supports the underscore character ( _ ) in the hostname.

CTM-5682

Control-M Managed File Transfer

AWS PrivateLink for Amazon S3 is now supported.

CTM-6229

Control-M Managed File Transfer

You can now select EBCDIC mode for transfers between AS/400 and z/OS.

CTM-6390

Control-M Managed File Transfer

You can now define FTP QUOTE commands as pre-commands in a File Transfer job over an FTP connection.

CTM-6391

Control-M Managed File Transfer

You can now select any existing coded character set identifier (CCSID) encoding in FTP ASCII mode using the %%AFT_ALTER_TYPE_CMD1 and %%AFT_ALTER_TYPE_CMD2 parameters.

WSI-1737

Control-M Managed File Transfer

You can now Run File Transfer jobs on Agents installed on Debian 11 platforms.

WSI-1853

Control-M Integrations

Control-M for AWS Glue is now available.

WSI-1854

Control-M Integrations

Control-M for Azure Databricks is now available.

WSI-1855

Control-M Integrations

Control-M for Azure Data Factory is now available.

WSI-1856

Control-M Integrations

Control-M for Azure Functions is now available.

WSI-1857

Control-M Integrations

Control-M for Boomi AtomSphere is now available.

WSI-1858

Control-M Integrations

Control-M for Databricks is now available.

WSI-1859

Control-M Integrations

Control-M for Google Cloud Platform (GCP) Dataflow is now available.

WSI-1860

Control-M Integrations

Control-M for Google Cloud Platform (GCP) Dataproc is now available.

WSI-1861

Control-M Integrations

Control-M for Informatica Cloud Services is now available.

WSI-1862

Control-M Integrations

Control-M for Microsoft Power BI is now available.

WSI-1863

Control-M Integrations

Control-M for UiPath is now available.

You can now view a graphical representation of execution insights for all tenants in the organization in the Usage Measurement dashboard.

You can now change the display language to one of the following: English, German, Spanish, French.

• Administrators can set the default display language for all new users.
• Users can change the display language for their interface only.

You can now send notifications to a destination via a Windows or Linux script on an OS job type.

The NotifyScriptLnx and NotifyScriptWin options appear in the If-Action drop-down list after you manually define as free text.

The script names are predefined in the Agent home directory, as follows:

• Linux: $CONTROLM/NotifyScriptLinux.sh
• Windows: NotifyScriptWindows.bat

It is preferable that the scripts under the Agent home directory point to a shared location and are accessible to other Agents.

Helix Control-M

Automation API

2022-03 (March)

WSI-1524

Helix Control-M

Automation API

2022-03 (March)

You can now download the complete AAPI CLI package.

• There are no required prerequisites.
• All necessary JAVA and nodeJS packages are included.
• The installation automatically sets AAPI to your BMC Helix Control-M tenant.

Helix Control-M

Automation API

2021-06 (June)

You can now set the Workflow retention period up to 14 days in Helix Control-M and Automation API, as follows:

• Helix Control-M: System Settings
• Automation API: Set the historyRetentionDays property in the JSON payload file. For more information about the historyRetentionDays property, see General system settings.

The default value is 4 days.

WSI-889

WSI-991

WSI-1037

WSI-1038

The response to the build command now provides validation warnings when site standards are applied and validations are not strictly enforced. For more information, see Build service.

Deploy Descriptors now support new options for manipulating JSON job definitions. You can now use a Deploy Descriptor to add or delete objects and properties in JSON job definitions, in addition to the previously available options for modifying job definitions by assigning new values in job properties or replacing job properties. For more information, see Deploy Descriptor.

The new, standard installation of Control-M Automation API now installs Control-M Automation API CLI with all of its prerequisite components (including, for example, Node.js). For more information, see Setting up the API.

Helix Control-M

Control-M Automation API

Deployment fails for a Peoplesoft-type job that was obtained using the deploy jobs::get command. The following error is issued:

"unknown type: Job:PeopleSoft" 

Helix Control-M

Helix Control-M

The displayed Run Date (for example, on the Summary tab of the Monitoring domain) refers to an erroneous date in the past if the browser locale is set to GMT-. This is only a display problem, and jobs run on their proper dates.

Helix Control-M

A Viewpoint with grouping by Run Date displays jobs in an incorrect order (that is, not sorted in chronological order). This occurs after upgrading to version 9.0.21.100.

The connection to the Alerts listener (for the transfer of alerts to an external client) goes down every two hours.

Output files are deleted earlier than expected. A warning message is issued in the Agent Daily log:
"FILE... REMOVED FROM BACKUP/SYSOUT DIRECTORY WITH WARNING:  ..."

As part of the resolution, the GENERAL_CLEANUP_INTERVAL parameter default was changed from 30 to 100.

The external Java check script log incorrectly reports a mismatch with the Control-M/Agent Java version.

(Linux/UNIX Only) The CPU usage is incorrectly calculated on the Agent when it is configured to use East Asian (CJK) language characters. The following message appears in the prolog directory:
Unable to calculate CPU usage from sar utility.

Some usernames do not appear in the Configuration domain when more than 60 users are added.

The Save button does not work in Edit Viewer > Access Control > Monitoring > Job Permissions in the Roles window of the Configuration Domain when the Contains all filter is used.

An incorrect filename appears for a transferred file in the destination folder when the filename has been shortened with the N#–# Name Pattern renaming tool in the Destination Filename tab and when one of the numbers in the range is a double-digit number.

You are not able to browse or transfer files on a remote FTP server when the connection is over SSL and the session must be resumed by the server. The following error message appears:
javax.net.ssl.SSLHandshakeException: Remote host terminated the handshake.

The list of names fails to load in the Notify section of the Upon Completion dialog in the Oracle E-Business Suite job definitions when one of the names includes an apostrophe. The following error message appears:
ctm5311 cm for oebs:ora-01756: quoted string not properly terminated

OEBS jobs execute with the wrong date format when the OEBS version is 12 or higher.

The elapsed time is incorrectly recorded for a PeopleSoft job when it is not provided directly from the PeopleSoft server.

A System Exception error occurs when you click Load in a PeopleSoft job to see a the list of processes and one or more process descriptions contains a " (quotation mark) character.

Helix Control-M

2023-05 (May)

Helix Control-M/Agent

2023-01 (January)

Helix Control-M/Agent

2023-01 (January)

The CVE-2022-32215, CVE-2022-32214, CVE-2022-32213 vulnerabilities are detected in NodeJs.

To resolve this issue, you must install patch PAFZ4.9.0.21.081 on your Agents. Although Control-M/Agents are not impacted by the vulnerabilities detected in this binary file, the patch replaces this binary file in the Agent package.

Helix Control-M/Agent

2023-01 (January)

The CVE-2022-37614 vulnerability is detected in the Control-M Automation CLI.

To resolve this issue, you must install patch PAFZ4.9.0.21.081 in your Agents. Although Control-M/Agents are not impacted by the vulnerability detected in this binary file, the patch replaces this binary file in the Agent package.

CTM-7430

Helix Control-M

2022-11 (November)

Permissions for the following actions on services in the Monitoring domain are not enforced correctly:

• Drill-Down
• Run 
• Hold
• Resume
• View runnable services that were run by other users.

CTM-7434

Helix Control-M

2022-11 (November)

Days in a periodic calendar or a regular calendar are incorrect or are shifted by one day when you use the recurrence option to mark weekdays, and when the language in the browser is not US English.

CTM-7361

Helix Control-M

2022-11 (November)

The tree in the navigation pane of a viewpoint is displayed with incorrect hierarchy when you open a viewpoint with non-default grouping and grouping is turned on.

Helix Control-M

CHECK OUT CALENDAR appears instead of ADD CALENDAR as the audit operation in the audit_activities database table when you add a new calendar.

CTM-6820

Helix Control-M

One or more folders are removed from the cache by the GUI Server definition cache in the rare event that the folders fail to be loaded from the database server, and they appear only after you update the folders or the GUI Server definition cache is reset.

CTM-2597

Helix Control-M

You cannot group the services grid by the Run Date (previously Order Date) column as expected.

CTM-6299

Helix Control-M

The Active Audit report sub-type returns uninformative data about internal user jmamaMaster1.

CTM-3847

Helix Control-M

A new step is added with the same step number when you duplicate a step in a SAP R3 job.

CTM-4344

Helix Control-M

The changes that you make to Control-M for SAP and Control-M for Hadoop configuration utilities are not audited.

CTM-4529

Helix Control-M

The type of database that appears in the job definition is SSIS instead of MSSQL and the Execution type drop-list is missing the SSIS package and MSSQL agent job types when you select a connection profile that is set with SSIS packages in a Databases job definition.

CTM-5907

Helix Control-M

Jobs that are defined with the same name but have different schedules, appear with the same schedule.

CTM-5703

Helix Control-M

The Databases job type is missing the Catalog Environment field.

CTM-6215

Helix Control-M

A resource is applied automatically, based on a rule for a Resource Pool (previously Quantitative Resources) on a Site Standard for all job types on a folder, even though you cannot define a Resource Pool on a folder.

CTM-6674

Helix Control-M

No results appear when you define a Databases job and browse for an SSIS configuration file.

CTM-4371

Helix Control-M

No results appear when you define an AWS job to search for a state machine and only one result matches the search filter.

CTM-5999

Helix Control-M

The list appears in the wrong order when you sort by the deadline time column on the Services tab in the Monitoring domain.

CTM-5797

Helix Control-M

Deleted folders appear instead of an empty list when you filter a search by Job Name, Member Name, Application, or Sub-application in the Planning domain. This occurs when certain folders are pending deletion.

CTM-5793

Helix Control-M

An error appears in the Run report, even though a job runs successfully, when the job that contains a long path name.

CTM-5196

Helix Control-M

The Total Number of Resource Pools (previously Quantitative Resources) parameter shows the currently available resources instead of the total resources defined. This parameter appears in job definitions in Helix Control-M.

CTM-4581

Helix Control-M

The On statement type does not appear correctly in the Helix Control-M when the On code field of the deployed folder contains one of the following patterns: <, >, <=, >=.

CTM-1886

Helix Control-M

The On Folder Ended Not OK does not include the action Stop Cyclic Run in the list of actions available when you add a new If-Action (previously On-Do action) to a cyclic folder in the Helix Control-M Planning domain.

CTM-5366

Helix Control-M

The job log date format does not match the browser date format, even after you change the browser date settings, as described in 000235561.

CTM-5644

Helix Control-M

The On setting of an If-Action (previously On-Do) incorrectly shows Job Ended not OK instead of Specific statement output. This happens when you add an If-Action with a specific statement output and you set the statement to *, and then edit the If-Action again. Despite the incorrect On setting, the job runs with the correct If-Action.

CTM-5517

Helix Control-M

You cannot add or delete an event from a job on the Waiting Info tab in the Monitoring domain. This happens when you have both Browse and Update access or Full access to the Event.

CTM-5652

Helix Control-M

Validation of a Workspace remains at 99% if you click Modify after importing a large Workspace.

CTM-5649

Helix Control-M

A split-screen appears when you disable a domain tab from a User View and log in again.

CTM-2522

Helix Control-M

An empty service tab appears in the Viewpoint when you open a service that contains a large number of jobs.

CTM-3465

Helix Control-M

Unhandled errors that occur in Helix Control-M enable information leakage or unused custom error messages.

CTM-5957

Helix Control-M

An empty schedule appears when you view the schedule of a Rule Based Calendar in a loaded folder.

CTM-6069

Helix Control-M

You cannot see the full job name when you view a predecessor or successor job in the Monitoring domain.

CTM-5824

Helix Control-M

Control-M Reports generates a partial report when you specify a group that contains wildcards.

Helix Control-M

The following message appears in the Validation pane when a user creates a sub-folder inside a folder that is defined with a Site Standard rule on a cyclic property:
Internal validation problem.

CTM-5966

Helix Control-M

A validation error occurs when you import a Workspace with a job that is defined with a From time that is earlier than the End of day (new day time).

CTM-5570

Helix Control-M

The report fails to generate when you copy a string of characters that includes a Carriage Return character (\r) from an external editor to Report filter parameters in Control-M Reports.

CTM-6703

Helix Control-M

The New Destination field is not mandatory when you select the Move Action for an Output Handling rule.

CTM-5466

The Append option does not work on a remote z/OS platform when you use the SITE command that changes the encoding. Instead, the file is overwritten.

CTM-5467

The Pre/Post commands do not work if the specified path is a relative path.

CTM-6183

A file transfer to a mainframe that uses FTP over SSL, and is larger than 17 GB, fails and the following error appears:
NullPointerExcption

CTM-6398

Upload to an AWS S3 bucket fails when the uploaded file is larger than 50 GB, and the following error message appears in the log:
com.amazonaws.services.s3.model.AmazonS3Exception: Part number must be an integer between 1 and 10000.

CTM-6503

An SFTP Connection Profile test fails when the remote host is a Microsoft Azure SFTP server.

CTM-6524

Cluster hosts are not added to the known hosts file when authorizing an SSH cluster, if the cluster is listening on a non-default port.

CTM-6544

It takes too long to transfer of a large number of files from an OS400 directory.

The Token parameter value in the OAuth2 settings is not validated.

A job fails when it executes a REST call with the PATCH method. The following error message appears in the job output:
Invalid HTTP method: PATCH.

The timeout of an Application Integrator job appears as an unresolved parameter in the job output instead of the actual number of minutes, when the job is set with a timeout and the timeout is defined in the job definition.

The following is an unresolved parameter example:
Exit Message = Application Integrator: UCM0001 = The job failed - Got timeout on Verify Operation completion (took over {{timeout}} minutes.

The REST API response is not processed correctly if it contains the & (ampersand) character.

This happens when you define an Application Integrator job with a REST execution step.

Authentication tokens do not refresh when an Azure service response is Token is expiring.

An Application Integrator job succeeds even though it is set to fail when the Set to fail if extracted data option is set in the Output Handling section and the condition is met.

You cannot deploy Application Integrator job types with Control-M Automation API if you enable Annotation, and the following error message appears:
Job could not be deployed.

A default parameter value that you define in JSON format turns to [object Object] when you import or export an Application Integrator job type.

Control-M for Hadoop

Control-M for Informatica

Control-M for Azure

Control-M for AWS

Control-M Application Integrator

Control-M for Hadoop

Control-M for Informatica

Control-M for Azure

Control-M for AWS

Control-M Application Integrator

You cannot view the job output of a job type when the job output size is several MB. The following error message appears:
Failed to get output

Control-M for Hadoop

Control-M for Informatica

Control-M for Azure

Control-M for AWS

Control-M Application Integrator

A job fails when you set the job with a centralized connection profile and the total length of the connection profile fields exceeds 4,096 characters. The following error message appears in job output:
Connection profile not found.

Control-M for Informatica

Control-M for Azure

Control-M for AWS

Control-M Application Integrator

Control-M for Hadoop

Control-M for Informatica

Control-M for Azure

Control-M for AWS

Control-M Application Integrator

A process stops on all Agents when you stop the process on just one Agent and when multiple Agents run as root on the same UNIX server.

Control-M for Hadoop

Control-M for Informatica

Control-M for Azure

Control-M for AWS

Control-M Application Integrator

Control-M for Hadoop

Control-M for Informatica

Control-M for Azure

Control-M for AWS

Control-M Application Integrator

Control-M for Hadoop

Control-M for Informatica

Control-M for Azure

Control-M for AWS

Control-M Application Integrator

Control-M for Informatica

Control-M for Azure

Control-M for AWS

Control-M Application Integrator

The following AWS regions are missing when you create a connection profile:

• eu-south-1
• us-iso-west-1
• af-south-1
• ap-southeast-3

A Control-M for Azure job fails when the Logic App end time is empty. The following error message appears in the job output:
Error while executing the logic app: null.

The following error message appears in a Netbackup job definition when you select Application and Automatic Backup or Transaction Log backup for the field Schedule:
java.lang.ArrayIndexOutOfBoundsException.

The time parameter is missing, which returns a large number of responses from the NetBackup server when running in CLI-only mode.

The following error message appears when you define a Databases job to load an embedded a query from a file:
file not found.

You cannot browse various folders in search of an SSIS package if the package source is set to catalog when you define a Databases job in Helix Control-M.

Databases jobs get stuck in execution. The Application Pack process consumes high CPU and memory when the database server returns a large number of warning messages. Warning messages found in the output include the following:

• Warning: Null value is eliminated by an aggregate or other SET operation.
• The operating system returned error 665.

A Databases job output times out if the job output is empty, and the following error message appears in the job log:
Sysout file was not generated for this job.

The Control-M for Hadoop plug-in installation fails on EMR EC2 servers and the following error message appears:
could be found for logger (com.bmc.onecm.ipp.Engine.Main).

The ctm/proclog/application_pack_fresh installation log file includes the following error message:
*java.nio.file.FileAlreadyExistsException: /tmp*.

Control-M for Hadoop Oozie jobs fail when the job is executed on a machine with a high load and the server ID is not sent back immediately from Oozie. The following error message appears:
oozie id cannot be null.

The date format of a SAP message is different from the format that is configured in the SAP user profile in a SAP job output.

The connection profile test fails on Windows if the JCO library version is 3.1.x. The following error message appears:
Incompatible JCO library file.

A connection to SAP that uses SNC fails when the value for the User Name in the SAP table USRACLEXT (transaction SM30) is * and the JCo version is 3.0.14 or higher.

For a workaround, see 000324846.

The following error message appears when you load a failed ABAP program:
CTM5311 socket closed due to unknown reason

The Target Server value in the External Command and External Program steps is mandatory when it should be optional.

An SAP job fails when the Variant name contains no English characters. The following error message appears:
Variant does not exist.

The SAP Java process fails to submit SAP jobs when using JCo version 3.1.3 or higher. The following error message appears in the logs:
Control-M For SAP: 0001 = com/sap/conn/jco/rt/DefaultParameterField

A new value is copied to the Job Name field after you update the SAP job name field using Find and Update.

CTM-5924

Helix Control-M/Agent

2022-10 (October)

The content of the ctm/proclog/Metrics folder is never cleared from the Agent machine.

Control-M for Hadoop

Control-M for Informatica

Control-M for Azure

Control-M for AWS

Control-M Application Integrator

2022-04 (April)

Vulnerable CVE-2022-22965 is detected.

The Spring Framework is now updated to version 5.2.20.

For more information, see 000395657.

2022-03 (March)

There is no indication of the time segment and execution times in Control-M Reports when the the workload history report runs.

CTM-6565

2022-03 (March)

All months are always selected when you duplicate a Rule Base Calendar in the Calendar tool.

2022-03 (March)

Users are incorrectly allowed to use the term localhost in the logical name and the physical hostname when installing Agent.

Helix Control-M

2021-06 (June)

In Agents tab, in the Configuration domain, the Delete Agent action fails with an error message even if the deletion completes successfully when the physical name of the Agent contains Latin characters or a . (period) character.

The Run Job and Ignore Scheduling Criteria action in the Planning domain, in Job Settings > Actions > If-Actions, accepts variables even though they are not supported.

If you have already defined jobs using the Run Job and Ignore Scheduling Criteria action with variables, you receive a notification to remove these variables when you open these definitions in a Workspace.

CTM-4463

Importing an Application Integrator job from the communities hub fails with the following error message:
There was an error getting the file.

CTM-4224

Control-M for Hadoop

Control-M for Databases

Control-M for Informatica

Control-M for AWS

Control-M for Azure

Control-M Application Integrator

CTM-4286

Installation fails on EMR EC2 servers with the following error message:
could be found for logger (com.bmc.onecm.ipp.Engine.Main).

The installation log file, ctm/proclog/application_pack_fresh, contains the following error message:
java.nio.file.FileAlreadyExistsException: /tmp.

The Agent daily log file shows event processing failure messages for events that are triggered by SAP jobs, even though it should not show these messages. For example:
ATW000:AG_MTRACKW_receive_event: Failed to process event for orderno 05ttw runno 36