I tried Tomcat on S390 USS (I think it was 4.0), it does not work. There are EBCDIC to ASCII code translation problems. Looks like Tomcat must use bite streams or other lower level constructs for I/O in a variety of places that do not get the correct code page by default.
As for S390 Linux we have had no problems with tomcat other than starting it automatically after an IPL, that turned out to be a JVM problem. I did not use rpm's I got the Tomcat tar.gz: 1. gzip -d and tar xvf to /usr/local/tomcat. 2. Created a user for tomcat 3. Set owner and group for /usr/local/tomcat 4. su -l tomcat -c "/usr/local/tomcat/bin/startup.sh" For the start after an IPL we found the JVM would just quit if you did not wait about 1min after the runlvl was completed, so in our rc.d script we do at now+1 in front of the startup command to delay one min. On Wednesday 12 March 2003 09:09, you wrote: > Hmm. If it really is 100% Java, then it might very well work. I know > Apache does, so 50% of the problem is already solved. > > Mark Post > > -----Original Message----- > From: David Boyes [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 12, 2003 10:09 AM > To: [EMAIL PROTECTED] > Subject: Re: Tomcat RPMs for S390 > > > I think she's working on Linux for S/390, not OS/390. I doubt Tomcat > would work properly (or at all) under USS. > > -- db > > David Boyes > Sine Nomine Associates > > > -----Original Message----- > > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > > James Melin > > Sent: Wednesday, March 12, 2003 9:30 AM > > To: [EMAIL PROTECTED] > > Subject: Re: Tomcat RPMs for S390 > > > > > > I would be quite interested in a breakdown of what you had to > > do to get > > apache/tomcat (are you doing jboss as well?) running under os/390
