Troubleshooting
Problem
Beginning with WebSphere Transformation Extender Version 8.1, the PACKAGE function returns a valid code page for data contained within group objects. Prior to Version 8.1, data contained within group objects had an unknown code page. As a result, a map rule that uses the PACKAGE function and the GET, PUT, or RUN adapter commands on any platform can convert data to a code page that is incompatible with the adapter.
Resolving The Problem
Change the map rule to use the CPACKAGE function, and specify the character set as NATIVE in the second argument of the rule.
For example, in a UNIX System Services (USS) execution environment, if you run a map on the that is set up to use the Java adapter and has a rule that uses the PACKAGE function, the PACKAGE function causes the map to convert the data to the NATIVE code page. In the USS execution environment, the character set for NATIVE is EBCDIC, which is invalid for the Java adapter, and causes a Java exception error.
Change the rule from:
GET("JAVA","-T",PACKAGE(GROUP:RECORD))
to:
GET("JAVA","-T",CPACKAGE(GROUP:RECORD,"NATIVE"))
With NATIVE in the second argument of the CPACKAGE function, the function treats the data as if it already is in the appropriate code page and does not attempt to convert it to NATIVE.
Was this topic helpful?
Document Information
Modified date:
23 June 2018
UID
swg21413048