scottklement.com

Does anybody have a good idea how to handle this?

In the documentation for XML-SAX it is possible to specify that the data passed to the XML-handler is in a certain CCSID. So it is possible to specify CCSID=1208 ( UTF-8 ) P xmlHandler B D xmlHandler PI 10i 0 D ignore 1a D event 10i 0 value D string * value D stringLen 20i 0 value D exceptionId 10i ...

Yesterday I had an RPG-program where the XML-SAX command failed with error code 6. After googling what this means, I found out that the cause was a character that couldn't be converted from UTF-8 to EBCDIC. I think it was the "hat" ^ character that somebody had hit accidently. This program...

Depending on the version of the operating system the problem is that the file has the wrong CCSID.
I assume it is 1252 ( Windows character set )

You have to change it to 1208 ( UTF-8 )
CHGATR OBJ('myFile.xml') ATR(*CCSID) VALUE(1208)

If the file is greater than 2GB then you have to add O_LARGEFILE to the open flags You can read more about it here: https://www.ibm.com/docs/en/i/7.2?topic=ssw_ibm_i_72/apis/open.html In the IFSIO_H copy source it is defined like this: * 00100000000000000000000000000000 Large file access * (for >2GB...

What CCSID does the file have?
And what format does it have ( Ascii, UTF-8, UTF16be ... )

If it is an UTF format then it could be the byte order markers that causes the problems.
I have experienced this before
Try to open it in Notepad++ There you can see the format.

Regards
Peder

Receiving a file in UTF-16 little endian from a Windows on an as/400 ( formerly known as ) gives a practical problem that the as/400 only can handle UTF-16 big endian ( CCSID(1200) ). As far as I can see UTF-16 little endian ( CCSID(1202) ) is not supported here. The question is: Is it enough to cre...

Another option to generate PDFs would be to use InterForm

https://interform400.com/

A quick and dirty solution could be to open the file and read the first 1MB into a variable.
Then scan for the string "AmbiguousAddressIndicator":

If it is found then it is file 2 else it is file 1

Don't forget to close the file after reading

If I understand you correct then it is the file in the IFS on your local machine that is not closed. Many years ago I had the same problem. I made a small program that tried to open the IFS file exclusively with the flags flags = O_RDONLY + O_SHARE_NONE; The program was called with the parameters 1)...