[
https://issues.apache.org/jira/browse/DERBY-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669635#action_12669635
]
Knut Anders Hatlen commented on DERBY-4035:
-------------------------------------------
RunTest also has a section which sets file.encoding to UTF-8 when running the
i18n tests. What happens if you change that too to EBCDIC? (We're not really
supposed to change file.encoding, so that might explain why we have problems
with these tests.) I'm not sure, but there may be some characters in the input
files that are not possible to represent in EBCDIC so that we won't get these
tests to run anyway as long as we copy the input files to the native encoding
first (I don't remember, but I think that may have been the reason why we set
file.encoding to UTF-8 for these tests, but apparently it didn't work as we had
hoped).
Now all the setting of different encoding flags in RunTest is getting very
complex (derby.ui.codeset, console.encoding, file.encoding,
derbyTesting.encoding all set to different values depending on platform, JVM,
name of test), so I'm beginning to think that it is easier to convert these
tests to JUnit and control the encoding per test, rather than trying to clean
up the mess in RunTest.
> 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.
