We have been unable to exactly recreate either issue in any environment configured with either English or Spanish (LCLCCSID=284) regional settings. However, any attempts to browse the problem component here does result in the BrowseComponentResults method returning a null response .
, which causes the Error 500 messages to be issued for certain function in the ZMF for Eclipse client. A fix for this issue is currently scheduled for ZMF for Eclipse \ ZMF Web Services 8.2 patch 2.
If customers fail to do this and attempt to access a ZMF 8.1.2 subsystem using an earlier version of the ZMF4CL client then problems will be encountered. This is regardless of whether or not the web services have been upgraded to an 8.1.2+ level.
In the interim, the obvious workaround is to not imbed such non-display characters within component code if at all possible. The same issue applies in relation to ChangeMan ZMF web service requests.
- the ChangeMan ZMF Client Pack, including both the ChangeMan ZDD and ChangeMan ZMF for Eclipse (ZMF4ECL) products. - any Serena-supplied or ‘homegrown’ solutions that utilise the native ChangeMan ZMF web services , the ‘ZMF Connector’ web services (a.k.a. the ‘ARM’, ‘RLM’, 'RC', 'SDA' and ‘Mainframe Connector’ web services ) or the ChangeMan ZDD API. - Comparex customers that utilise Unicode facilities and options.
