APAR status
Closed as program error.
Error description
In IBM Developer for z/OS - IDz - v14.1.7, opening Menu manager preferences shows the first menu available instead of the previously selected one when duplicate names exist. Steps to reproduce the problem: - create a menu manager file for datasets in c:\tmp\menumanager.xml with a menu named MyMenu - copy it into c:\tmp2\menumanager.xml and import this copy into IDz menu manager preferences as Data set menus - On IDz preferences Menu Manager > Menu Selection, select context MVS Files in Remote Systems view and Default Dataset Menus is set to MyMenu c:\tmp2\menumanager.xml (first on the list is MyMenu c:\tmp\menumanager.xml) - click Apply and OK - reopen the Preferences dialog and "Default Dataset Menus" is now set to MyMenu c:\tmp\menumanager.xml (first one on the list) instead of MyMenu c:\tmp2\menumanager.xml (second choice on the list that was previously selected).
Local fix
There is no known workaround at this time
Problem summary
This problem occurs when there are multiple menus with the same ID in a workspace. In this specific case, the user created a new Menu Manager file that contains a custom menu. The user then copied the file into a different directory, and imported the copied file. When default and base menus were loaded, IDz only used the ID to find and load the menus that were specified by the user. Finding the menus using only the ID caused issues when multiple menus with the same ID existed, since IDz oftentimes found the incorrect menu.
Problem conclusion
A menu's ID is not enough to uniquely identify the menu, since other menus with the same ID may exist. However, the combination of a menu's ID and file does uniquely identify it. So, both the ID and file must be used to find and load the correct default/base menu that the user selected.
Temporary fix
Comments
APAR Information
APAR number
PH19373
Reported component name
DEV FOR Z/OS
Reported component ID
5724T0700
Reported release
E10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-11-20
Closed date
2020-05-15
Last modified date
2020-05-15
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
DEV FOR Z/OS
Fixed component ID
5724T0700
Applicable component levels
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSJK49","label":"IBM Developer for z Systems"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
27 October 2020