|
Yes I was wrong once... and then smoke filled the laboratory......
In the case we really got pounded the *DTAARA is not journaled. The
access was from within an RPG program not a CL CHGDTAARA. The program
wasn't ending it was retrieving journal entries and posting the entry
number to the data area. (then doing other work with the data) All
prior tests had been run on systems with RAID disk and therefore disk
write cache. When we hit the first system with no write cache is when
we identified the problem. The two drives in the mirrored pair that had
the *DTAARA on it were at 100% busy while the other 4 pairs sat at 5%.
Soon as the *DTAARA was changed to a single record DB file we were off
to the races.
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.
midrange.com
