[ 
https://issues.apache.org/jira/browse/DERBY-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668585#action_12668585
 ] 

Kathey Marsden commented on DERBY-4035:
---------------------------------------

This seems to be related to the fact that the i18n tests are run with 
derby.ui.codeset=UTF8.  The input sql file is EBCDIC on Z  so this really 
mangles things.  The change to have the i18n tests run with 
derby.ui.codeset=UTF8 was made as the fix for DERBY-244.

If I force the derby.ui.codeset to EBCDIC the test doesn't pass but fails only 
with a bit of garbage of the form EnC:>65533<  EnC:>655533...  at the beginning 
of the file before the version prints.  The rest of the output is as expected.



> i18n tests fail with Lexical error on z/os 
> -------------------------------------------
>
>                 Key: DERBY-4035
>                 URL: https://issues.apache.org/jira/browse/DERBY-4035
>             Project: Derby
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 10.3.3.0, 10.5.0.0
>         Environment: java version "1.6.0"
> Java(TM) SE Runtime Environment (build pmz6460sr3-20081108_01(SR3))
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 z/OS s390x-64 
> jvmmz6460-20081107_25433 (JIT enabled, AOT enabled)
> J9VM - 20081105_025433_BHdSMr
> JIT  - r9_20081031_1330
> GC   - 20081027_AB)
> JCL  - 20081106_01
> $
>            Reporter: Kathey Marsden
>
> On z/os  the following tests fail with a Lexical error e.g.
>  ERROR 42X02: Lexical error at line 1, column 1.  Encountered: "`" (96), 
> after : "".  There also seems to be some garbage in the output.  The tests 
> that fail with these errors are:
> derbyall/derbyall.fail:i18n/JapanCodeConversion.sql
> derbyall/derbyall.fail:i18n/UnicodeEscape_JP.sql
> derbyall/derbyall.fail:i18n/I18NImportExport.sql
> derbyall/derbyall.fail:i18n/urlLocale.sql
> derbyall/derbyall.fail:i18n/messageLocale.sql
> derbyall/derbyall.fail:i18n/caseI_tr_TR.sql
> derbyall/derbyall.fail:i18n/iepnegativetests_ES.sql
> The error I think is coming from ij, it is not in the derby.log and there is 
> not a stack trace anywhere.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to