Any CCSID other than 1208 fails to connect to database

[ibm]

Any CCSID other than 1208 fails to connect to database

[abmusse]

Original comment by Kerim Gueney (Bitbucket: KerimG, GitHub: KerimG).

---

@dmabupt

I think so, yes. Thank you very much.

[abmusse]

Original comment by Xu Meng (Bitbucket: mengxumx, GitHub: dmabupt).

---

@KerimG Can we close this issue now?

[abmusse]

Original comment by Xu Meng (Bitbucket: mengxumx, GitHub: dmabupt).

---

Hello @KerimG , the DB2CCSID env var actually calls SQLOverrideCCSID400().

Ref --> https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_61/apis/pase_sqloverrideccsid400.htm

Long long ago this DB2 addon ran with its job CCSID (which corresponding to CCSID = 0). But it had some problems so I overrides the default CCSID to 1208 (UTF-8) and adds this DB2CCSID env var for customization.

[abmusse]

Original comment by Kerim Gueney (Bitbucket: KerimG, GitHub: KerimG).

---

Hello @dmabupt,

the character set mismatch issue has been resolved ( #18 ). It wasn't actually a characterset mismatch, despite the error message making it seem so,

Nonetheless, shouldn't

process.env.DB2CCSID = '273';

work?

Your suggestion with

process.env.DB2CCSID = '0';

on the other hand does work.

Perhaps I'm confused about what the DB2CCSID environment variable is for. I assumed that it has to match whatever CCSID the database fields are defined in.

[abmusse]

Original comment by Xu Meng (Bitbucket: mengxumx, GitHub: dmabupt).

---

Hello Kerim,
Would you show me the error when you insert data with CCSID 1208?
The system automatically converts character arguments and results between the CCSID of the job or database field and a CCSID used for idb-connector functions that defaults to 1208 (UTF-8).
Generally we do not need to change the default CCSID value. But you may try

#!javascript

process.env.DB2CCSID = '0';

[abmusse]

Original comment by Jesse G (Bitbucket: ThePrez, GitHub: ThePrez).

---

I'm not sure on this one, but assigning to @dmabupt who can probably handle.