Re: Left and Right Quotation Marks

The critical factor I think is how the data will be used. If it has to be displayed/printed on attached EBCDIC devices then converting to conventional quotes is really the only option if changing the code page of the field in question is not an option.

On the other hand if you are just "holding" the data and it will just be sent out as JSON or other UCS2 forms then you could just add your own escape sequence to allow it to be restored and recovered.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On May 18, 2018, at 9:35 AM, Bradley Stone <bvstone@xxxxxxxxx> wrote:

That was why I was questioning the workaround. :)

I do appreciate the input though. I am just guessing that while those
answers will allow it to convert, I would also need to change the CCSID of
the job/files/etc. That most likely won't happen any time soon.


On Fri, May 18, 2018 at 7:54 AM Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:

Don't see how they could Brad - they don't exist in that code page do they?


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On May 18, 2018, at 8:49 AM, Bradley Stone <bvstone@xxxxxxxxx> wrote:

I guess my question is.. will these curly quotes even work in a PF with
CCSID 37?


On Fri, May 18, 2018 at 6:44 AM Barbara Morris <bmorris@xxxxxxxxxx>

wrote:

On 2018-05-17 6:39 PM, Scott Klement wrote:

2) An easier solution would be to use DATA-INTO with the YAJLiNTO
parser, and specify ccsid=ucs2, and define the RPG field also as UCS-2.
This causes all of DATA-INTO's work to be done in Unicode, and since

the

RPG field is also unicode, you'd get the quotes as expected.

It's not necessary to specify ccsid=ucs2 for DATA-INTO. Unlike XML-INTO,
DATA-INTO defaults to cccsid=ucs2.

--
Barbara

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related

questions.

Help support midrange.com by shopping at amazon.com with our affiliate

link: http://amzn.to/2dEadiD

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD