1. It would help if you sent a full stack trace of the exact exception that you're getting. 2. When creating the AS400 object, are you specifying a systemName of "localhost" or using the new AS400() constructor? If not, what does your AS400 constructor invocation look like? Gary > -----Original Message----- > From: java400-l-bounces@xxxxxxxxxxxx > [mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of Coy Krill > Sent: Tuesday, December 27, 2005 6:30 PM > To: Java Programming on and around the iSeries / AS400 > Subject: Running Java Application from Job Scheduler and User > Has No Password > > I've looked through the list and have seen some references to > problems running jobs with a user profile with *NONE for the > password, but none of the referenced fixes seems to work for me. > > I have a program that manages our spooled files and it works > just fine when submitted by an interactive job, but when I > put the job on the scheduler and run it using our automation > user profile that has password *NONE, it complains about the > fact that the user has a password of *NONE. At first it was a > complaint when using the cross-platform JDBC driver, so I > switched to the native DB2 driver. The next problem was that > it didn't have a property set way down in the > SpooledFileList. I traced through the code to where it was > sending the exception because the system name wasn't set in > the implementation object. So I tried to force it by making > an AS400.FILE connection early on. That's now where I'm > getting the error on the password being *NONE. Is there no > way to run a java app from the scheduler using a user profile > with no password? I have set the expiration limit to *NOMAX > and that doesn't seem to have helped. > > Coy Krill > Systems Analyst > Whidbey Island Bank
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.