db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-588) database created on zOS (os/390) cannot be used on windows
Date Wed, 28 Sep 2005 22:30:48 GMT
database created on zOS (os/390) cannot be used on windows
----------------------------------------------------------

         Key: DERBY-588
         URL: http://issues.apache.org/jira/browse/DERBY-588
     Project: Derby
        Type: Bug
  Components: Services  
    Versions: 10.1.1.0    
 Environment: zOS, R6, with ibm jvm 142
    Reporter: Myrna van Lunteren


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.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message