×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Maybe here:
http://www-912.ibm.com/s_dir/slkbase.nsf/1ac66549a21402188625680b0002037e/1844b1c3eb91bbf886256c5b0071fbba?OpenDocument&Highlight=2,http,admin
There are several things to check on.
ZSRV_MSG0362: Client denied by server configuration: This is a problem
where Java does not realize that it is running on the operating system.
It is caused by the user putting jar files in the Java classpath; it is
probably a file named jt400*. To see the actual classpath, you can
install this small Java program on the machine:
import java.util.*;
import java.io.*;
public class classpaths {
public static void main(String args[]) {
System.out.println("sun.boot.class.path=" +
System.getProperty("sun.boot.class.path"));
System.out.println("java.ext.dirs=" +
System.getProperty("java.ext.dirs"));
System.out.println("java.class.path=" +
System.getProperty("java.class.path"));
}
}
Name this file classpaths.java. It must be in CCSID 819; therefore, FTP
Loopback might be required to send the file back to the same directory
(ASCII mode). View the file, and verify that the square brackets look
normal (you can also CAT the file in QSH). Start QSH and CD to the
directory with the classpaths file in it. Use the command: javac
classpaths.java to compile the Java routine. There should be no errors.
Then, while still in the directory, issue the command: java classpaths.
This lists the classpath for Java. On a V5R1 system, this defaults to
the path for Java Toolkit 1.3. Use the command: java -Djava.version=1.2
classpaths to run the program against the classpath for Java Toolkit
1.2. The error message above was related to a jt400.jar file placed in a
/java400/ext directory that was not part of the path for Java Toolkit
1.3 but rather only for Java Toolkit 1.2 . The /ext directories are read
first, so the jt400.jar there is found. Because that file / directory
are not optimized for the IBM® iSeries™, the toolkit thinks it is
running on a different system.
Jonathan Mason said the following on 4/11/2007 10:33 AM:
Hi Steve
I've tried using both www.astradyne-uk.com:2001 which has port redirection
mapped to the iSeries and also 192.168.0.101:2001 which is the local IP
address within the network. Both give the same result.
I'll power up the v4r5 box later and see what happens with that one.
Cheers
Jonathan
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.