Re: CPYTOIMPF and accented characters

[Mohammad Tanveer <surgum@xxxxxxxxx>]

ok here it is... my data is in a table with fields defined with CCSID 37

My JOB CCSID = 37

This is my test table: DANISH2   CCSID 278

           Data        Field  Buffer    Buffer        Field    Column
Field      Type       Length  Length  Position        Usage    Heading
CHAR_00001 CHAR           30      30         1        Both     CHAR_COLUMN
  Alternative name  . . . . . . . . . . . . :
      CHAR_COLUMN
  Allows the null value
  Coded Character Set Identifier  . . . . . :    278


Inserted one record hard coded value:
insert into danish2 values('MÅGEVEJ 44')

CHAR_COLUMN                     HEX ( CHAR_COLUMN )

MÅGEVEJ 44
 D45BC7C5E5C5D140F4F44040404040404040404040404040404040404040

When I copy this DANISH2 file to IFS using the CPYTOIMPF all looks good

... Problem starts when... I copy data from following a file.. into
DANISH2.. This file sl600o has data in CCSID(37) format.
insert into Danish2
SELECT substr(add1,1,30) FROM sl600o WHERE
add1 like '%M$G%E%44%'


Now when I look at my DANISH table I have two records both are showing
different HEX.

CHAR_COLUMN                     HEX ( CHAR_COLUMN )

MÅGEVEJ 44
 D45BC7C5E5C5D140F4F44040404040404040404040404040404040404040
M$GEVEJ 44
 D467C7C5E5C5D140F4F44040404040404040404040404040404040404040

If I switch my job CCSID to 1134 and check DANISH2 table I see following..
CHAR_COLUMN                     HEX ( CHAR_COLUMN )

M$GEVEJ 44
 D45BC7C5E5C5D140F4F44040404040404040404040404040404040404040
MÅGEVEJ 44
 D467C7C5E5C5D140F4F44040404040404040404040404040404040404040



On Wed, Nov 2, 2016 at 1:09 PM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

> On 11/2/2016 3:19 PM, Mohammad Tanveer wrote:
> > It looks like when I entered the data as per your example it took it as
> > ASCII character code that is why it appeared correctly.
> >
> > I copied the data from my database which stored the data as Danish
> > character set then translation is not happening correctly.. looks like my
> > problem still exists
>
> Stored how?
> DSPFFD and tell us what the CCSID of the column is.
>
> > You can see Record#1 was copied using the values from Danish CCSID 278
> and
> > #2 was entered manually using the SQL
> >
> > STRSQL(US 037 Mode)
> > RRN ( A )   CHAR_COLUMN
> >         1   M$GEVEJ 44  (entered using den/swe character set)
> >         2   MÅGEVEJ 44  (ASCII input)
> >         3   KÆRBØLVEJ 52
>
> Entered how?
> By a TN5250 job last year with a CCSID of 65535?
> By DBU just now with a job CCSID of 65535?
> By DBU just now with a job CCSID of 278?  37?
>
> I'm trying to understand the situation you face there, but I don't have
> enough information yet to re-create the problem here.  I gave an example
> of your data and your CCSIDs and it works, so either your people are
> doing something different or there's a PTF you need that I have.  I'm on
> TR4 (WRKPTFGRP, SF99717).
>
> For one more added data point, here is DSPPFM DANISH
>
> KÆRBØLVEJ 52
> D9DC8DECD4FF444444444444444444
> 2E9203551052000000000000000000
>
> M$GEVEJ 44
> D5CCECD4FF44444444444444444444
> 4B7555104400000000000000000000
>
>
> Here is DBU DANISH
>
> KÆRBØLVEJ 52
> D9DC8DECD4FF444444444444444444
> 2E9203551052000000000000000000
> MÅGEVEJ 44
> D6CCECD4FF44444444444444444444
> 477555104400000000000000000000
>
>
> Here is SELECT HEX(CHAR_COLUMN) FROM DANISH
>
> D29ED9C280D3E5C5D140F5F2404040404040404040404040404040404040
> D45BC7C5E5C5D140F4F44040404040404040404040404040404040404040
>
> All on a green screen with job CCSID(37).  What does your system show?
>
> One more thing.  CCSID 278 has assigned 'A-ring' to x'5B'
> ftp://ftp.software.ibm.com/software/globalization/gcoc/
> attachments/CP00278.pdf
>  So DSPPFM is correct to show me x'5B' as the raw data.
>
> I found that PDF from here:
> https://www-01.ibm.com/software/globalization/cp/cp_cpgid.html
>
>
> --
>   --buck
>
> Visit wiki.midrange.com and register for an account. Edit a page that
> helps you, and because it's public, you'll help someone else, too!
>
> --
> 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.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.