|
I think maybe I'm adding too much complexity to a simple problem. I could just use the op code extender 'E' when I chain instead of checking for a lock. The only problem with that is the job still has to wait 30 seconds(default wait time) until the error is returned. From what I understand the default wait time parameter is ignored when reading a database file. I'm assuming that holds true for chaining as well. ---------------------------------------------------------------------- message: 1 date: Mon, 5 Dec 2005 11:40:25 -0500 from: rob@xxxxxxxxx subject: Re: Finding out which record is locked using QWCLOBJ Worse case scenario, combine that information with this? http://publib.boulder.ibm.com/infocenter/iseries/v5r3/topic/apis/qdbrjbr l.htm Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.