Re: setting CCSID of QZDASONIT jobs

    Hi Eric,

    Here's a possibility that should work.  Because of all the possible
non-standard variations, a conforming JDBC driver will allow *any* string to
be sent to the DBMS.  If the DBMS/OS understands how to interpret it, the
statement will be run.  In "Getting Started with the JDBC API", here's what
"SQL Conformance" at:

<
http://java.sun.com/j2se/1.5.0/docs/guide/jdbc/getstart/intro.html#1018592
>

says:

" One way the JDBC API deals with this problem is to allow any query string
to be passed through to an underlying DBMS driver... In fact, an application
query may be something other than SQL..."

    So, you should be able to pass a  CALL QSYS.QCMDEXC statement for
CHGJOB, using Statement.executeUpdate() or Statement.execute().  See

<
http://www-912.ibm.com/s_dir/slkbase.NSF/0/f1eaeecc0af19cc38625669100569213?OpenDocument
>

for an example with OVRDBF.


                                                         Joe Sam

Joe Sam Shirah -        http://www.conceptgo.com
conceptGO       -        Consulting/Development/Outsourcing
Java Filter Forum:       http://www.ibm.com/developerworks/java/
Just the JDBC FAQs: http://www.jguru.com/faq/JDBC
Going International?    http://www.jguru.com/faq/I18N
Que Java400?            http://www.jguru.com/faq/Java400


----- Original Message ----- 
From: "Eric Lee" <Eric.Lee@xxxxxxxxxxxx>
To: <JAVA400-L@xxxxxxxxxxxx>
Sent: Monday, February 28, 2005 6:50 AM
Subject: setting CCSID of QZDASONIT jobs


> Hi All,
>
> I need to set the ccsid of the QZDASONIT job started by a JDBC connection
> to 65535.
>
> I've tried changing the ccsid of the iSeries user profile that the JDBC
> connection uses - but that does not work
> with 65535 - it takes the sysval if you try to use 65535. (The ccsid of
> the qzdasonit job is set correctly if you use another value that forces
> conversion)
>
> Does anyone know of another way I can achieve this (without changing the
> sysval)?
>
> My problem is to do with the jobs writing a hex '3F' for certain accented
> characters which is causing problems when the character is read in.
>
> When the job is 65535 - (when I change the job's ccsid manually) the
> characters are written with a valid hex code.
>
> Best regards,
> Eric Lee
> DCS Transport & Logistics Solutions
>