New Release TD/OMS Core V17.0 Milestone 3

New Release TD/OMS V17.0 Milestone 3

Monday, Wednesday 14, 2025

To learn more about the specific enhancements and how they can benefit your organization, explore the detailed breakdown below.

New and Noteworthy in TD/OMS V17 Milestone 3

Dynamic Compile Results Based on Selected Source Tab

The compile result view now dynamically updates to reflect the selected source tab, ensuring that the displayed compile results correspond to the active source.

 

Improved Error Line Mapping

From the Build Queue, you can use the menu option “Show Errors in Source”. In some cases, primarily when using SQLRPGLE, the error location was not placed on the correct line.

 


Components View in Table
Layout

Updated the components view layout to a table format, improving readability, organization, and usability.

 

 

Enhanced Transfer API to Include Job Description Details

The Transfer Wizard now includes a final page where users can set schedule dates and job descriptions for the remote machines.

 


New Tabs in Component Editor

The Component Editor has been enhanced with three new tabs:

Transfer History Tab: Displays detailed information about all transfer activities related to the selected component.

Dependencies Tab: Shows an overview of components that either depend on or are used by the current component.

Object History Tab: Lists all tasks or objects with which the component has been previously associated, providing a comprehensive history for tracking and reference.

 

Multi-selection in Solutions Tab of Item Editor

The Solutions tab in the Item Editor now supports multi-selection, allowing users to select multiple solutions simultaneously. This enhancement enables actions such as locking or unlocking multiple solutions at once.

 

RDi & Standalone Client

Functionality has been implemented to hold a job during the transfer process based on user selection. If the ‘hold’ option is selected, the system will now hold the job accordingly.

 


Note: The registry OMQDEPLOYCTL must be set for the application when you want to hold the remote transfer. If this registry key is not active, the transfer for the remote job will not be held.


IBM i Core

 

T00410 – Program call REST API
We have developed a new Program call REST API. For more information, please click the link below.
REST Program call API

I03136 – Managed Deployment System
A new maintenance screen and command line API have been created for the managed deployments.

T00419 – Managed Deployment REST API
We have developed a new Managed Deployment REST API. For more information, please click the link below.
REST Managed Deployment API

I03236 – Add progress support in Transfer API.
Upon completion or during execution of a transfer job, the progress bar provides a detailed overview of the transfer status.

For more information, please follow the link below.
REST Transfer Objects API

I03153 – OCTO – Enhance Transfer API to include job description details.
The job description and hold job functionalities have now been implemented in the Transfer API. For more information, please follow the link below.
REST Transfer Objects API

I03204 – Added logic to hold job based on selection during transfer.
Functionality has been implemented to hold a job during the transfer process based on user selection. If the ‘hold’ option is selected, the system will now hold the job accordingly.

Note: The registry OMQDEPLOYCTL must be set for the application when you want to hold the remote transfer. If this registry key is not active, the transfer for the remote job will not be held. For more information.


Octo Server

961 – Created a command to reset the Octo admin token. For the docker-compose en Kubernetes environment there is a script available that will clear the currently set admin token.

Gravity Server

909 – Xref support for Octo
A Gravity CORS server setting has been introduced so that Xref has better support for being accessed from a browser.
I2166 – Solved Solr vulnerabilities in Gravity, all registered Solr 4.3.0 vulnerabilities (CVEs) have been assessed and addressed.
To mitigate potenially harmfull XSS attacks from the Solr Admin UI, we have removed the Admin UI, also the Solr replication handler has been disabled to remove the possibility of SSRF exploits.
I2168 Upgraded mysql jdbc connector 8.0.23
The Gravity JDBC driver has been upgraded to support version 8 of the MySql database.


Rich Client Rdi

I03144 – For a SonarQube issue, showing the issue info was not working for a SonarQube server version 2025
The SonarQube interface has been updated to recognize the new issue info layout of SonarQube server 2025
I03231 – HOLD Job Checkbox Behavior Incorrect During Job Scheduling
The HOLD checkbox is now disabled by default during job scheduling to prevent unintended changes. It becomes enabled when a remote system is selected and
schedule details are modified, ensuring correct job setup and reducing conflict risk.


OpenAPI Generator

I03241 – REST API – Adjusted Packed Decimal Field Formatting
When generating REST APIs, numeric fields with packed decimal format (6:0) are rendered without any trailing zeroes or decimal points (e.g., 123.00 = 123). However, if the field is in packed(6:2) format, trailing zeroes should be preserved to reflect the precision (e.g., 123.00 = 123.00).
I03184 – REST API – Client generator fails to load the response data properly
The issue with parsing and loading the JSON response data in the client-generated REST API has been resolved.
I03193 – REST API – Excessive Memory Allocation for Local Variable in Client REST API
The issue was caused by excessive memory allocation for a local variable in the generated client REST API, and this has now been resolved.
I03057 – Rest – Client generator issue for setting the default value
The Client API Generator allows users to manually set default values when generating a client for an API.
I03081 – REST – Retrieve database issue
The Retrieve database API now returns the correct records when multiple groups are linked to a single parent group.
I03087 – REST – Retrieve database issue for sortFields
The sortBy field can be left blank, and it will default to “ASC.”
I03126 – Client Code Generator Issue for Array Type Response
The parsing of the inline array reference schema was incorrect in the generated CLIENT API.

PLEASE ACCESS THE PAGES AND FULL RELEASES NOTES FROM HERE