× 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.



The system i will require a user account, but not necessarily that of the user
running the jdbc app - and this is where I don't know all details.

If connecting more like System i Navigator Run SQL Statements, then
connections use a QZDASOINIT pre-start job, and that user will
becomes the current user, and I have never had or seen anyone face the
system i signon prompt in that context.

On the other hand, a MS Access app we run and which updates system i
tables will prompt for a user id and password if/when the user running
the app lets their system i account lapse or, I think, password get
out of sync, or neglect to start a 5250 session first. This app
uses ODBC/ADO drivers to connect.

Again, all this from memory: HTH



-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of TAllen@xxxxxxxxxxxxxxxxx
Sent: Monday, January 16, 2012 10:47 AM
To: Java Programming on and around the IBM i
Subject: RE: JDPC prompt

When you say "keeping the user account in synch with the system i" what do you mean? I am simply trying to connect to the system i from a Java application via JDBC.

Thanks,
Todd Allen
Estes Express Lines
tallen@xxxxxxxxxxxxxxxxx




Gary Thompson
<gthompson@swirec
c.com> To
Sent by: Java Programming on and around the
java400-l-bounces IBM i <java400-l@xxxxxxxxxxxx>
@midrange.com cc

Subject
2012-01-16 12:38 RE: JDPC prompt


Please respond to
Java Programming
on and around the
IBM i
<java400-l@midran
ge.com>






Todd, maybe it is the user account on the machine that is making the connection -
my experience is with ODBC-type connections, but when we kept the user
account, including password, in sync with the system i, the login prompt
from the i could by "by-passed".

If I remember correctly, we also needed to configure the 5250 session
Properties to "Use System I Navigator default" for User ID signon information.

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx
] On Behalf Of TAllen@xxxxxxxxxxxxxxxxx
Sent: Monday, January 16, 2012 10:03 AM
To: Java Programming on and around the iSeries / AS400
Subject: JDPC prompt

I know I've dealt with this before but it has been a while. I've got a Java app that makes a JDBC connection. The connection is using a properties file. Each time I am getting a login screen. How do I suppress this? The user and password are in the properties file. Logging in with the user and password in the properties file works fine.

Thanks,
Todd

For 80 Years — Delivering Solutions that Exceed Expectations.
This communication and any transmitted documents are intended to be confidential. If there is a problem with this transmission, please contact the sender. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited.
--
This is the Java Programming on and around the IBM i (JAVA400-L) mailing list To post a message email: JAVA400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/java400-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.