QMHSNDM parameters

[ibm]

QMHSNDM parameters

[kadler]

Original comment by Tony Cairns (Bitbucket: rangercairns, GitHub: rangercairns).

---

little training for debug ...

Real problem was system API documentation just plain misleading. Aka, the data in msgKey is not character, but binary (change msgKey 4a to 4b).

#!python

.addParm(iData('msgKey','4a',''))

... change to ...

 .addParm(iData('msgKey','4b',''))

... how does a human know documentation is lying ???

The key indicator was that debug/trace XML simply stopped middle of the XML document. Aka, var="msgKey" simply did not continue. Of course, this means the binary data most likely had a zero in the data, which acted like a null terminated string for the XML string. The trace output simply did not finish printing the entire XML document ... ding, ding, ding, debug rule (below) ... system API needed binary type not character.

#!bash

6f3d22626f746822207661723d227039 o="both" var="p9
223e0a3c6461746120747970653d2234 ">.<data type="4
6122207661723d226d73674b6579223e a" var="msgKey">
3c215b43444154415b <![CDATA[

Therefore, as a general debug rule, when debugging system APIs and you see truncated XML, the most likely need is to change your data type from character to binary (change msgKey 4a to 4b).

Aka, the 'liar, liar, pants on fire' system API debug rule.

[kadler]

Original comment by Tony Cairns (Bitbucket: rangercairns, GitHub: rangercairns).

---

I made the correction in issue #8.