×
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.
On 16-Dec-2015 08:37 -0600, Werner, Robert wrote:
I've changed my job to DFTWAIT(1) yet when I run a program it hangs
on a "chain(e)" statement if I have that specific record locked on
another session. We are on v7r1 tr9.
The Default Wait Tim (DFTWAIT) time is intended for timeout for
locking of whatever does not have a specific timer; from the Change Job
(CHGJOB) help text for that setting, the "default wait time is used when
a wait time is not <ed: or can not> otherwise specified for a given
situation. ... The wait time specified for this parameter is ignored
for read <ed: and open> operations to database files." The Data
Management (DM) wait timers for the Database File Member Open requests
are the Maximum Record Wait Time (WAITRCD) for records and the Maximum
File Wait Time (WAITFILE) for file members. These attributes can be set
in the file creation Create Physical File (CRTPF) and Create Logical
File (CRTLF), and can be changed using Change Logical File (CHGLF) or
Change Physical File (CHGPF), or can be overridden at run-time using the
Override With Database File (OVRDBF).
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.
midrange.com
