ORN:V16.1 Release Notes Summary
Jump to navigation
Jump to search
In case you do not want to wait for the official milestone build, you may install the nightly builds.
New and Noteworthy in TD/OMS V16.1
| Web Support | Did you know that your favorite change management system now comes with a brand new Web Development environment. Our Web Framework is called Octo and with Octo we are geared towards a zero install development experience.
We still support our rich client and RDi, because these are still the best option for power users. Also the green screen and VSCode are part of the UI mix.
|
|---|
| VSCode Integration | We have officially released our VSCode extension. In order to use it you have to setup your Octo environment. Please reach out to us if you need help.
|
|---|
| I02741 - Allow the creation of SSL rest server instances | The command CFGRESTSRV has been extended to allow SSL configurations. |
|---|
| I02716 - REST API Documentation | The REST API documentation is up to date. For more Information, you can see REST APIs documentation. |
|---|
| New CLI API's | We are moving all TD/OMS business logic into separate programs for our back-end modernization project. These APIs can also be called using a command with the same name. To access additional information about these APIs, please click on the link below. |
|---|
| New REST API's | We have developed a set of new REST APIs. To access additional information about these APIs, please click on the link below. |
|---|
| Dependency Charts | In the Web or VSCode, find the components menu to open the dependency chart.
|
|---|
GUI issues/enhancements resolved
- I02692 - Application interface does not work in collapsed mode in the GUI
- Fixed a bug where the collapsed mode was not showing all correct results in the components view.
- I02710 - Possible duplicate nodes in trees are compared only based on name
- There was a bug where two possible duplicate nodes were compared only by name while now they will be compared based on their object as well.
- 02062 - Compiling with erors
- There was an issue where the compile result view wouldn't open after a compile.
- I02739 - Object types and attributes not updated
- Fixed an issue where the object types and attributes were not saved or were disabled in the libraries in definitions.
- I02720 - Handled null pointer exception on get license end-date
- If back-end licensing is not setup properly, authorization wise, then this would cause the null pointer exception
- T00376 - Create a new Solutions Viewer
- Now the search of the solutions viewer works in a similar way as in the components view, namely to be able to use the * and % characters in search for solutions that start with or end with a string of characters.
- T00338 - Upgrade the definitions view
- Added documentation to the definitions and removed any irrelevant context menu actions from the view.
Server issues/enhancements resolved
- 737 - Move Solution functionality in the ITEM Editor
- We have added the same move solution functionality to the ITEM editor already available in work management.
- I02753 - OMQRNO - Rest API contains the incorrect logic
- API had some incorrect logic which resulted in incorrect response. A change has been added to rectify this.
- 637 - Add to build queue adds objects not in *DEV.
- Now it does not add objects that are not in development.
- I02747 - New Object Rest API does not return the correct error message
- Extra validations have been added to return the correct messages from the API.
- I02751 - Ignore Leading Zero in Job number
- In the fill object REST API, the leading zero of the job number is now ignored.
- I02744 - SpoolFile Rest API Issue
- We can delete all the spool files for a particular user.
- I02733 - Solution Rest API issue
- Added the functionality to delete the object and source when a disconnect action is triggered.
- 727 - Checkout and promote do not work for IFS objects inside the Item Editor.
- It works when we try to check out and promote at the task level, and now it also works when we check out or promote from the Item editor.
- 715 - Checkout and promote is not working for IFS object
- Checkout and promotion are now possible for IFS objects.
- 671 - Checkout is not working properly
- You can now check out objects from the production environment with authorization code 2.
- I02361 - Deprecate old servers
- The OMSOCTO and OMSREST services are removed from TD/OMS. They have been replaced by Octo Server and the Apache rest services.
- 684 - Transfer REST API Issue
- If a task has no solution or has *ANY status, we can either promote it or check it out.
- I02674 - Show completion date for finished tasks
- The "Work with Tasks" screen now displays dynamic dates based on the status of the task. You can see Fix Maintenance documentation for more information.
- Q817 - Not able to connect Lansa objects
- An issue was resolved where an export of a WAM did not take the associated service program in the export. Now the service program is added to the export again.
- 02058 - Usage in modules not recognized when long sql table names are used.
- When long table names were used in modules the reference to the short table were not visible in TD/OMS. For example, assume a table long name BC_CONNECT_BOOKING_JRN, with system name PFBCBU00. If we do a connect with rules for PFBCBU00 then only the programs that use PFBCBU00 were connected to the task. The modules were missing. This issue is fixed
- I02713 - The library name in the action is not correct.
- During the transfer, the correct library is used in the message logs.
- I02723 - STRFOF crashes
- STRFOF no longer crashes due to insufficient authorization.
- I02722 - STRFOF crashes because the application doesn't exist
- STRFOF is not crashing anymore.
- I02708 - RGZOMSF
- The RGZPFM is now executed with KEYFILE *NONE to ensure proper execution when the command defaults have been altered.
- 02050 - We can not compile after upgrade to 16.0M3
- When a selection is defined with a *LIST - on Label, the type code API did not return the correct compile command.
- I02717 - REST API - Retrieve the object information exclusively from the Source API
- In the Source API, setting pageNumber to 0 indicates that we need to retrieve the fundamental details of the object, including the CSSID, the source's editability, the type of source, and the total record count.
New and Noteworthy in OCTO V1.3.0 (1.3.0 Release: July 3, 2024)
| Dependency Charts | We are proud to present a depdendency visualization engine with the following initial options. The plugin will be automatically installed when the 'Dependency Chart' action is selected for a component.
The tree visualization collapses and expands when you click on a node. Use the expand/collapse toolbar item to expand and collapse the entire tree (
|
|---|
| Kanban improvements | The Kanban board has been improved in the following areas
|
|---|
| Move solution to another task | We can move the solutions to another task in VSCode and the Web.
|
|---|
| Change the solution type. | We can change the solution type in VSCode and the Web.
|
|---|
| Change the transfer path. | We can change the task transfer path in VSCode and the Web.
|
|---|
| Disconnect solutions from the task | We can disconnect the solutions (and optionally delete the objects and source from disk) in VSCode and the Web.
|
|---|
| Assign/Unassign Programmer
|
We can assign or unassign the programmer from the task in VSCode and the Web.
|
|---|
| Complete Task
|
We can complete a task in VSCode and the Web.
|
|---|
| Workspaces View
|
We've added a view where you can see and manage all your workspaces links in one place.
|
|---|
OCTO Other issues/enhancements resolved
- 811 - OCTO - Failed to fetch transfer history
- When we attempt to retrieve the transfer history of the solution, it should return the corresponding transfer history records for that solution.
- I02689 - Unable to create a new member
- If a member is already part of the task, we can now create a new member with the same source file and library.
- 737 - Move Solution functionality in the ITEM Editor
- We have added the same move solution functionality to the ITEM editor currently available in work management.
- 733 - Disconnect functionality in the ITEM Editor
- We have added the same disconnect solution functionality to the ITEM editor currently available in work management.
- I02749 - Build queue rest API sometimes works with the wrong user
- In the build queue, users can now only see their objects, not those of other users.
- 623 - Add to build queue does not work when the file is saved
- When we save the source in VS Code, the object is now added to the build queue.
- 633 - Octo VS Code - Add workspace state rebuild support.
- Loading Octo in VS Code should be able to rebuild the current workplace state from memento.
- 635 - Octo client - Add a plugin to handle workspace links.
- A plugin where to view and edit user's own workspace links. It should be available both in web client and VS Code.
- 636 - Add to build queue does not work when the object is already in the build queue.
- The appropriate message is given when the object is already in the build queue.
- 641 - Octo Memento Retains Task Selection Across Configurations.
- When a task is selected within the work management system for a specific configuration in Octo, and subsequently, the user switches to another configuration, the selected task
persists within the Octo memento. However, upon reloading the configuration, an informational alert is displayed indicating that the selected task is not found in the current configuration. This behavior can lead to confusion and inefficiency for users..
- 648 - OCTO - Item Editor Issue
- Identifying which object was designated as either *COMPILE or *TERMINATE has been simplified.
- 649 - Inconsistencies in Promote Wizard Page Display and Grouping Logic
- Upon selecting a sub-environment in the initial wizard page and proceeding to the next step, inconsistencies arise:
- 1. Duplicate Transfer Object Groups: The following wizard page presents two groups with identical transfer objects. This redundancy confuses users and disrupts the workflow.
- 2. Incorrect Grouping by Task Number: Furthermore, the grouping logic on the second page is based on task number rather than sub-environment, which contradicts our intended design and creates confusion among users.
- 650 - Promoting a Solution from Solutions Tab Leads to Full Transfer Overview Instead of Target Object
- Currently, when attempting to promote a solution from the Solutions tab, the system displays the entire transfer overview showcasing all transfer objects related to the task. This results in unnecessary clutter and confusion for users, as they only need to see the object they intend to promote.
- 653 - Implement Link to Open Compare Editor
- Currently, users can access the compare editor via the "Compare with Production" context menu. However, there is no implementation that allows users to open the compare editor directly from a link. This feature would significantly enhance user experience by providing more flexible access to the compare editor.
- 654 - Octo Client - D3js integration
- Integrate the D3.js library charts to be used by Octo plugins.
- 655 - Implement VS Code Source Compare that Opens Dedicated Compare Editor
- This issue proposes implementing a source compare feature in VSCode that functions similarly to the Octo Monaco editor. This would involve opening a dedicated compare editor window when comparing two files.
- 656 - VS Code Octo server setting update does not work anymore
- I've encountered a problem with the VSCode Octo extension. It appears that the server setting update feature is no longer functioning. Upon investigation, it seems that the script file responsible for handling the save action has been removed from the media directory.
- 657 - Create a source compare with revision for Monaco in OCTO
- We implemented a feature that allows users to compare different sources with revisions specifically for Monaco in OCTO.
- 658 - Rename the Object Service to Entity Service
- The Object Service currently performs the same functions as the Entity Service; however, it was named differently. To maintain consistency and clarity within our codebase, the Object Service is renamed to Entity Service.
- 660 - Monaco - Typing is slow
- Every cursor action in the Monaco web editor has a delay. Coding is not nice in the editor.
- 661 - Monaco - When scrolling to the end of the document the editor titles disappear
- When scrolling to the end of the document the editor titles disappear
- 674 - The attribute shouldn't be mandatory during the creation of the panel group
- When creating a panel group in OCTO, the attribute is no longer mandatory.
- 675 - Create a source compare with revision for Monaco in VS Code
- We implemented a feature that allows users to compare different sources with revisions specifically for Monaco in VS Code.
- 676 - Octo Client - Add charts examples plugin
- Add an Octo plugin to illustrate how to use the core chart data providers and types.
- 677 - Replace 'objectAttribute' with 'source type' from SourceReply
- Currently, we use 'objectAttribute' from the solution to define the extension of the source. However, this field doesn't always exist, causing inconsistencies and potential errors. To improve reliability, we need to switch to using the 'source type' that can be retrieved from the SourceReply.
- 680 - OCTO - Disconnect solution issue.
- The sequence of solutions in the disconnect solutions wizard was incorrect.
- 681 - Source saving is not working
- Source saving does not work if the spool is open.
- 682 - Revert Bootstrap to 5.2.3 Due to UI Problems in 5.3.3
- We have recently upgraded Bootstrap from version 5.2.3 to version 5.3.3 in our project. However, this upgrade has introduced several UI problems that are impacting the user experience. These problems were not present in version 5.2.3, which suggests that the new version has introduced changes that are incompatible with our current implementation.
- 683 - Item Editor Optimizations
- When the item editor refreshes, it refreshes all open editors. This can be inefficient and disrupt user workflow. We propose the following optimizations:
Refresh Only Active Editor; When a task is selected, the open item editors should not be refreshed; Don't refresh the spool file component on task selection.
- 685 - Octo client - Plugin reveal with preinstall causes dispatch event issue
- A revealed/automatically installed plugin may get the same event more than once.
- 686 - Octo client - Enable tree chart expansion and collapse
- Make it possible to expand/collapse a tree chart.
- 687 - Octo client - Allow plotting a chart directly from a URL
- Make it possible to draw a chart directly from a URL pointing to some JSON file containing tree data.
- 691 - Octo client - Allow chart data providers to register for URL handling
- An Octo chart data provider may choose to register for URL handling. The core will revive the right data provider to further process and plot the incoming URL.
- 692 - Running men icon disappears in dark mode during task transfer
- When a task transfer is initiated, the running men icon is displayed correctly in light mode. However, if the mode is switched to dark mode, the icon becomes invisible. This issue needs to be resolved to ensure the icon is visible in both light and dark modes.
- 693 - Source Editor Plugin
- We can scroll the title away
- When the mouse pointer is in the header of the view and the source editor is open then using a scroll will scroll the title out of view.
- 694 - Octo client - Automatically dismiss info toasts
- Automatically dismiss info and success toasts after a short given time.
- 696 - Info message "Task not found in Test 16.1M00 " displayed every time.
- Whenever you log in to OCTO or reload the page, the "Task not found: / in Test 16.1M00" message is displayed every time.
- 697 - Components filter does not work for STMF objects
- IFS objects can be filtered
- 698 - Checkout One Object Does Not Work as Expected
- Currently, the checkout functionality is not working as intended. Instead of fetching only the specified object, the system retrieves all objects and the GUI subsequently filters to display the correct one. This results in unnecessary data retrieval and processing.
- 699 - Show the long IFS name in the solutions tab
- 700 - New Object Wizard does not show the correct error message
- The new object wizard now provides the correct error message.
- 701 - Refreshing Browser Shows Login Dialog Briefly for Logged-In Users
- If a user who is already logged in to Octo refreshes the browser, all displayed plugins initially show the first login dialog. After a short period, the login dialog disappears, and the content of the plugins is shown. There is no need to show the login dialog if the user is already authenticated. This behavior can be confusing and disrupts the user experience. The expected behavior is to directly show the plugin content without the login dialog if the user is already logged in.
- 702 - Replace Hardcoded Field Names in OCTO Code with Static Fields
- In the OCTO codebase, there are numerous instances of hardcoded field names. This approach can lead to maintenance challenges and increase the risk of errors. To enhance code maintainability and readability, replace these hardcoded field names with static fields sourced from params or the corresponding entity classes.
- 705 - Build Queue Unresponsive to Save Event in VS Code
- When saving a source file in VS Code, the build queue does not react to the save dispatch event.
- 707 - Add Scrollbar to Task Details in Item Editor
- In the item editor, task details are displayed without a scrollbar when their content exceeds the tile height. Currently, the entire tile scrolls to view all details if all headers are expanded. This makes navigation and usability difficult.
- 708 - Change Hardcoded Fields to Read-Only Fields in VS Code
- In the current implementation of VSCode, there are certain fields that are hardcoded. To enhance flexibility and maintainability, these fields should be converted to read-only fields. This change will ensure that the values can be viewed but not altered directly, improving the overall robustness of the application.
- 709 - Octo client - Opening KanBan via link doesn't work
- Kanban URL API doesn't work correctly.
- 710 - Octo client - Open a chart via a link
- Add URL API support to charting.
- 711 - Octo VS Code - Add support for Octo charting in VS Code
- Enable opening the Octo charts plugin in VS Code.
- 712 - Make selection of multiple environments more clear
When a task contains multiple environments and we attempt to transfer it, the message displayed on the wizard is unclear. Users are not explicitly informed that they must select an environment from the environment selection list. This can lead to confusion and hinder the task transfer process.
- 713 - Wizard doesn't display the message.
- The wizard displays a message when no reason code or transfer path is found for the application.
- 714 - Create New object Template Issue.
- There should be no spaces in the name of the new object wizard when a message is selected.
- 715 - Checkout and promote is not working for IFS object
- Checkout and promotion are now possible for IFS objects.
- 716 - An unnecessary message is displayed
- Unnecessary messages will no longer be displayed in the connection list.
- 717 - CMD Source Type Missing in Source Editor
- The type of the CMD source on the source editor is empty, resulting in the source code not being highlighted. Please update the source type to ensure proper syntax highlighting.
- 718 - Octo client - Transitional page shows up before loading the perspective
- When reloading Octo web client and before loading the perspective, a transitional page indicating there is no perspectives yet is shortly shown when is shouldn't..
- 719 - When pressing refresh, the item editor gives an error
- How to reproduce: Open a task in the item editor > Press F5 > Error (see attachment).
- 722 - Build Queue Message text issue.
- We have shortened the lengthy message text in the build queue.
- 723 - Add Functionality to Delete All Spool Files from Spool File Component
- Implement a feature that allows users to delete all spool files within the spool file component efficiently.
- 724 - Octo client - Plugin addition/removal should be allowed for all org owners
- Any owner of an Octo org should be able to remove/add a plugin within an org perspective.
- 725 - Octo client - Plugin reveal should work regardless of perspective authority
- Plugin reveal should work even if the user can't install the plugin being revealed.
- 726 - Connection list issue
- We can now choose a particular object to remove from the connection list.
- 728 - Error Opening Solution Due to Invalid Page Number
- Opening the solution in the earlier versions does not work.
- 729 - Tasks do not filter on the release field
- We can now filter tasks based on the release field.
- 730 - Access token not found message is displayed each time on configuration switch
- When switching configurations, an error message stating "Access token not found" is consistently displayed. This issue occurs every time a configuration change is made, regardless of the specific configurations being switched.
- 731 - Update 'getJsonWebToken' in the Login Service to Handle Refreshing Token from Old Token
- The current implementation of the getJsonWebToken method in the Login Service does not support the functionality of refreshing an old token to obtain a new one.
- I02750 - Item editor refresh does not refresh ratification
- After activating the ratification, refreshing the ratification tab in the item editor does not retrieve the updated task information.
- 734 - Octo client - Add a TD/OMS chart data provider
- A TD/OMS chart data provider that is registered by the Octo available providers and will be automatically initiated to handle chart URL meant for TDOMS.
- 735 - The displayed file name based on the solution is wrong for a member in VS Code
- When viewing a file associated with a solution member in Visual Studio Code, the displayed file name is incorrect.
- 736 - Source Type Missing When Opening Source from Component
- When opening a source from the component, the source type is not displayed. This issue makes it difficult to identify and categorize the source properly.
- 738 - Mismatch in Source File ID between Item Editor and Components View
- The source file retrieved from the item editor and the components view does not have the same ID. As a result, the file will be opened twice if it is called from both the item editor and the components view. This discrepancy leads to redundancy and potential confusion for users.
In case you do not want to wait for the official milestone build, you may install the nightly builds.
New and Noteworthy in TD/OMS V16 Milestone 3
 I02631 - Action group on SL is wrongly executed
|
When an action group selection is specified with 'Object Detail' detail and value '*BLANK' then this selection would be inverted. This means that some action groups will stop functioning.
This bug was introduced with V15.0 Milestone 3 and has been patched in V15.1M02. User may upgrade to V16 milestones as well. To check if you are affected:
All affected V15 users must upgrade to V15.1M02 All affected V16 users must upgrade to V16.0M02 or V16.0M03 Nightly What can happenAction Groups that are executed on SP,SL,EL,EP,SD and ED that use the 'Object Detail' detail and value '*BLANK' selection may not trigger anymore or trigger when a member is promoted. This may have an effect on the following standard actions groups:
WorkaroundIf you cannot upgrade quickly the the following workaround is possible:
After the upgrade you must again reverse the selection. |
|---|
| T00376 - Create a new Solutions View | We have a new view that shows the solutions (objects attached to a task) in a separate table. This makes working with large tasks a lot easier.
The documentation can be found here
|
|---|
| 02041 - Unable to deploy transfers over 2GB | The TD/OMS legacy file transfer module cannot handle file transfers when the save file to be sent is over 2GB. This is a limitation of the current deployment application. We are currently rolling out a new deployment mechanism that does not contain this limitation and, amongst other things, provides encrypted connections. To mitigate the problem, we produced two new registry settings to allow for compression of the save file:
|
|---|
| T00373 - Support type details in the definitions | Type details have been added in the definitions view. Now the pre-compile commands, compile commands and post-compile commands can be viewed, created, changed or deleted under a compile type.
|
|---|
| I02621 - Always process version conflicts | Version conflicts were not signaled when the objects comes from development instead of being checked out from production.
This sometimes happens when developers import work that they have been doing on their private libraries, or when objects are received from a third party. Version conflicts are now checked on every move and checkout. |
|---|
| New CLI API's | We are moving all TD/OMS business logic into separate programs for our back-end modernization project. These APIs can also be called using a command with the same name. To access additional information about these APIs, please click on the link below. |
|---|
| I02614 - Check for logicals before transfer | Before transferring, all physical files are checked to ensure the absence of any unexpected dependent logical files. For more Information you can see CHKPFDEP documentation. |
|---|
| I02636 - Add 'Compare with production' action for solution | When a solution is selected in a Task, an action to "Compare with production" is added in the context menu. This is implemented to filter objects in *PRD environment in the application which compares the source of solution to one in production directly.
|
|---|
| I02681 - Display Objects witout target Check | If objects are attempted to be promoted then the objects which are missing from promotion due to the current target configuration are displayed for confirmation.
|
|---|
Web/VSCode issues/enhancements resolved
- I02688 - Database API - Wrong field is reported in error
- When two fields are added to the sorting part if the first field name is incorrect, the second field name is incorrectly reported as wrong, even though it is actually correct.
- I02669 - Compile Queue Issue
- If the object is already in the build queue, an incorrect message is returned.
- 583 - Issues when loading and saving sources
- When a source was changed on the backend, the web view would possibly open a cached version of the source. In addition, when a source was changed in the backend while the developer was editing on the web, the source was silently overwritten when the user saved it on the web.
- I02665 - Dashboard - Wrong data is passed back from the server
- In some scenarios, the Dashboard API did not return the anticipated response.
- I02668 - OCTO - Source saving issue
- When we delete the first row in the source member and save it, we end up losing the subsequent record following it.
GUI issues/enhancements resolved
- I02620 - Report output XLS, DOC and PPT are no longer working
- We have replaced these legacy output settings with XLSX, DOCX and PPTX renderers. You can find these settings in the TD/OMS Report Preferences
- I2149 - Fix layout of TD/OMS Teaming Route and Task selection dialogue
- The common dialogue now scales properly when resized and no longer blocks UI when routes are being fetched.
- I02600 - Fixed remote job monitor where entry count for any section can be 0 but could contain entries.
- Fixed the situation where expanding on a zero count entry would show all job entries.
- I02593 - Exception during transfer (checkout)
- An exception could be thrown when retrieving job information, handled this correctly if no job found.
- I02634 - Fixed exception on xref when showing hits for an IBMi location.
- Xref UI was not handling all IBMi type locations correctly, a location without and ending .LIB would cause an exception.
- I02617 - Updates for Xref UI
- Added help and hints on the simple search dialog. Removed warning message 'not Admin ...' in Preference page when user is not the Gravity admin user.
- I02657 - Fixed when XREF Responds incorrectly on open editor.
- If the active editor was an oas3 editor then the simple Xref query handler would throw an exception.
- I02660 - Changing a library to one that needs to be created fails in definitions (OMQCHGSL)
- Fixed a bug where changing a library of a sub-environment to one that needs to be created (but not copied from somewhere else) fails in the definitions.
- I02694 - Move solutions to other task does not reset error (GUI)
- Fixed a bug where the error from selecting the same task as a target was not cleared after selecting a correct target.
- I02547 - Change path and programmer fields in new task wizard
- The path and programmer fields of the new task wizard are converted from a combo box to open a dialog to select their value.
Server issues/enhancements resolved
- I02686 - Incorrect response returned by connectionList REST API
- Now we are getting a correct response from the connectionList API.
- I02679 - Add the OMQCHGCO and OMQCHGAI APIs to the OMSAPI menu
- OMQCHGCO and OMQCHGAI APIs have been added to the OMSAPI menu.
- I02654 - TimeFlash - Add events to the TimeFlash Mimix process
- Events were added to the TimeFlash process for the Mimix Promotor Engine.
- I02655 - TimeFlash Decrease delay in ready process
- The idling process delays for 30 seconds at a time. This is very long and it was made shorter (5 seconds).
- I02677 - OMERSV1 - URL field crash when multiple entries in OMAGP
- The OMQLINKPREFIX sysvar enables multiple levels for this variable (e.g., system and application). If there is an override on the application level, the OMERSV1 view crashes. This was fixed
- I02658 - Transfer messages are logged under OMS##/QSECOFR
- Sometimes, the job switches to QSECOFR. Log entries would appear in the system application if this is the case. The log entries will now be properly placed.
- T00380 - Add capability to return the target library and source file from the new object rest API.
- A new path '/location' has been added to the new object rest API to return the source and object library.
- I02685 - REST Spoolfile API
- The time to fetch spoolFile content is reduced.
- I02682 - Retrieve Database API issue with the response file name
- The filename in the Retrieve database API response should be "ObjectOMS" rather than "Object."
- I02661 - Wrong file name in OMDDI
- In the OMDDI file, "CreateObjectMonitorExtended" should be updated to "CreateMonitorExtended" for the OMCOMV1 file.
- I02662 - Retrieve Database API issue
- The Database API was not providing accurate results for IFS records.
- I02663 - Dashboard- Cursor getrecords is closed
- The dashboard API was encountering an error with the message "A cursor getrecords is closed."
- I02667 - Terminate OMQCHJD *SRVPGM & Module
- We've developed the job description API OMQCHGJD. Consequently, the *SRVPGM associated with OMQCHGJD is obsolete and not in use anymore.
- I02651 - TFROBJOMS doesn't work with the high sub-environment number
- Now the remote transfer can be done by having the library list seq# combination of less than and greater than 999.
- I02664 - Wrong authority for Fusion Pro CPP
- Fusion Pro Command processing programs are now authorized as PUBLIC *USE.
- I02659 - Solution points to second sub-environment
- The solution record was updated multiple times for the same object in multiple targets. The record is now only updated if it was not updated before.
- I02652 - Add object information to ACT0104 and ACT0105
- The object library, code and type information have been added to these message IDs.
- I02551 - STRFM - Branch creation issue
- When attempting to create a branch with the option CB for a task assigned to a different programmer, the branch was created, but it was not set in the task. Now a code 2 user can not create a branch for the task that was created by a code 3 user.
- I02646 - STRAIM - Attempt to write a duplicate record
- The duplicate record error has been resolved while attempting to add and modify an entry.
- I02552 - Location type copy issue
- A change has been added to return the correct location type.
- I02635 - Device Type is not copied when remote location override is created with API
- Now, when we create a distribution entry in the subenvironment the override is automatically copied with its device type.
- I02637 - Can not add a new job definition by copying
- The STRJDM (Job Description Maintenance) command with option 3 doesn't work as expected. It returns the message OMQC815.
- T00360 - Improve the source API
- We need to enhance the Enable functionality for opening and saving, Facilitate the opening and saving of IFS (Integrated File System), and Implement the capability to add to the build queue in the Rest Source API.
- I02435 - Skip the error schema from Transfer API
- If no errors are detected while using TransferAPI, we need to exclude the error schema from the response.
- I02429 - Create event for Source API.
- Events for source loading and source saving should be created within the Source API.
- 582 - Fail save is not detected in VSCode
- Octo doesn't save the source when the member is locked onto the green screen.
- I02619 - Version is not created correctly on import
- When importing objects from development, the object's version number was not correctly calculated if the object exists in an upstream application.
- I02639 - SETLIBLOMS crashes with more than 128 libraries in the compilation library list
- When more than 128 libraries are set in the compilation library list, the SETLIBLOMS command crashes. This command is used during compiles.
- I02645 - Version conflicts are not always created in related applications
- The version conflicts were not added when working with a double application. They were created when checking out from prod but not when loaded in the middle of the cycle.
- I02628 - OMQCHGTD - The topic name is not good.
- The event topics for the type code detail have been updated to "type/compile/detail/update."
- I02602 - OMQCHGTC - Incorrect data is being written.
- Now, the correct data is being written in the OMCOB file.
- I02596 - Add Filter on STRTCM command
- Now, the filter has been added to the STRTCM command.
- I02607 - Solution Rest API issue
- Now, we receive an accurate number of alternative texts when connecting IFS objects to the fix.
- I02619 - Version is not created correctly on import
- When an existing object is imported in the development environment (e.g., a new version has been received from a third party), then the version number could be incorrectly calculated if solution records only exist in exporting applications.
- I02605 - Not all registry definitions in STRRDM
- The missing registry settings OMQFLBCOPYTYPES and OMQDFTSRCFLEN have been added for the next milestone.
- I02480 - OMQCHGEVCP not accessible
- Authorization class *C2 has been added for OMQCHGEVCP; now, it is accessible.
- I02587 - OMQCHGTD Command Line API (Type Definitions)
- When the type is *COMPILE, the entered sequence value is ignored and automatically set to *ONLY (1). Similarly, When the command type is *ALL for a delete operation, the entered sequence value is ignored and automatically set to *ALL.
- I02604 - Switch of CL program logging in OMSJOBD (+SC +PC)
- Now, the logging for the CL program will be switched off to reduce the amount of useless log entries.
- I02594 - Update Type Code Detail API panel group
- The help text for *ONLY has been improved.
- I02558/I02632 - A record is added to the object file while creating a new object with a space before its name.
- Now, an object having space before its name can not be created.
- I02608 - Cursor GETCOUNT not open
- Whenever we execute the REST API, we consistently encounter the "Cursor GETCOUNT not open" message in the job log.
- I02610 - Select Fix OMX108 does not show *NEW status anymore
- When selecting option 31 for a solution from the solution list and subsequently pressing F4 to choose a task, the *NEW status no longer appears.
- I02584 - OMQCHGLB *UNLABEL
- The OMQCHGLB command with *UNLABEL action should not verify the object's presence in OMOBJ.
- I02583 - Type code maintenance issue
- Changing the type variant in STRTCM (Type Maintenance) should display the type code right from the start.
- I02611 - Duplicate key on OMCHCL1
- During the utilization of the REST API, the job log will not record the "A duplicate record key was found in member OMCHCL1" messages.
- T00377 - Clear Log File older than To Date - Add Options in Parameter TODATE
- It is enhanced to delete Logs older than last Week, 2 Weeks, 1 Month, 3 Months, 1 Year, 2 Years, and 5 Years by using options *1-WEEK, *2-WEEK, *1-MONTH, *3-MONTH, *1-YEAR, *2-YEAR, *5-YEAR respectively.
- I02603 - Duplicate record in OMOW3 when a dependent logical failed to recreate
- This has been fixed.
- T00366 - Add an option to delete all the processed event history.
- Now logs can be deleted for the last 1 Day to 99 Years, which has an option to include the event audit trail.
- I02615 - DLTAPPOMS command is not deleting a few file records
- When the application is deleted, some file records are not deleted.
- I02622 - OMQCHGFI - TASK/STATUS event is not added.
- In OMQCHGFI API, when a task is completed, the task/status event is also added.
- I02618 - OMQCHGEV - Trying to write the duplicate record.
- Now even if multiple events are hit simultaneously, duplicate records will not be written into the event file.
- I02609 - Indicator variable required.
- When invoking the REST API, the job log will not record the "Indicator variable required" messages.
- 574 - Promote Solution Failed Environment *ANY not Found in Application YADAN
- Promotion fails to occur when the environment is set to *ANY.
- I02623 - MEMLEAK in OMQRTO01M
- While executing the transfer API call sometimes we see a memory leak message in the job log.
- I02629 - OMQCHGEV - Use unlock keyword instead of out
- Unlock keyword has been used to remove the lock from the data area which takes less time now.
- I02624 - Cursor C03 not open.
- During the utilization of the REST API, the job log will not record the "Cursor C03 not open" messages.
- I02631 - Action group on SL is wrongly executed for detail
- Selecting an action group on SL with Object detail *BLANK + should be executed.
- I02633 - Issue in OMSYSUTIL service program
- Unable to get the message due to the absence of content in the second-level message.
- I02638 - SSHTransfer distribution processing was sending in an incorrect value for the remote job monitor processing
- The remote job monitor now shows the remote job's receive, start an end time.
- I02644 - SSHTransfer server does not log the exception of a file write failure.
- Logging information was insufficient without the exception.
OpenAPI Generator Enhancements
Please re-install the generator with INZOMSSRV SERVICE(*APIRESTGEN)
==OpenAPI Smaller Issues resolved==
In case you do not want to wait for the official milestone build, you may install the nightly builds.
New and Noteworthy in TD/OMS V16 Milestone 2
| New Pre-Transfer Checks | We have created two new transfer checks. They are disabled by default.
More information:
|
|---|
| New REST API's | We have developed a set of new REST APIs. To access additional information about these APIs, please click on the link below.
|
|---|
| New CLI API's | We are moving all TD/OMS business logic into separate programs for our back-end modernization project. These APIs can also be called using a command with the same name. To access additional information about these APIs, please click on the link below. |
|---|
| E243 - Connect and checkout in one go | Now when an object is connected to a task with direct connect, it is also "checked out" to the development environment from production so work can be done immediately to it. |
|---|
| I02508 - Update Genexus interface Genexus 18 including RPG development | Work has been done to update the Genexus interface to work with version 18 of Genexus. For Genexus RPG development we have support for the interactive en non-interactive mode (of which the last is driven by the distribution of an XPZ change-file). For this milestone the non-interactive mode is beta. |
|---|
| TDOMS.I2145 XREF ui updates | Major update on working with Xref locations in the UI. Location properties have now been separated from the location URL and can be edited separately. Also there is added functionality to more easily work with locations, for example move, copy and view locations.
|
|---|
| T00372 - Support types in the definitions | Types have been added in the definitions view. Now compilation or a location types can be viewed, created, copied, changed or deleted under a host.
|
|---|
| I02505 - Sub-environment filters in definitions | Sub-Environment filters have been added in the definitions view. Due to the possibility of having hundreds, or even thousands of sub-environments, filters are needed in order to find the ones required. If the results of a filter are more than 50, then they are grouped into folders of 50, otherwise they are displayed immediately.
|
|---|
| I02539 - Processing sequence now also considers the IFS file extension | Use Case: To clear the cache of a web server, a trick can be used to fetch an HTML page by adding a dummy variable to the path. If the variable changes, the web server reloads the HTML page instead of serving it from its cache, including the CSS and JS. This implies the CSS and JS should be placed in the directory before the HTML file. |
|---|
| I02479 - Remote libraries not cleaned up | When a remote job fails, the cleanup should still be done. There is too much data stuck on the remote machines when the transfers fail end the end users should not be burdened with this. Now all files are always cleaned up after a successful deployment or after a successful fallback.
In case some additional investigation must be done; the strategy is to keep remote files when the debugging level is below INFO. Debugging can be switched on in the System Definition function (STRSD). |
|---|
| 02010 - Millions of log records | In a situation where the 5250 screen is disconnected due to a connection issue AND the user was on the OMQUSIOB, OMQUSIFI or OMQUSISO program, the program would loop and produce millions of log records.
Sysadmins can run this query on the OMLOG file. It shows the number of job entries per job. Anything above 10000 records is suspect and should be investigated for repeating records with the CPF6A0F message id and potentially be removed. SELECT ogjob#, ogjobn, ogusid, COUNT(*) as count FROM omlog GROUP BY ogjob#, ogjobn, ogusid ORDER BY count desc
|
|---|
| I02574 - Accept source change date issue | When accepting a source change date conflict, it would sometimes still fail during the transfer. This has been fixed.
In addition, accepting a source change date conflict is now allowed for developers when leaving the development environment. We are still debating this rule and we will make changes here in future releases. |
|---|
| I02497 - OMQCHGCL - unable to change the solution type of the object in the connection list. | The OMQCHGCL command does not contain the action code *CHANGE due to which solution type of the object can not be changed. Now we have introduced new action code *CHANGE to resolve this issue.For more information you can see OMQCHGCL documentation. |
|---|
| 02007 - Cleanup savefiles older than | The CLRFBSOMS command had a fixed date parameter. Now it has been changed to accept *1-WEEK, *2-WEEK, *1-MONTH and *3-MONTH along with pre existing *ALL and Date. For more Information you can see CLRFBSOMS documentation. |
|---|
GUI issues/enhancements resolved
- I02475 - Clips appear multiple times in the menu
- The Clips icon would occur multiple times in the work management menu for RDi 9.6
- I02545 - TimeFlash view does not refresh correctly
- We fixed an issue where the TimeFlash view would not refresh correctly when a Task was selected.
- I02538 - Branch API should only work in a *PATH environment.
- The cleanup and creation of BRANCH library lists should only be done when the environment is a *PATH environment. This allows you to add in a mixed *USRPRF and *PATH environment by adding the path to the user profile library list in an event. This should then not be deleted when the branch is deleted.
- I02523 - Recalculate solution records init fails
- When receiving a remote distribution, a flag was initialized on every processing step, causing the re-calculation of the source location to be skipped on the remote.
- I02511 - Member is not labeled when created from a template with a label
- Creating a "new object template" for a member with labels is possible. The labels were not applied when the member was created.
- I02475 Clips appear multiple times in the menu
- In RDi 9.6 the clips toolbar menu is not correctly cleaned up. This showed the clips menu every time the work management view was activated.
- I02462 - Doubleclick on details gives an error
- Fixed an issue where double-clicking a detail to open it was failing with an error dialog.
- I02465 - Missing options for unattended install RCP/RDi installers
- The Azure or Birt reporting option were missing from the RCP/RDi 9.8 TD/OMS client installers.
- 01979 - Press F5 to refresh sometimes does not react.
- The refresh logic has been relaxed. F5 can now be pressed multiple times without the tree collapsing. In addition, the allowed time between refresh has been decreased from 5 seconds to 0.5 seconds.
- I02397 - Transfer in the GUI works without FP license
- Rectified the issue by adding a check to validate the FP licence to transfer, promote or checkout in GUI.
- 01866 - User ID may not be lowercase in user option
- In TD/OMS User Option, the User ID is restricted to be in Upper Case now when it is edited.
- E203 - Hide members in detail view associated with database files
- In TD/OMS Details View, a new icon is tagged along to hide data members. This is implemented to add the ability to filter the details view and not display details that are data members of objects. For example, if a database file (not SRCPF) has one or more members, those all will not be displayed in the details view now. The icon is selected by default along with hide sources when the detail view is displayed.
- 01980 - Source is closed when another object in the task is checked out
- Resolved the issue where two files in the task were open in the editor and a third object was being promoted or checked out. The process closed the two files but they should not be closed.
- 01573 - Component filter cannot be deleted
- The issue related to the Component Filter in the toolbar of TD/OMS Components view was resolved where the user was not able to delete the filter.
- 01775 - Connect alternative as merged is missing in the gui
- When appropriate the connect alternative as merged option is now displayed during solution conflict handling.
- I02488 - Ratification for TST is shown on a higher level
- Fixed a bug where sometimes the ratifications shown in an environment also showed ratifications from the previous environment.
- I02503 - Retry upon warning is missing on definitions
- An extra "Ignore Warnings" field now exists in the job descriptions, directory and route entities when they are being created or changed. This gives the option to ignore warnings if desired (default is No).
- I02525 - Issue in comparing with object without any source
- Handled an exception where two or more solutions or objects in tasks or components view are compared to each other and any of them is without a source.
- I02170 - Exception in details view when filter on task and deleted options are both selected
- Resolved the runtime exception thrown when both filter on task and show deleted objects are pressed in the details view.
- I02529 - Edit filter action is allowed when many filters are selected
- Restricted the edit filter action which must not be allowed when more than one filter is selected.
- I02527 - Persist a reference to a user provided java trust-store
- A trust-store required for certificate verification can be added to Remain's certificate directory and be used by Remain's certificate manager (see EWM:2 – Secured Communications)
- I02528 - MIW IBMi connection not using a secure connection when required
- A MIW related IBMi connection will now be secure if the IBMi server in TD/OMS is configured for Secure Connections.
- I02534 - GUI Definitions
- After application create no environments can be added
- Fixed a bug when a new application is being created and no action could be done with it afterwards because it wasn't loaded in the TD/OMS GUI yet.
- I02547 - Change path and programmer fields in new task wizard
- The path and programmer fields of the new task wizard have been converted from a combo box to open a dialog to select their value due to the big number of values that they might have, thus slowing the wizard.
- I02531 - Move solutions to other task is not available
- Fixed a bug where the move solutions action was not present when many solutions are selected.
- I02537 - GUI Definitions Remote location override cannot be deleted
- Fixed a bug where the wrong error message was shown when an application remote location could not be deleted because it was in use as a distribution entry.
- I02535 - GUI Definitions Issues with directory creation
- Fixed a bug where a directory could not be created.
- I02569 - GUI is leaking Windows resources
- Fixed a Windows resource leak in the Transfer Wizard
- I02550 - From Compare revisions it is now possible to checkout an archived stream file directly to a eclipse project.
- This support was added to aid those who want to use the archive as like a versioned SCM repository.
- I02572 - New object of type member can't be created
- Fixed a bug where a new object of type member can't be created.
- I02560 - OMQCHGSO logs exceptions on close of API.
- Fixed the call on the close of the OMQCHGSO API.
- I02573 - API PCML call unexpectedly disconnecting.
- Processing multiple PCML calls in parallel could invoke a currently running PCML call to be disconnected, this has been fixed.
- I02580 - Optimize Workmanagement perspective tree.
- Work has been to make the Workmanagement perspective tree respond more quickly when refreshing and selecting a menu option from a tree item.
- I02581 - Minimal UI blocking if host goes offline.
- Work has been done to detect and minimize UI freeze when the connection is lost when working with a system.
- T00374 - Make the change solution type action available for many solutions
- Now the change solution type action is available when many solutions are selected.
Server issues/enhancements resolved
- I02592 - Solution REST API issue.
- Now we can disconnect members from the task.
- I02586 - Add new events.
- The events have been added in the OMC017/OMQCHGTC, OMC020/OMQCHGTD and OMO021/OMQCHGCD.
- I02540 - Remote Location API issue.
- Now an address is added at the sub-environment level and does not exist at the application level.
- I02557 - Solution conflict resolution must be part of the solution rest API.
- Now solution conflict resolution is part of solution rest API.
- I02477 - Spelling error in Compile Queue API.
- Now the spelling is corrected.
- I02591 - Table API Error Message Conflict.
- Now we return only 1 message field for every message.
- I02519 - Unable to view processed events in the subscriber maintenance screen.
- Now we can view the processed events in the subscriber maintenance screen.
- I02445 - OMQCHGSR - Restrict the actions add, change, and delete for the registry.
- Now the actions are restricted for the OMSSECADM group profile.
- I02459 - Pointer or parameter error for Program OMX108.
- Now we don't get the pointer or parameter error when we call the OMX108 program.
- I02590 - Members are not getting deleted from the connection list
- Now the members are also deleted from the connection list.
- I02567 - Compilation library *LIBS
- Now, you can add more than 50 libraries and a maximum of 248 libraries using the *LIBS keyword.
- I02589 - REST API - Source API issue
- When an IFS path with a blank application name is provided, it should return the IFS source data instead of generating an error.
- I02565 - Library list not set for second sub-environment
- On promote compilation library list for the second sub-environment is identical to the first sub-environment.
- I02579 - OMQUSRDTALIB not in STRRDM
- The missing registry setting (OMQUSRDTALIB) has been added for the next milestone.
- I02568 - Add the APIs to the OMSAPI menu.
- The OMQCHGTC, OMQCHGTD, OMQCHGCR, and OMQCHGCD APIs have been added to the OMSAPI menu within the application section.
- I02576 - Label API delete does not check on usage in object templates
- This caused a possible label deletion while it was still in use. The label delete error message has been updated to indicate where the label has been used.
- I02577 - OMQCHGSL API Does not fill BDLOLI correctly
- When using the API to add a library to a subenvironment with a specific type resulted in an incorrect value in one of the fields. This caused the library to be excluded from several places in TD/OMS like compilation library lists, filling, and target selection.
- I02514 - DSPLOGOMS option 8 display section no longer works.
- The option 8 display section in DSPLOGOMS no longer functions correctly; it indefinitely hangs.
- I02517 - Object should not be added to the connection list if it is already connected to the task.
- An object should not be added to the connection list if it already has a connection to the task.
- I02518 - Override Active solution in production env should not close the other solution
- Override Active solution in a production environment should not close the other solution.
- I02515 - Messages VRS0001, VRS0002 and VRS0003 must be suppressed by events
- Messages VRS0001, VRS0002, and VRS0003 are now suppressed by events.
- 499 - Sorting Inconsistency on Fetch Ratifications History Request with Date and Time Fields
- When executing a "Fetch Ratifications History" request with sorting by date and time fields, the returned ratifications seem to be incorrectly sorted.
- I02530 - Source API. The source change date is changed for all records when saving
- The date of source change for a line should only be updated when the source is modified during the save process from OCTO.
- I02542 - Retrieve Database API issue
- The Retrieve API is experiencing an error because the specified length or start position falls outside the permissible range for the string operation.
- I02555 - System ratification groups and members are not read
- The database API does not return system ratification groups and members. The system groups have a blank application code and should not be stopped by the database API.
- I02522 - The target source library for *COMPILE solutions issue
- The target source library for *COMPILE solutions on the remote library list is filled with the branch library but it should be filled with the production library.
- 495 - Confusing Line Number in Source File API Error Message
- When the message retrieved from the Source File API exceeds the maximum line length, the error message inaccurately indicates a confusing line number. Rather than specifying the correct line number '5', the message erroneously references '.50', confusing for developers in pinpointing the actual location of the issue in the source code.
- I02549 - OMQCHGCL always connects with rules
- Now, OMQCHGCL API will add the object to the connection list with and without rules.
- 01997 - Lots of messages "OMSEXITADM not found".
- Some user profile checking was leading to a lot of confusing messages in the log. These messages are now suppressed.
- I02548 - Sourcefiles should not be created with CCSID 65535
- Sourcefiles are by default created with CSSID 65535. This causes problems when using sourcefiles in VSCode and Octo
- 01984 - OMQPRTFI For Fixes that have no reason code
- We could not produce a list of tasks that were not closed by a reason code but through the normal deployment process. This has been fixed by adding *NONE to the Reason Code options in the OMQPRTFI command.
- T00346 - Call OMQCHGEN API from the Environment maintenance screen
- Now, OMQCHGEN API is used within the environment maintenance screen.
- I02472 - Rename Dump to Archive
- Historically, we have referred to the source archives as "Source Dumps". We have renamed all "Dumped Sources" references to "Archived Sources." All green screen functions and context-sensitive help have been updated.
- I02411 - OMQCHGRT - Changing the recursive route to *YES does not work properly.
- The recursive route flag will no longer be turned to '*YES' when a route code is created with the recursive route flag set to '*NO' and assigned a directory using the OMQCHGID API, choosing a parent directory already associated with a different route code.
- I02444 - OMQCHGEN - Issues with Environment code and description field
- The API no longer crashes when a blank environment code is passed, and it now correctly handles empty descriptions in the change action code.
- I02452 - User option check value
- A change has been made to display the 'CHK' value in the OMX20201 screen.
- I02467 - Issue in INZOMSSRV command
- Resolved the following problem when executing the command "INZOMSSRV SERVICE(*APIRESTGEN)": "Pattern not allowed in path name directory."
- I02478 - STRJDM not working with CCSID 65535
- When the job CCSID is set to 65535, job descriptions are not displayed.
- I02484 - Member version number is not taken from previous applications
- When the object file is loaded, the member version is not taken from the previous application but instead set to a wrong value.
- I02482 - Event filter documentation AND/OR
- Now, the filtering of events is documented with the AND condition, as well as the use of regular expressions (regex).
- I02513 - Task API issues
- Now, the long description has been added for ratification. For more information, you can see the REST Task API documentation.
- I02460 - New registry view and file is required
- A new OMXRegistryExtended is required in the GUI (and an equivalent view in the backend) that will join the existing OMXRegistry (OMAGP) and the new OMGPD file which doesn't exist in the GUI yet.
- I02458 - Logging issue
- When utilizing TRACE and DEBUG levels, if the program name is defined within the OMLOGLVL data area, extra verification is added to ensure that the program name provided as a parameter does not coincide with the program indicated in the ONLOGLVL data area. If this condition is met, the logging process is disregarded.
- I02446 - Comment should not be copied
- Now when you copy the application, it won't include comments on tasks, objects, requests, solutions, and details.
- I02442 - STROCM - Modify the selection values *AUTHORIZED and *UNAUTHORIZED
- The selection values *AUTHORIZED and *UNAUTHORIZED have been updated to 0=*ALL, 1=*AUTHORIZED, and 2=*UNAUTHORIZED.
- I02489 - The description of a job description can't be changed
- Now the description of a job description is allowed to change even when it's not on the host level.
- I02490 - The type of job description is allowed to change even when there are overrides
- Now the job description is not allowed to be changed from *TRANSFER to *OTHER on the host level when there are overrides on the lower level.
- I02495 - Job Description API has wrong field names
- Now errors are reflecting the correct fields in the TD/OMS definitions.
- I02510 - Omxfercd client-deployment failing on password decryption
- Due to an issue with a 3rd party library, decrypting passwords, contained in a configuration property file, could fail. The issue was fixed with an update of the library and re-encrypting the password.
- I02509 - Connection rule detail can not be deleted
- A validation was there which has been removed for the delete case, to resolve this issue.
- I02516 - Subscriber filter variable must always start with &
- A validation has been added to check if the variable starts with & or no.
- I02553 - REST API - Retrieve the solution conflicts text details
- Added logic into the solution API to retrieve the text details of solution conflicts based on the "messageId."
- I02588 - Override issue in SBSVAROMS command
- We're retaining the override in the Replace Object (OMX307C1) program.
- I02443 - InvalidCharacterError issue in Source API
- When attempting to use the source API for certain members, we encounter the "InvalidCharacterError: Failed to execute 'atob' on 'Window': The string to be decoded is not correctly encoded" error. Also, the source type is not returning correctly.
OpenAPI Generator Enhancements
Please re-install the generator with INZOMSSRV SERVICE(*APIRESTGEN)
| I02454 - Introduce logging in to the JWT. | We've implemented JWT logging to monitor errors in Rest API token validation.
|
|---|
OpenAPI Smaller Issues resolved
- I02464 - Memory leak issue in rest API generated code
- Addressed the memory leak problem in the rest API generator when making API calls.
- I02466 - Transfer API Issue
- Failure to provide the transfer number in the "/execute" method results in an incorrect message being returned.
- I02470 - The message of the memory leak should be sent to the job of the CGI program.
- Previously, we sent the memory leak message to the QSYSOPR queue. However, we have now updated the process to report memory leak issues directly in the current CGI job.
- I02471 - Fix memory leak issue in the existing generated Rest API
- Resolved the memory leak issue in the previously generated Rest API.
- I02476 - REST - Generate Client Issue
- The "Generate Client" feature produces a duplicate sub-procedure named pMessages in the M member when creating programs for the REST API.
- I02473 - OCTO - Source API issues
- Ensure that the API includes passing the maximum line length, indicating 0 for stream files. Avoid assuming all request fields are correctly filled; account for scenarios where the short object code is provided without the IFS path. In such cases, the IFS path retrieval from the request may not be accurate when writing the event.
- I02483 - Rest API - Global variable definition issue
- The definition of the global variable "logMessage" is absent in the generated source code from the REST API generator.
- 473 - Improve Checkout in DEV Environment with Clearer API Errors
- Encountering an unclear error message from the API during the checkout process in the DEV environment poses challenges for effective troubleshooting and understanding of the issue. The expected behavior is that users should receive explicit and meaningful error messages from the API, offering insights into the nature of the problem encountered during the checkout process.
- I02502 - REST API - Declare the variable as a pointer when its length exceeds 65535.
- If the length of the variable exceeds 65535 and the type is "application/json," the field should be declared as a pointer.
In case you do not want to wait for the official milestone build, you may install the nightly builds.
New and Noteworthy in TD/OMS V16 Milestone 1
| I02419 - Provide YouTube Integration | We have integrated instructional videos in our RDi views. These menus are dynamically created. When we add a new video, it will be available when the RDi is restarted. You can augment this menu with your own documentation links. Let us know when you want to try this.
|
|---|
| I02438 - Remove TD/OMS from all view titles | The TD/OMS views are no longer prefixed with 'TD/OMS' this information is redundant and may obscure the readability of the UI.
|
|---|
| I02393 - Additional security refinements | It is not always desirable that administrators can define their and other people's authority or that developers can execute code on the production machine through TD/OMS. A couple of extra measurements are implemented to control who can change security settings inside TD/OMS and who can define exit programs.
|
|---|
| I02416 - Analytics Performance Indicators for Branch | We now have a KPI chart for branches. If a developer has more than five open branches or more than one closed branch, the chart appears on the warning section of the TD/OMS Analytics web page. It is advised to delete closed branches immediately because every branch contains temporary development and test libraries. Branch libraries should be cleaned up when the task is implemented or abandoned.
|
|---|
| T00338 - Upgrade the definitions view | The existing definitions view in the definitions perspective has been enhanced to support even more definition related entities and actions further eliminating the need to use the green screen. Below there is a brief description of what has been added. In the future more entities and their actions will be supported.
|
|---|
| Better support for data areas. | We now have a better dialog to create, edit and view data areas. A new data area can be created using New / Object / Data Area on the task level. To view or edit a data area, just double-click it like you would edit a source.
|
|---|
| 01961 - Error view is not opened after compile. | The direct compile action has been enhanced. You can now open the Error View to see the event log even if the compile was successful.
|
|---|
| T00360 - Improve the source API | We have improved the Rest Source API to enable opening and saving and handling IFS files. For more information, you can see the REST Source API documentation. |
|---|
| I02368 - REST API - Add action Transfer in Transfer Object API | The Transfer action has been added to the Transfer Object API. For more information, you can see the REST Transfer Objects API documentation. |
|---|
| I02358 - REST Task API - Complete the remaining actions | The Remaining actions Connect, Disconnect, Complete, Ratify, and Status have been completed. For more information, you can see the REST Task API documentation. |
|---|
| T00357 - Create a new command to archive the object (ARCOBJOMS) | A new command has been introduced to archive the source of the objects. The documentation is here. |
|---|
| New Registry settings | We introduced a couple of new registry settings to tweak the behavior of TDOMS. Please check the end of the list in the Predefined Registry Settings |
|---|
| I02365 - Event Filters | We have successfully implemented event filtering based on specific criteria. This should help you better control and manage event triggers. For more information, you can see the TDOMS Event System documentation. |
|---|
| New Event Topics | Two new event topics have been introduced to enable you to hook into the new object creation process. When a new object or member is created, the topics object/new or object/detail/new can be received by event subscribers. How the eventing feature works is described in the TDOMS Event System documentation. |
|---|
| New Action in BRANCH API | We've added a new action, *SETLIBL, to the branch API. With this action, you can add the branch library to the beginning of the library list. To tailor this functionality to your needs, you have the option to modify the OMSETLIBB user exit program. For more information about the branch API, you can see the BRANCH API documentation. |
|---|
| OMQRTVLI API | We've created a new API, OMQRTVLI which returns the libraries for a path. For more information you can see the OMQRTVLI API documentation here. |
|---|
| 01925 - Massage WebSmart PDW | We made a function to set the information in the WebSmart PDW files after checkout.
|
|---|
GUI issues/enhancements resolved
- I02413 - An already connected IFS file cannot be connected to another task in the GUI
- This has been solved.
- I02415 - Default Filters
- A default set of filters is automatically created for new users. Filters are created for the Task, Branch, Request, and Application nodes.
- I02404 - Error on disconnect solution
- Sometimes, an error could occur when disconnecting an object from a task.
- I02277 - Reserved solution shows as *MERGED in GUI
- Earlier Reserved solutions were being shown as *MERGED in GUI.
Server issues/enhancements resolved
- I02439 - Maintain Create Command - Action add is not working correctly
- The "Authorized by user" field is no longer populated incorrectly when attempting to add the compile override command.
- I02436 - The "Disconnect" action in the Solution Rest API is ineffective for IFS objects.
- The "Disconnect" action in the Solution Rest API is now working for IFS objects also.
- I02425 - Give the message in the OMSLOG when the completion is executed
- Now, A message will be logged When the completion is executed for an unauthorized compile override command.
- I02408 - The "Authorized by user" flag should be removed
- Now, the "Authorized by user" flag will be removed if there has been an update to the compile override command.
- T00362 - Select Task window
- The filtering has been updated, and now additional values have been permitted for data filtering. Furthermore, a new parameter field has been added.
- I02359 - REST Solution API- Complete the remaining actions
- Remaining action codes Change, Move, Lock, and Unlock are completed.
- I02392 - The OMQCHGFI API with the action *COMPLETE should trigger a branch status recalculation
- The status is being re-calculated when we perform action *COMPLETE for OMQCHGFI API.
- T00364 - ADD new field in OMFLT file
- We have added one field LTSDTA in the file OMFLT and compiled all its dependencies.
- I01401 - Fill object file changes source location in development
- The STRFOF for the development environment changes the source location to the production environment for objects for which the source in development has been changed but the object has not been compiled yet. A change has been introduced to stop the source location from being changed.
- I02437 - The Connection List Rest API does not work
- The functionality of the Connection List Rest API has been enhanced to ensure seamless operation. The improvements include Case sensitivity Correction for the Object code field, Integration of connection rules and error message enhancement.
- I02424 - The processing method can be changed
- The Fix processing allows changing the processing method value when the BATCHONLY registry key value is set to 1. A change is added to stop the processing method from getting editable when the registry is ON.
- I02423 - ARCOBJOMS - Refinements
- Command was throwing dump in a few cases, so it has been refined. Also, a new field 'Force' has been introduced to the command interface which will help to archive the source even if there is no update in the source.
- I02410 - OMQCHGUA - Add OMSSECADM security logic for environment security.
- OMSSECADM security logic has been added for environment security in OMQCHGUA API.
- I02433 - Make TD/OMS services installable from an IASP
- When TD/OMS is installed on an IASP, the Java services cannot be installed. We now consider the IASP when installing the Java services.
- I02420 - BRANCH - The *SELECT value must be valid for the *SETLIBL action only
- The *SELECT value is now valid exclusively for the *SETLIBL action.
- I02406 - OMQCHGRT - Incorrect field name
- For the Archive Location field, the name was returned as ifsDirectoryCode, but now it has been updated to 'archive location'.
- I02405 - OMQCHGID - Two error messages are displayed for one field
- We have eliminated the unnecessary error message, leaving only the relevant one: "No relative path allowed" when an incorrect directory name is provided.
- I02403 - BRANCH - Action *SETLIBL is not working as expected
- The pop-up window will no longer appear when specifying the branch code.
- Leaving the application, branch, and environment code fields blank is no longer possible.
- I02401 - Delete duplicate fields from programs that are already present in OMQCHGFIDS data structure.
- OMQCHGFIDS has been modified. New fields have been added but those fields are available in several other programs too. So while recompiling those programs, they throw errors. Now those fields have been removed from the required programs.
- I02400 - OMQCHGEN - Add OMSSECADM security logic
- The ratification can be added or updated only by a code 3 user (*ADMIN) who is part of the OMSSECADM group profile.
- I02399 - OMQCHGUA - Add OMSSECADM security logic
- If user OMSSECADM exists then only users belonging to this group are allowed to security-related functions. An application manager who is part of the OMSSECADM group profile can only authorize another user as an application manager.
- I02395 - STROCM - Compile overrides can now be authorized
- Option 1 has been introduced to grant authorization for the record within the Object Compile Maintenance screen. The "Authorized by User" field is now included in the displayed list as intended. See the TDOMS Security document for more information.
- T00358 - REST Request API - Complete the remaining actions.
- Remaining action codes Connect, Disconnect, Complete, Ratify, and Status are completed.
- I02394 - Issue in REST Connection List API
- IFS Object path is converted from Lower to Upper Case, which is incorrect. A change has been added to stop the case conversion.
- I02389 - Object Type and Attribute array length is incorrect in OMQCHGSL API
- Internal array length has been decreased from 25 to 15 and also return field name has been changed from 'objectType' to 'objectTypeArray'.
- I02371 - Subscriber Processed Events maintenance program is encountering a dump
- The Subscriber Processed Events maintenance program no longer encounters a dump when selecting option 8 on the screen.
- I02385 - OMQCHGSO performs the action *CHANGE even with the wrong values.
- Action *CHANGE for OMQCHGSO API now throws an error in case of wrong values.
- I02363 - In the OMQCHGRL API, the application address gets deleted regardless of whether it has been used at the sub-env level.
- The application address will not be deleted if it has been used at the sub-environment level.
- I02318 - Terminate Solution Check
- The terminate solution check verifies relationships in the target and higher environments, ensuring comprehensive validation.
- I02369 - OMQCHGID - Action delete is not working correctly
- Deleting a directory will no longer accidentally delete the wrong records, ensuring data safety.
- I02362 - OMQCHGFI - Action disconnect is not working correctly
- Action disconnect is now working correctly when trying to disconnect the fix from the requests using request code *ALL.
- I02357 - OMQCHGAP - Ratification groups are not copied
- When copying an application, the ratification groups are also copied.
- I02387 - New IFS file does not work for a *NEW task
- When a new IFS file was added to a *NEW task, the routes would not be visible. This has been resolved.
- I02349 - OMQCHGOB gives strange values in the return message
- When we run OMQCHGOB ACTC(*JOBREL) JOB(*ALL) it gives the strange values in return message.
- I02364 - For target selection, use the label of the message file or file
- Before a message or member is put in the selection engine, we fetch the label from the message or member. If the message or member does not have a label, the label should be retrieved from the parent object.
- I02370 - The build queue process is not functioning properly
- An object without a compile command is added to the build queue if we select more than one object to add to the build queue. Also, the first object should be valid to add to the build queue.
- I02368 - REST API - Add action Transfer in Transfer Object API
- We have introduced the Transfer action in Transfer Object API.
- I02390 - Update Version for upstream application
- We have introduced the functionality to update the version for the upstream application.
- 345 - Task search no longer works
- The task search and/or has been changed and now the search no longer works in the Retrieve database API.
- I02432 - The transfer API fails to return the correct response.
- The transfer API was unable to provide the correct response due to issues with processing the details of the solution.
- I02422 - The source API fails to return the correct response
- When empty results are expected or the source is not found, the source API fails to deliver the appropriate response.
- I02407 - The correct type code is not returned.
- The correct type code is not returned for a member and the message ID when they are associated with multiple labels.
OpenAPI Smaller Issues resolved
- I02367 - The response is incorrect for the transfer object API.
- Our response consists of a string, but we need to modify it to create an object that includes the response as a string.
- I02409 - Memory problem encountered in generated REST API.
- When we transfer a value from a base pointer to another pointer and deallocate the base pointer's memory, the value in the other pointer also becomes invalidated.