All,
I've got a strange problem, it seems as if SETLL is performing very, very slow.
Looking at the call stack for my job it mostly stays here:
Program
or
Procedure Library Statement
CV142C HLTHQALIB 0000005200
PEP_CV142R HLTHQALIB
CV142R HLTHQALIB 0000023800
ILDRECORDS HLTHQALIB 0000063100
X_DB_SETLL QSYS 0000000189
QDBGETKY QSYS 078F
Statement #63100 is a SETLL using 4 of 5 keys one a logical.
This program is reading data from a physical using one of two logicals, The
SETLL is being used to
determine if there are any child records for a given record. So the main
logical contains no children
records and the other logical has just children.
During my initial tests, there were no children, so the logical being hit by
the SETLL would have been
empty. During those tests, the program performed very fast. 55,000+ records
in seconds. Now, it is
only doing a dozen records a second.
Anybody seen any instances where SETLL performs very poorly?
Thanks,
Charles Wilt
--
Software Engineer
CINTAS Corporation - IT 92B
513.701.1307
wiltc@xxxxxxxxxx <
mailto:wiltc@xxxxxxxxxx>
This e-mail transmission contains information that is intended to be
confidential and privileged. If you receive this e-mail and you are not a
named addressee you are hereby notified that you are not authorized to read,
print, retain, copy or disseminate this communication without the consent of
the sender and that doing so is prohibited and may be unlawful. Please reply
to the message immediately by informing the sender that the message was
misdirected. After replying, please delete and otherwise erase it and any
attachments from your computer system. Your assistance in correcting this
error is appreciated.
As an Amazon Associate we earn from qualifying purchases.