|
On May 6, 2021, at 6:33 AM, a4g atl <a4ginatl2@xxxxxxxxx> wrote:
Thanks Patrik,
I know what the file is used for, but the question is why is the system
doing so much I/O on this file? Normally, it is very low in CPU
utilization. I checked some production systems and the CPU utilization is 0.
Does someone know how to fix this?
I will start with a RCLSTG this morning.
I did do a RCLDBXREF and that responded immediately with no issues. The
*FIX option returned no issues.
Thanks, Darryl.
On Thu, May 6, 2021 at 4:45 AM Patrik Schindler <poc@xxxxxxxxxx> wrote:--
Hello Darryl,
Am 06.05.2021 um 03:43 schrieb a4g atl <a4ginatl2@xxxxxxxxx>:this?
Going through WRKACTJOB,QDBSRVXR had an abnormally high CPU count. I
displayed the job DBSRVXR and it has a very high I/O count for the cross
reference file QADBXLFN with the count well over 100 million. Why is
each
I see the 2 jobs alternating state between RUN and DEQW. The job QDBSRVXR
is always in a RUN state and consumes about the same CPU as the 2 jobs
around 15%.
Google turned up nothing really helpful.
https://www.ibm.com/support/pages/710-ibm-i-memo-users:
"Cross-reference logical files QADBXATR, QADBXDIC, QADBXFIL, QADBXLFI,
QADBXLLB, and QADBXLFN also reflect this field change."
Maybe it helps you to know that QADBXLFN is a "cross reference file"?
According to documentation I found, it is a logical file built by the
system over another system managed PF, QADBXREF.
Maybe the PF or LF is damaged or needs some "love", like RCLSTG?
Probably others can chime in from here.
:wq! PoC
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com
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.