Troubleshooting
Problem
A simple map reading some JSON data either fails or succeeds, dependent upon the page size/count settings.
Using IBM Transformation Extender, a map reading a specific input should always be consistent, regardless of the page size/count settings.
Symptom
The audit log may show:
<Message>One or more inputs was invalid</Message>
The content trace may show:
INPUT 1 exists, but its type is in error.
Cause
There was a boundary condition where the ITX JSON parser was not breaking out of a data loop at the end of the buffer and this caused JSON parser errors.
Environment
IBM Transformation Extender maps reading JSON data on any supported platform.
Diagnosing The Problem
This issue can be detected by examining the results when using different settings of the Workspace/Pagesize value. The map should treat the input the same, regardless of this value.
Resolving The Problem
Obtain and apply the fix from APAR PH03279 from IBM Support
Was this topic helpful?
Document Information
More support for:
IBM Transformation Extender
Software version:
9.0.0.0, 9.0.0.1, 9.0.0.2
Operating system(s):
AIX, HP-UX, Linux, Solaris, Windows, z/OS
Document number:
735687
Modified date:
18 October 2018
UID
ibm10735687