IBM i Core V19 Milestone 1

Prioritize Build Queue Based on Dependency Hierarchy
When multiple related objects have the same Default Sequence Number, dependency-based serialization is required to ensure the correct processing order in the Build Queue and Transfer. This serialization was already implemented for Transfer, where the Processing Sequence Number was assigned in decremental order. The existing Transfer dependency serialization logic was rebuilt and is now used for Build Queue prioritization, assigning sequence numbers incrementally based on object dependencies. This ensures that related objects with the same Default Sequence Number are prioritized and processed in the correct
dependency order.

OMQCHGNT – New Object Template
This API provides a solution for creating new object templates through a command-line API and a REST API. For more information.

New object/task processing command for Genexus interface
This API provides a solution for processing Genexus objects and tasks through the Genexus interface.

Remove CRTZIPF command
The CRTZIPF command has been made obsolete by recently added native IBM i command CPYTOARCF. The command has been removed and the programs using it have been updated.
If you use CRTZIPF in your own programs then these programs must be changed to also use CPYTOARCF.

Dispatcher upgrade
The TD/OMS Service Framework (aka Dispatcher) has been upgraded:

• Use the latest version of the used open source components.
• Java 17 is now the minimal runtime.
• The ZIP service has been dropped

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