IBM i Core V18.1

STRMDM – Create new Screen to view Objects in transfer
A new Option 12 has been added to the Manage Deployment Maintenance screen to view the list of objects in a transfer. This option lists all objects in the transfer, irrespective of their location.

OMQCHGMB – Member API
This API is used to maintain member information within the TD/OMS database. It allows you to add, update, or delete members as needed. For more information, please follow the links below.

Extended views synced to IBMi environment
Several extended views that were previously defined in the data dictionary but missing from the IBM i environment have been identified and added. These views are now fully available and accessible within the IBM i environment, ensuring consistency between the data dictionary definitions and the live system.

Lots of OR libraries on the target system
During transfer processing, a large number of OR libraries were found accumulating on the target system. These libraries are expected to be deleted automatically after a successful promotion. A change has been implemented to ensure the cleanup is performed correctly.

Prevent Deployment Manager logging to the OMS log
Deployment Manager messages were appearing in the OMS log. These messages are no longer recorded in the OMS log.

STRFOF Attaches PROD Source When DEV Object has Uncompiled Source Changes
The Fill Object File function was attaching the Production source to a DEV object when the DEV object had uncompiled source changes. This has been corrected to ensure the appropriate DEV source is retained.

New Object REST API returns an incorrect error message for *MSGF objects
The handling of *MSGF objects in the New Object REST API has been adjusted to ensure the expected error message is returned.

Add Source stream file (SSTF) param to OMQRTVOB command
A new Source Stream File (SSTF) parameter has been added to the OMQRTVOB API. When an object is passed, it returns the IFS (Integrated File System) stream file path containing the source code to compile, if one exists.

2E exit program calls STRFOF incorrectly
The logic has been updated to automatically use *ANY when the owner value is blank, ensuring STRFOF executes correctly.

Missing Override in Journaling logic during transfer
Resolved an issue where file overrides were not always removed correctly. Additionally, the debugging logic in the OMSCRTLIB command has been enhanced to provide more accurate diagnostic information in debug logs.

Task Long description bombs out
While adding a long description in the Task Extended Description field, the application could terminate unexpectedly without displaying an appropriate error message. The handling of long descriptions has been improved to ensure proper validation and user feedback.

Load Procedures List – Replace Logic that requires Fetch on QSYS2.PROGRAM_INFO
Performance issues were reported by some customers while fetching procedure listings that required program information from the system-supplied table function QSYS2.PROGRAM_INFO. To improve response times, the implementation has been updated to use native IBM i APIs instead of querying QSYS2.PROGRAM_INFO, resulting in more efficient retrieval of program information and improved overall performance.

OMQCHGOBJ ACTC(*REFILL) RELI(*IMMED) Relation Build Performance Delay
Delays were observed during the relation-building phase while refreshing one or more objects, where each object is either added if not found in the database or updated according to user specifications or new attributes. The root cause was investigated, bottlenecks were identified, and the necessary optimizations have been applied. The issue is now resolved.

Branch STASH Should Not Be Allowed When a Directory Definition Is Not a Branch Directory
Branch STASH operations could proceed when a directory definition in the branch sub-environment was not configured as a branch directory. Branch STASH operations are now prevented when a required directory definition is not configured as a branch directory.

Source Override Issue When Creating Different Object Types with Same Name
Previously, the system allowed creation of a new object when another object with the same name, but a different object type already existed. This behavior caused source override conflicts and inconsistent object handling. The issue has now been resolved by enhancing the validation logic to properly detect existing objects with the same name across different object types, preventing duplicate object creation and avoiding source override issues

SQL User Defined Function Relationship Not Retrieved from Program
SQL User Defined Function relationships were not being retrieved correctly due to a broken linkage between the SQL function and its underlying program object, resulting in missing or incorrect relationship data. Resolved the linkage issue to ensure that relationship data is now retrieved accurately as expected.

Issues in the Log Details view – numeric search, performance, and wildcard support
Previously, entering numbers in the search field returned no results even when matching entries existed, and search execution was taking over a minute, negatively impacting usability. Both issues have been resolved; numeric searches now return accurate results and perform significantly faster.

Duplicate data identified during processing.
During data retrieval using the database API, duplicate records were intermittently detected and corresponding messages were generated in the job log. This issue has now been resolved, and the data retrieval process is working as expected without generating duplicate record messages.

Retrieve Database API – Date/Time Filters Return No Results
Previously, the Retrieve Database API could return empty result sets when date or time fields were used in filter conditions, despite valid filter values being provided. The API now correctly processes date/time-based queries and returns the expected matching records, improving reliability for dependent workflows.

 Fill Object File access corrected for level 2 users
Authorization handling for the Fill Object File process has been corrected. Users with authorization code 2 (Programmer level) can now execute the process successfully.

Export SQL error logging procedure for reuse
A shared error logging capability has been introduced for SQL-related errors. Previously, this logging functionality was duplicated across multiple programs. It has now been centralized into a single, reusable component, making the system more consistent and easier to maintain going forward.

Search functionality broken in Transfer History view
Previously, the Date and Time field was not being recognized correctly, which caused the search to stop working. This has now been resolved, and users can search Transfer History records by Date and Time as expected. The Search functionality in the Transfer History view has been restored.

Work with Action Selections Screen issue.
The screen was skipping one record on each page-down. The logic has been corrected to display all records properly.

Incorrect Default Subsystem Values in VRYOMSSRV API
The default subsystem values in the VRYOMSSRV API were incorrect, causing the API to fail during execution. The default values have now been corrected to ensure successful API processing and maintain system consistency. Additionally, errors are now logged, allowing users to review failure details using DSPLOGOMS.

Save conflict warning added for externally modified IFS sources
When an IFS source file was modified by another user while already open, saving the open version completed silently without any warning or error, risking undetected overwrite of changes. Now, an appropriate warning is displayed when a save is attempted on a source that has been externally modified, alerting users to conflicts before any changes are lost.

Program call rest API Switch user issue
Switch user logic is added to Program call rest API.

Option 30 on solution – Incorrect behavior when cancelling with F12
When Option 30 is used, cancelling (F12) from the Connection Objects Processing window caused the solution to be disconnected from the task and left in the connection list with (*LASTVRS). Now, the solution is correctly restored to the task, ensuring consistent behavior.

Solution REST API – IFS Object Not Connecting to Task When Already Linked to Other Tasks
An IFS object that is already connected to other tasks can now be connected to new tasks as well.