From the stack trace it appears that the AS400 jdbc driver is trying to
pop up a login dialog (which is a very naughty thing for a driver to
do), which would say to me that the login credentials are probably
incorrect or missing.

-Father Ramon


Rob.S wrote:
> I got the following error upon starting a new driver, based on an existing
> driver.
> ===================
> [02/18/09 11:56:41.664]:*** PT:
> DirXML Log Event -------------------
> Driver: \DEV-CCPSIDV\system\idm\CCPS Drivers\STU-TERMS
> Channel: Publisher
> Status: Fatal
> Message: <description>An unhandled exception was thrown while trying
> to connect: java.awt.HeadlessException:
> No X11 DISPLAY variable was set, but this program performed an operation
> which requires it..</description>
> <jdbc:exception jdbc:class="java.awt.HeadlessException"
> xmlns:jdbc="urn:dirxml:jdbc">
> <jdbc:message>
> No X11 DISPLAY variable was set, but this program performed an operation
> which requires it.</jdbc:message>
> <jdbc:stack-trace>java.awt.HeadlessException:
> No X11 DISPLAY variable was set, but this program performed an operation
> which requires it.
> at java.awt.GraphicsEnvironment.checkHeadless(Unknown Source)
> at java.awt.Window.&lt;init>(Unknown Source)
> at java.awt.Frame.&lt;init>(Unknown Source)
> at java.awt.Frame.&lt;init>(Unknown Source)
> at
> com.ibm.as400.access.ToolboxSignonHandler.setupPas swordDialog(ToolboxSignonHandler.java:573)
> at
> com.ibm.as400.access.ToolboxSignonHandler.handleSi gnon(ToolboxSignonHandler.java:496)
> at
> com.ibm.as400.access.ToolboxSignonHandler.connecti onInitiated(ToolboxSignonHandler.java:50)
> at com.ibm.as400.access.AS400.promptSignon(AS400.java :2148)
> at com.ibm.as400.access.AS400.signon(AS400.java:3412)
> at com.ibm.as400.access.AS400.connectService(AS400.ja va:869)
> at
> com.ibm.as400.access.AS400JDBCConnection.setProper ties(AS400JDBCConnection.java:3016)
> at
> com.ibm.as400.access.AS400JDBCDriver.prepareConnec tion(AS400JDBCDriver.java:1242)
> at
> com.ibm.as400.access.AS400JDBCDriver.initializeCon nection(AS400JDBCDriver.java:1105)
> at com.ibm.as400.access.AS400JDBCDriver.connect(AS400 JDBCDriver.java:355)
> at java.sql.DriverManager.getConnection(Unknown Source)
> at java.sql.DriverManager.getConnection(Unknown Source)
> at
> com.novell.nds.dirxml.driver.jdbc.util.connect.JDB CConnectionImpl.newConnection(Unknown
> Source)
> at
> com.novell.nds.dirxml.driver.jdbc.util.connect.JDB CConnectionImpl.setConnection(Unknown
> Source)
> at
> com.novell.nds.dirxml.driver.jdbc.util.connect.JDB CConnectionImpl.open(Unknown
> Source)
> at
> com.novell.nds.dirxml.driver.jdbc.util.connect.JDB CConnectionManager.newConnection(Unknown
> Source)
> at
> com.novell.nds.dirxml.driver.jdbc.util.connect.JDB CConnectionManager.newPublicationConnection(Unknow n
> Source)
> at
> com.novell.nds.dirxml.driver.jdbc.JDBCPublicationS him.initialConnect(Unknown
> Source)
> at com.novell.nds.dirxml.driver.jdbc.JDBCPublicationS him.start(Unknown
> Source)
> at com.novell.nds.dirxml.driver.jdbc.JDBCPublicationP roxy.start(Unknown
> Source)
> at com.novell.nds.dirxml.engine.Publisher.run(Publish er.java:388)
> at java.lang.Thread.run(Unknown Source)
> </jdbc:stack-trace>
> </jdbc:exception>
> ===============
>
> Any ideas?
>
> 1. I am having both drivers connect to the same server/port, but they are
> dealing with different files
> 2. I'm using the "indirect" method.
> 3. The database "schema" on the AS400 is called "Indirect" as it would be
> in any other JDBC driver. I have added secondary files to support this
> secondary driver. Last_IDU and Last_IDU2; Indirect.indirect_process and
> Indirect.indirect_process2; and so forth.
>
> Thanks for any insights,
>
> Rob
>
>