|
I checked the AJS command list file,
QUSRIJS/QAIJS1CM, WAITRCD set to 60.
All the AJS files are set to 60.
Maximum record wait time . . . . . . . . . : WAITRCD 60
I then checked the QIJSSCD monitor job for overrides.
The command list file was not listed, probably one of the others is
causing the lock.
Waiting for update from IBM.
AJS is an IBM product, but development is 3rd party.
Opt File Level Type Keyword Specifications
QAIJSWFS 5 DB TOFILE(QUSRIJS/QAIJSWFS) WAITRCD(600)
<<SNIPped many others>>
QAIJSMST 5 DB TOFILE(QUSRIJS/QAIJSMST) WAITRCD(600)
CRPence on Tuesday, November 05, 2013 1:45 PM wrote:
<<SNIP>>
I do not know what 8=Command List does, but it seems to me that
another possible approach is to determine if it even makes sense
that the opt-8 action should hold the record lock(s) "until the
8=command list is exited." Of course the actual
design\implementation dictates what occurs, but a logical inference
from a reviewer perspective is worthwhile to consider\suggest...
just as much as suggesting a shorter wait time.
As for the timeout, what is the _Maximum record wait time_
(WAITRCD) setting on the file? Apparently WAITRCD(600); per DSPFD
results? If so, that implies the effect is likely customizable
without any code or definitional changes to the feature; i.e.
effect CHGPF [or CHGLF] WAITRCD(1) to specify your own desired
effect.
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.