A fix is available
APAR status
Closed as program error.
Error description
DataStage 8.1 job aborts while parsing XML with special characters but same job works in version 7.5.X. The error message is: XML_Input,0: Fatal Error: Fatal: XML input document parsing failed. Reason: Xalan fatal error (publicId: , systemId: , line: 1, column: 1): An exception occurred! Type:UTFDataFormatException, Message:invalid byte 2 (N) of a 2-byte sequence. In non-NLS mode XML pack should use the local code page defined in the LANG variable for encoding. Somehow it is not using the local code page for encoding.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: 81 Users **************************************************************** PROBLEM DESCRIPTION: DSCGetNLSOn() always returns true.( even on non-nls systems).The same is fixed **************************************************************** RECOMMENDATION: Apply the patch ****************************************************************
Problem conclusion
DSCGetNLSOn() always returns true.( even on non-nls systems).The same is fixed
Temporary fix
Apply the patch
Comments
APAR Information
APAR number
JR35557
Reported component name
WIS DATASTAGE
Reported component ID
5724Q36DS
Reported release
810
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-02-04
Closed date
2010-05-17
Last modified date
2010-05-17
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
WIS DATASTAGE
Fixed component ID
5724Q36DS
Applicable component levels
R810 PSN
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"InfoSphere DataStage"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
12 October 2021