If you change the default encoding of the VM as I suggested above, console output is
in ascii. If you want to see it without downloading the server log file you can
convert the output stream to EBCDIC so that you can view it in a telnet console for
instance. You can pipe the output thru a filt
that should read "...remove the javax.* packages from it..."
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3838410#3838410
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3838410
Here is some additional information that may be useful setting up a connection to DB2
under JBoss 3.x on z/OS, using IBM's native driver. I used these connection
parameters:
ConnectionURL: jdbc:db2os390sqlj:
DriverClass: COM.ibm.db2os390.sqlj.jdbc.DB2SQLJDriver
Set these paths (appropria
My ejb app is now working on z/OS using JBoss 3.x, but I had to go to the IBM 1.4 vm
instead of the IBM 1.3.1 vm. This is due to a message I was getting about "class
violated loader constraints" during EJB access which seems to be due to an issue in
the IBM 1.3.1 vm. This plus doing everything
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
