When you zipped it up and unzipped it on Linux, did you by chance use Windows to zip it? This sounds a lot like the problems I had. Windows apparently can't handle all the symbolic links on that CD. I ended up taking the CD to a linux machine and making a ISO out of it using Linux, then FTP'ing it up and then mounting that .iso file.
(I sure wish they didn't do this stuff with pretty installs. Boy MQ Series was a breeze since it's just .rpm's and uses standard stuff!) Marcy Cortes Wells Fargo Services -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Kevin A. Schmidt - at Potomac Electric Power Company Sent: Tuesday, May 25, 2004 14:53 To: [EMAIL PROTECTED] Subject: [LINUX-390] Error running graphic install for DB2 Connect version 8.1 I am looking for someone that has installed DB2 Connect version 8.1 and has run into a problem running the db2setup graphical process. I zipped up DB2 Connect V8.1, uploaded it to my Linux zSeries image and unzipped it. I am using Reflections-X to support the xterm graphical interface to Linux zSeries. When I went to run the graphical install process, it failed with these messages: Exception in thread "main" java.lang.UnsatisfiedLinkError: /home/schmidk/DB2ConnectUnzipped/db2/linux390/install/libdb2ure.so: /home/schmidk/DB2ConnectUnzipped/db2/linux390/install/libdb2ure.so: file too short at java.lang.ClassLoader$NativeLibrary.load(Native Method) at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1799) at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1685) at java.lang.Runtime.loadLibrary0(Runtime.java:780) at java.lang.System.loadLibrary(System.java:865) at com.ibm.db2.install.core.NativeLibraryInitializer.initLibrary(Unknown Source) at DB2Setup.<init>(Unknown Source) at DB2Setup.main(Unknown Source) I got around the problem by running the non-graphical installation db2_install script. Later in the process I discovered that since I had installed the IBM JDK 1.4, this caused a problem in the db2javit script when I tried to launch the Client Configuration Assistant. Apparently IBM built some of the com objects that assumed you had the requisite JDK 1.3. They blew off because it could not find the /opt/IBMJava2-s390-131 directory. I created a symbolic link for the directory and that allowed me to launch the Client Configuration Assistant. I thought maybe this was related to the problem running the db2setup process. It wasn't. It still failed. Has anyone run into this problem? Kevin Schmidt Supervisor, Systems Programming PHI Services Company room 3609 701 9th Street, NW Washington D.C. 20068 phone: (202) 872-2081 cell: (202) 744-5714 fax: (202) 872-2252 email: [EMAIL PROTECTED] ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
