IC89146: STERLING CONTROL CENTER HAS ISSUES WITH USING BRAZILIAN CHARACTERS IN A SLC NAME ON A WINDOWS PLATFORM
Closed as program error.
The console allowed me to add SLC name with Brazilian characters as a wildcard SLC. However, once added, the SLC name displayed differently. I believe this is due to the Brazilian special characters. I tried to remove the SLC through the console, but received an error. I had to manually remove the xml from the folder and remove the name from the wildcard slc ordering text file.
STRRTC - 360345 SF / SF Circumvention: None
Customer applied the fix and it works now.
The fix will be part of the next maintenance release and on other releases.
Description of issue: After a SLC was created from the console, some of the characters in the XML file were not encoded properly. The user was unable to edit the SLC properties, receiving the following error message: CSLC095E Group file does not exist. Additionally. the engine would not startup, due to the bad encoding, until after the XML file was manually deleted from the slc\group folder.. This issue was specific to a windows environment, which was running Control Center as a started service (not started via runEngine.bat) Description of fix: Modified file runEngine$.lax to include file encoding of UTF-8. (i.e. added property: "-Dfile.encoding=UTF-8"). This will ensure that UTF-8 file encoding is used when the product is run as a started service in Windows environments.
Fix described will be the permanent fix
Reported component name
STR CONTROL CEN
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
STR CONTROL CEN
Fixed component ID
Applicable component levels