TD/OMS V19 Milestone 1

New Release TD/OMS V19 Milestone 1

Wednesday, Oct 7, 2026

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


VSCode & Octo Web 


ServiceNow

ServiceNow integration is now added to OCTO. Tasks and any entity that extends it (Incidents, Problems etc.) can be viewed, filtered and linked/unlinked to TD/OMS tasks.


New IFS file wizard

Added a new IFS File Wizard to simplify the creation of IFS files. The wizard guides users through selecting the target environment and route, specifying the destination directory and file name, and creating the new IFS file.

It also provides the option to create a new IFS file by copying the contents of an existing IFS file, making it easy to reuse existing source content.

Labels Tab in Solution Editor

The Solution Editor now includes a dedicated Labels tab, allowing users to view, create, edit, and delete labels associated with a object from the solution.

Stashed Branches

The Branches plugin has been enhanced to show the stashed branches. Besides filtering, restore and purge actions are also available on a single or multiple branches.
With a simple option, the users can now switch between the active and stashed branches.


Transfer History Tab in Solution Editor

The Solution Editor now includes a Transfer History tab, allowing users to view the transfer history for the currently selected solution.



IBM i Core

Overriding TD/OMS OMSREFOBJ object deployment authorities
TD/OMS normally applies deployment authority using the standard OMSREFOBJ reference object processing. This works well for most deployments, but some objects require different authority settings after deployment.
This enhancement introduces the GRTAUTREFO command to support object-specific authority overrides as part of the deployment process. Some deployed objects require more restrictive or different IBM i object authority settings than those inherited from the normal OMSREFOBJ model. Examples can be:

  • SQL exit programs
  • Security-related programs
  • Objects deployed into special system libraries
  • Objects requiring specific ownership for adopted authority

Filter has been implemented in DSPLOGOMS
The DSPLOGOMS screen now includes Occurrence date and Filter search options to easily find jobs by Date, Job Name, User, Job Number, or transfer number. For more information, you can see the DSPLOGOMS documentation.

Create an API to Link or Unlink Tickets to the Task and Request
A new command-line API has been created to link or unlink a ticket to a task or request. Previously, linking or unlinking a ticket did not generate event topics. Event topics are now generated with the appropriate payload whenever a ticket is linked to or unlinked from a task or request.

BLDIFSOMS Fails Processing IFS Object

The following functionality is now working as expected:

  • BLDIFSOMS no longer throws an error when processing IFS objects on a case-insensitive directory.
  • Objects having no source are now getting connected correctly during BLDIFSOMS processing.
  • The object description is now displayed correctly when the directory is not case-sensitive.
  • The source file is now populated correctly during BLDIFSOMS processing.

Extend backend service to support new IFS file creation
The New Object API now includes a new /addIFSObject path for creating new IFS objects.

Extend backend service to support new Data Area creation
The New Object API now includes a new /addDataArea path for creating new Data Area objects.

PULLVAROMS should return a proper message
The PULLVAROMS command now checks the supplied buffer length against the correct minimum/maximum for the specified interface level and issues a proper error message when the value falls outside the valid range, instead of failing silently or returning an unclear error.
The buffer length required by the Pullvaroms command depends on the interface level in use:

  • Interface level V3R0M0 – buffer length must be between 340 and 1024 bytes
  • Interface level V5R1M0 – buffer length must be between 377 and 1024 bytes

PLEASE ACCESS THE PAGES AND FULL RELEASES NOTES FROM HERE