× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Vinay,

Those are "control characters" -- specifically:

    dec   hex  abbr  description
    ==    ==    ==    ============== 
    28    1C    FS    File Separator
    29    1D    GS    Group Separator
    30    1E    RS    Record Separator
    31    1F    US    Unit Separator

These control characters have the same values in ASCII and EBCDIC, for data "interchange" purposes.

(In EBCDIC, they are called IFS, IGS, IRS and IUS, respectively, for "Interchange File Separator", "Interchange Group Separator", etc.)

But, why do those characters appear in your data?  It might indicate that data was not processed correctly at some earlier stage -- perhaps there should be more separate records, or separate files, etc.?

Something to consider.

All the best,

Mark S. Waterbury

On Tuesday, September 26, 2023 at 05:33:23 PM EDT, Vinay Gavankar <vinaygav@xxxxxxxxx> wrote:

Hi,

I am using YAJLDTAGEN generator to generate JSON string in RPG.

My data has some control characters like x'1C', x'1D' and x'1E' embedded
within other printable characters.

The final JSON string has some other characters instead of my control
characters.

x'1C' is converted to '\u001C' (hex equivalent x'E0A4F0F0F1C3').
x'1E' is converted to '\u001E' (hex equivalent x'E0A4F0F0F1C5').

Is there any way this can be avoided? I want my data to be unchanged in the
JSON string.

TIA
Vinay

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.