Use job default CCSID for SQL (ie. instead of CCSID 65535)

When a system is currently configured with its CCSID set to 65535, this causes issues with SQL functions that require CCSID conversions (ex. JSON, HTTP, ...), for example

Select cast(RESPO00001 as varchar(32)), cast(RESPO00002 as varchar(32))
from Table(QSYS2.HTTP_POST_VERBOSE(
'http://echo.free.beeceptor.com', '{"hello":"world"}', '{"headers": {"Content-Type": "application/json"}}'))

This statement will result in error SQLCODE = 332 SQLSTT = 57017 or "CHARACTER CONVERSION BETWEEN CCSID TO REQUESTED BY IS NOT SUPPORTED" in case the system is running with CCSID 65535.

A job has however also a "Default coded character set identifier" (next to the job CCSID) which is determined by the language ID. This alternative CCSID can be seen on page 4 of DSPJOB OPTION(*DFNA).

It would be nice if SQL could be instructed to use this value instead of the normal CCSID value as it would fix the above statement (now we need to explicitly set the job CCSID before each SQL statement).

I found an attribute SQL_ATTR_NON_HEXCCSID (which seems to allow to use the default CCSID) but I guess that can only be set for SQL CLI, not for embedded or interactive SQL.

It would therefore be handy to have for example an environment variable to do something similar for embedded or interactive SQL

PS. Ideally we would change the QCCSID value but this has been historically set to 65535 and we don't know the impact (and retesting all software is almost impossible) when changing this value.