[
https://issues.apache.org/jira/browse/DERBY-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manjula Kutty closed DERBY-588.
-------------------------------
Resolution: Invalid
This is a jvm issue and filed the issue in the IBM jvm bug tracking system. And
the PMR number is 87297,001,866. So closing this issue as invalid
> database created on zOS (os/390) cannot be used on windows
> ----------------------------------------------------------
>
> Key: DERBY-588
> URL: https://issues.apache.org/jira/browse/DERBY-588
> Project: Derby
> Issue Type: Bug
> Components: Services
> Affects Versions: 10.1.1.0
> Environment: zOS, R6, with ibm jvm 142
> Reporter: Myrna van Lunteren
> Attachments: TestPropertiesWrite.java
>
>
> When a database is created on zOS, the service.properties is readable
> English, thus, it is created in EBCDIC or with file.encoding Cp1047. After
> jar -cvf, ftp to window, jar -xvf, the database is not accessible:
> ---------------
> ERROR XJ040: Failed to start database 'bladb2', see the next exception for
> details.
> ERROR XCY03: Required property 'derby.serviceProtocol' has not been set.
> --------------
> which is the error we get when something is wrong with service.properties in
> the database.
> After converting (native2ascii -encoding Cp1047) service.properties, the
> database is usable again.
> Doing the reverse, i.e. creating and jar-ing the database on windows and
> ftp-ing it to zOs, works fine. In that case, service.properties is not
> readable.
> If I understand correctly how this should work, Derby should not create the
> service.properties on zOS in local encoding.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
