|
I believe this implicit conversion support to job CCSID was actually done back in either V3R7 or V4R1. I did try this on a V5R1 system and it worked as expected (no conversion if the job is 65535, conversion if not 65535). Vern Hamberg <vhamberg@centerf ieldtechnology.co To m> Midrange Systems Technical Sent by: Discussion midrange-l-bounce <midrange-l@xxxxxxxxxxxx> s@xxxxxxxxxxxx cc Subject 09/15/2004 01:38 Re: How to display Unicode in SQL PM Please respond to Midrange Systems Technical Discussion That did it, too. Sounds like another consequence of V5R3 changes with 65535 - is that the case? Does a V5R2 machine work with 66535? Just curious Vern At 12:20 PM 9/15/2004, you wrote: >Is your job CCSID 65535? > >On my system: > >chgjob ccsid(37) >strsql >select * from ucsfile > >shows my UCS2 (13488) data converted to my job CCSID. > > > > > > Vern Hamberg > <vhamberg@centerf > ieldtechnology.co To > m> Midrange Systems Technical > Sent by: Discussion > midrange-l-bounce <midrange-l@xxxxxxxxxxxx> > s@xxxxxxxxxxxx cc > > Subject > 09/15/2004 11:51 How to display Unicode in SQL > AM > > > Please respond to > Midrange Systems > Technical > Discussion > > > > > > >The discussion on Unicode coincides with a little problem I'm having. I've >looked a little in the SQL Reference and other SQL manuals, but I've found >nothing on this. > >I am working with an IBM output file for performance data. One of the >columns is Unicode (UCS-2, I assume) - CCSID 13488. The others are numeric >or character or some sort. A SELECT in STRSQL shows the Unicode column in >the usual EBCDIC fashion - accented characters with intervening blanks >(actually x'00' bytes but get converted to displayable blanks). > >The file is QAPMJOBWTD - found from V5R2 onward, I believe. > >Thanks >Vern > > >-- >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: http://lists.midrange.com/mailman/listinfo/midrange-l >or email: MIDRANGE-L-request@xxxxxxxxxxxx >Before posting, please take a moment to review the archives >at http://archive.midrange.com/midrange-l. > > > >-- >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: http://lists.midrange.com/mailman/listinfo/midrange-l >or email: MIDRANGE-L-request@xxxxxxxxxxxx >Before posting, please take a moment to review the archives >at http://archive.midrange.com/midrange-l. -- 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: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
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.