This may also be due to the AS400 driver itself.
When you create the AS400 connection object, you can pass it a
property of "prompt".
The default is "prompt=true". If your special logon fails, the Driver
takes over and prompts for good information.
If you want to control everything, use the property "prompt=false",
and the connection will throw an exception if it fails.
However, I believe you will then have to figure out yourself whether
the failure was due to an invalid password, or an expired password,
or....
Here is an example using a properties file (you could just put the
properties in the URL also)
java.util.Properties p = new java.util.Properties();
p.put("libraries", "QS36F QGPL");
p.put("errors", "full");
p.put("user", getUserName());
p.put("password", getPassword());
p.put("transaction isolation", "read committed");
p.put("prompt", "false");
setJdbcConnection(DriverManager.getConnection("jdbc:as400:" +
getSystemName(), p));
Robin Nilsson
Sr Programmer/Analyst
SRC Vision
Medford, OR
[EMAIL PROTECTED]
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
