|
On 03/09/2003 at 03:59:40 AM, java400-l-bounces+kulack=us.ibm.com@xxxxxxxxxxxx wrote: the wait time depends on the database (as400: waitfile - default *immed and waitrecord default 60) and maybe on your driver. --- end of excerpt --- Yeah, the WAITFILE and WAITRECORD parameters on the physical file that Dieter mentioned will probably get you want you want. You may also want to look at the CHGJOB command. Its relatively common to have a single 'setup' sort of stored procedure that you run one time when you get a connection that sets up your backend agent DB environment (i.e. AS/400 job settings) the way you want it for that connection. There's a default wait time on that job that occasionally comes into play as it relates to waiting for locks. "The stuff we call "software" is not like anything that human society is used to thinking about. Software is something like a machine, and something like mathematics, and something like language, and something like thought, and art, and information... but software is not in fact any of those other things." Bruce Sterling - The Hacker Crackdown Fred A. Kulack - IBM eServer iSeries - Enterprise Application Solutions ERP, Java DB2 access, Jdbc, JTA, etc... IBM in Rochester, MN (Phone: 507.253.5982 T/L 553-5982) mailto:kulack@xxxxxxxxxx Personal: mailto:kulack@xxxxxxxxxxxxxx AIM Home:FKulack AIM Work:FKulackWrk MSN Work: fakulack@xxxxxxxxxxx
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.