IBM i Core V18 Milestone 3

Support for SQL UDFs
Internal SQL function relationships are now correctly reflected in ‘Used By’ references.

VRYOMSSRV – Command to control TD/OMS Services
This API is used to control the TD/OMS services. It allows you to start, stop, or restart the TD/OMS services as needed. For more information

Improved INZGITOMS
INZGITOMS – TD/OMS init. GIT Repository has been updated to copy source members using a configurable naming setting, controlled by the registry OMQIFSSRCNAMEC.

Git
We are preparing for a Git interface rebuild and we now ship the first integretion command BLDIFSOMS which can be hooked into CTRL+E in VSCode to upload, attach and compile sources from Git. The previous version of the Git interface was centered around RDi. The new version will be IDE agnostic so that it can be integrated in any IDE or DevOps pipeline.

BLDIFSOMS- Build Solution from IFS.

Processes an IFS file in various ways to be able to connect the resulting object to a task. This can be used in VSCode CTRL+E environments or DevOps pipelines where sources are managed through git.

Deprecated TD/OMS internal Git commands.

We supplied our own git interface through Java. Since then, IBM i includes a git client that can be installed with the YUM command.

See also

• Command BLDIFSOMS Build Solution from IFS
• Registry OMQIFSCONSTMF Connect IFS File to Task
• Registry OMQIFSSRCNAMEC IFS Source naming conventions
• Registry OMQGITPRCRTE TD/OMS Git Source Route

Improved installation version checker
It has come to our attention that in some situations versions can be skipped with the TD/OMS installation program. We have added checks to ensure that product installations are always correct.

Added signature to OMLOGGER Service Program
We have added a signature to the OMLOGGER service program. OMLOGGER enables logging into the TD/OMS log. If you are using OMLOGGER in your own programs, then these programs should be recompiled.

Allow or block potential version conflicts confirmation
A potential version conflict is a state where the same object is attached to two or more tasks but none them was committed to production yet. A Version conflict confirmation has to be done by the developers to indicate that the changes of the other task have been incorporated (merged). Potential Version conflicts should not be confirmed too early because there is always the possibility that a new change is made after the initial confirmation.

If you find yourself in this situation too often then you can use the OMQALWPVCONF registry to block confirmations of potential version conflicts.

IBM i Core Other Issues Resolved

No DSPFs available in TD/OMS after upgrade to 18.0M02

The object file fill process now continues even if an error occurs for any intermediate object.

Incorrect Current user when same CGI job is used by more than one user requests.

The current user is now correctly fetched and updated.

TFROBJOMS API fails when task status is **ERR

The TFROBJOMS API now handles the **ERR task status correctly.

OMX899 crash due to invalid array index

Now we do not get an OMX899 crash when %lookup(*blanks: array) returns 0, as the case is handled.

Allow potential version conflicts confirmation

An option is now available to control and block confirmation of potential version conflicts using the OMQALWPVCONF registry setting. For more information, see the OMQALWPVCONF registry documentation.

 Managed Deployment Maintenance – Schedule Date issue when Format is not *DMY.

Logic was converting all dates to DMY. As of now, dates are converted based on the job date format.

OMQRTVSE – Reference Library List Sequence Issue.

Special values *FIRST and *LAST were changed to resolve to -1 and -2 respectively.

Processes calling the API using special values *FIRST or *LAST were updated accordingly to stay in sync with this change

 Location type selection on object library gives unexpected result

Location type selection based on the object library now returns the correct location type.

OMQCHGCL – Incorrect response of API

The Connection List API now validates that the solution type cannot be changed to *COMPILE when the solution is in the production library. If such a change is attempted, the API will return a meaningful error response.

Invalid Job Details Caused Spool File API Failure

The spool file API should validate job details before proceeding. If the provided job details are invalid, the API must return a structured error response with a descriptive message and must not continue with further processing.

Selective source inclusion during deployment

We are able to configure a sub-environment to include only specific sources. However, TD/OMS still expected the source to be present in the OR library for all solutions with a source processing indicator. As of now, the sending system ensures that the receiving system is informed when the source is not included for such solutions.

OMQRTVSE – Retrieve Sub Env – Fetch *LAST sub Env not working.

Special value *LAST was incorrectly resolving to 1.This has been corrected to return the actual last sequence value

Fill Object File REST API – Job Not Submitted in Batch

Fill Object File REST API now submits jobs in batch.

Connection List Error When Copying Task

When a task is copied, the system now assigns the current object library from the source task instead of retaining an invalid value. This ensures that the connection list is processed successfully without errors.

Source API save fails when TDOMS holds member lock

Source API now successfully saves the source even when the source date is left blank.

Retrieve Database issue – DISTINCT needs fields

Retrieve Database API now accurately returns records when the distinct record set is enabled, even without return field details specified.

Unable to Load All Spool Files from Component View

We are now able to load all spool files from the component view.

SAVLOGOMS crashes on date *ALL

The menu logic has been updated to prevent passing *ALL as the default value. The command now executes successfully with valid input.

OMQRTVRC – Retrieve route code help text

Help text has been added to this command. Follow this link to refer the documentation.

Deployment Should Create /tmp/remain/deploy Directory if Missing

The deployment process now creates the /tmp/remain/deploy directory automatically if it does not exist.

OCTO Error message shows short name

The issue where the OCTO Build Queue error message displayed the short name instead of the long name has been resolved.

XXV180SEC security program should add the /tmp/remain/deploy dir

The XXV180SEC security program now creates the /tmp/remain/deploy directory and makes it publicly accessible.

 Cleanup of remote /tmp/remain

Remote /tmp/remain/deploy/OR directories and the OR libraries are now cleaned up properly.

SpoolFile and TransferHistory dates returned in formatted string instead of century format

In the Spool File Component view, all date fields should be consistently displayed in the YYYY-MM-DDTHH:MM:SSZ format.

Retrieve Database API – Time Format Separator Issue

The Retrieve Database API will always return the time in the HH:MM:SS format, using a colon (:) as the separator.

Source API – IFS File Name Case Preservation Issue

When saving an IFS source file, the Source API preserves the original case of the file name and does not convert it to uppercase anymore.

OCTO Component member view must show source members only

The component view will consistently display members from source PF objects, while excluding any members that belong to data PF objects.

Log History Filter Returns Unfiltered Results

The Log History API is now working at the specific task level, and the task-level filtering functionality is also working correctly.

Editing IFS causes filename to become all UPPERCASE

When saving the IFS source file, the Source API now preserves the correct file name casing.

Enhanced Security with Restricted Root Access

Temporary distribution folders were previously created in the root (/) file system, which posed a security risk. They are now created in a dedicated directory under /tmp/remain/deploy/OR… to improve security and prevent unnecessary access to the root file system.

Create ObjectVersionConflictExtended View

In OCTO at the task level, the Version Conflict view previously displayed the IFS short name instead of the long name. To address this, the ObjectVersionConflictExtended view was created to retrieve and display the IFS long name based on the short name.

OMQRLH – OMS Log Message API Issue

Filtering with the same date format shown in the Log History plugin now returns the expected results

Action group selection is not working

During transfer, negative object library selection with wildcards (* or ?) did not function in Action group selection.

Registry value for OMQPRCLODINT is missing

The registry value for OMQPRCLODINT has been added.