ORN:V16.0 Milestone 3
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 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)