If you have already contacted support, continue on to the
component-specific MustGather information. Otherwise, click: MustGather:
Read first for all WebSphere Application Server products.
i18n/DBCS specific MustGather information
- Create a simple testcase that shows the problem. Make sure to verify
that it do not have any external dependencies and confirm that it does
fail on your system.
- Collect the following:
- A screen capture of expected character rendering and error
condition.
- SystemOut.log, SystemErr.log,
trace.log, as well as any logs that capture application output.
- For UNIX® systems, value of LOCALE settings.
- The ibm-web-ext.xmi file found in the
WEB-INF folder of the failing Web application.
- If the failing application retrieves DBCS data from a
database, then a detailed description of your database configuration and
included JDBC driver level.
Finally, a trace might be necessary at a later time. If it is convenient
to capture a Servlet Engine and Web Container trace when recreating the
problem, it could reduce time to resolution. You can find information in
the following Related information section for Servlet Engine and Web
Container trace on V5
and V6.
Follow instructions to submit
the diagnostic information to IBM Technical Support for problem
determination.
For a listing of all technotes, downloads, and educational materials
specific to the i18n/Internationalization/DBCS component, search the WebSphere
Application Server support site. |