I was able to get JBoss 3.x apparently running (a servlet works) on OS/390 (z/OS) OMVS by uploading everything in my JBoss windows directories as a binary tar (preserving the ascii encoding of the xml files and not converting to EBCDIC), then setting the system properties in run.sh as if it was Windows:
JAVA_OPTS="$JAVA_OPTS -Dsun.io.unicode.encoding=UnicodeLittle -Dfile.encoding=Cp1252 -Djava.compiler=NONE" This is using the same IBM JDK 1.3.1 to run JBoss that runs my app on Websphere on Z/OS. The console output is in ascii, which is viewable on the OMVS console as garbage, but you can ftp download server.log as binary and view it in Notepad. You could also probably write a ascii-to-EBCDIC conversion program in java easily and pipe the JBoss console output thru it to view it in OMVS. I still have some work to do with the EJB deployment so there may be other issues I havent encountered yet. Anyone else have any caveats to share? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3837857#3837857 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3837857 ------------------------------------------------------- This SF.Net email is sponsored by: GNOME Foundation Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event. GNOME Users and Developers European Conference, 28-30th June in Norway http://2004/guadec.org _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
