YAJL error following V7R4 upgrade

[US022614]

Hi,

We upgraded our OS release from V7R3 to V7R4. After that, we are getting errors from our Credit Card processing job in the YAJL area of the code:

Procedure or user-defined function HTTPPOSTCLOBVERBOSE in SYSTOOLS
returned a warning SQLSTATE.
Procedure or user-defined function HTTPPOSTCLOBVERBOSE in SYSTOOLS
returned a warning SQLSTATE.
Procedure or user-defined function HTTPPOSTCLOBVERBOSE in SYSTOOLS
returned a warning SQLSTATE.
1002: parse error: premature EOF█
The document for the DATA-INTO operation does not match the RPG variable;
reason code 5.
Maximum number of records reached for file QPPGMDMP. (C R NOMAX 1-999999)


Message ID . . . . . . : CPF9897 Severity . . . . . . . : 40
Date sent . . . . . . : 02/28/23 Time sent . . . . . . : 08:45:19
Message type . . . . . : Diagnostic
From . . . . . . . . . : QPGMR CCSID . . . . . . . . : 65535

From program . . . . . . . . . : YAJLINTO
From library . . . . . . . . : YAJL
From module . . . . . . . . : YAJLINTO
From procedure . . . . . . . : DATAINTOERROR
From statement . . . . . . . : 25600

To program . . . . . . . . . . : YAJLINTO
To library . . . . . . . . . : YAJL
To module . . . . . . . . . : YAJLINTO
To procedure . . . . . . . . : YAJLINTO
To statement . . . . . . . . : 17300

Message ID . . . . . . : RNX0356 Severity . . . . . . . : 50
Message type . . . . . : Escape
Date sent . . . . . . : 02/28/23 Time sent . . . . . . : 08:45:19

Message . . . . : The document for the DATA-INTO operation does not match
the RPG variable; reason code 5.
Cause . . . . . : While parsing a document for the DATA-INTO operation, the
parser found that the document does not correspond to RPG variable
"responsedata" and the options do not allow for this. The reason code is 5.
The exact subfield for which the error was detected is "responsedata". The
options are "doc=string case=any allowmissing=yes allowextra=yes". The
document name is *N; *N indicates that the document is not an external file.
The parser is 'YAJL/YAJLINTO'. *N indicates that the parser is a procedure
pointer.
Recovery . . . : Contact the person responsible for program maintenance to
determine the cause of the problem.

Technical description . . . . . . . . : Reason codes and their meanings are
as follows:
1. The specified path to the name was not found in the document.
2. The document contains too few array elements for array subfields of a
data structure.
3. The document contains too many array elements for array subfields of a
data structure.
4. The document is missing information to match subfields.
5. The document contains extra names that do not match subfields.

Is this a known issue and is there a code update to fix this? Thanks.

Regards,
Sundar
Uline Inc., Wisconsin

[Scott Klement]

The error means that it encountered a premature EOF -- in other words, it reached the end of file (EOF) before the JSON data was complete.

Check the data you're receiving...

[US022614]

Without any changes, the error resolved itself around noon today. We are wondering if the Credit Card validation service encountered an error and sent us incomplete data and resolved it only today...

We'll keep monitoring the situation. IS there any version check we can do for the YAJL library for potential updates?

[Scott Klement]

You can go here to see if anything new has been done since you downloaded it:
https://www.scottklement.com/yajl/