IBM Z Software
This portal is to open public enhancement requests against IBM Z Software products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Development Tooling
Product - IBM Fault Analyzer
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Enterprise Tooling
Product - IBM Fault Analyzer
The following response was added to this RFE back in May however I believe the absence of the #publish tag prevented the update from flowing back to the developerworks system. I apologize for this. Please review the following response and let us know the outcome.
Adrian Simcock
Steps required:
1.Determine which specific code page the single-byte Katakana characters belong to
2. Find the locale name that matches this code page
3. Set this locale name inside the Fault Analyzer "LOCALE()" option file
4. Check whether the minidump values are displayed correctly
Notes:
We believe the code page may be "Japanese (Katakana) Extended (00290)" (otherwise known as "IBM-290") listed on this page: http://www-03.ibm.com/systems/i/software/globalization/codepages.html
By manually converting these bytes using this IBM-290 code page, we found that the correct Japanese characters were displayed, though it's possible another code page/character set could work as well.
The Fault Analyzer "LOCALE()" option mentioned in my previous comment allows the user to set the code page that they want Fault Analyzer to use when reading the minidump memory. This should mean that setting the option will display the Japanese Katakana characters as expected. Once the desired code page has been determined, find the corresponding 'local name' from the following list: http://publib.boulder.ibm.com/infocenter/zos/v1r13/index.jsp?topic=%2Fcom.ibm.zos.r13.cbcpx01%2Floccomp.htm&path=6_6_11_3_0
e.g. "LOCALE(Ja_JP.IBM-290)"
However. one potential issue that we may have discovered is listed on this locale listing page: "Not all locales listed in Table 138 are fully enabled. The compiler cannot compile source that is coded in Ja_JP.IBM-290, Ja_JP.IBM-930, Ja_JP.IBM-1390, or Tr_TR.IBM-1026.". It appears that those specific code pages are not fully supported in z/OS C/C++ programs (like Fault Analyzer) and as such, may not display all of the correct characters in the minidump.
Please let us know if this works.
The following response was added to this RFE back in May however I believe the absence of the #publish tag prevented the update from flowing back to the developerworks system. I apologize for this. Please review the following response and let us know the outcome.
Adrian Simcock
Steps required:
1.Determine which specific code page the single-byte Katakana characters belong to
2. Find the locale name that matches this code page
3. Set this locale name inside the Fault Analyzer "LOCALE()" option file
4. Check whether the minidump values are displayed correctly
Notes:
We believe the code page may be "Japanese (Katakana) Extended (00290)" (otherwise known as "IBM-290") listed on this page: http://www-03.ibm.com/systems/i/software/globalization/codepages.html
By manually converting these bytes using this IBM-290 code page, we found that the correct Japanese characters were displayed, though it's possible another code page/character set could work as well.
The Fault Analyzer "LOCALE()" option mentioned in my previous comment allows the user to set the code page that they want Fault Analyzer to use when reading the minidump memory. This should mean that setting the option will display the Japanese Katakana characters as expected. Once the desired code page has been determined, find the corresponding 'local name' from the following list: http://publib.boulder.ibm.com/infocenter/zos/v1r13/index.jsp?topic=%2Fcom.ibm.zos.r13.cbcpx01%2Floccomp.htm&path=6_6_11_3_0
e.g. "LOCALE(Ja_JP.IBM-290)"
However. one potential issue that we may have discovered is listed on this locale listing page: "Not all locales listed in Table 138 are fully enabled. The compiler cannot compile source that is coded in Ja_JP.IBM-290, Ja_JP.IBM-930, Ja_JP.IBM-1390, or Tr_TR.IBM-1026.". It appears that those specific code pages are not fully supported in z/OS C/C++ programs (like Fault Analyzer) and as such, may not display all of the correct characters in the minidump.
Please let us know if this works.
Could you please tell me what kind of information you need?