Crap, I forgot to change the address so I did respond publicly. I hate when I do that.
From: smith5646midrange@xxxxxxxxx <smith5646midrange@xxxxxxxxx>
Sent: Thursday, September 4, 2025 1:02 PM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Sever pulling a bazillion rows from IBMi via JDBC (I think)
Without responding publicly...
I agree 100% but I can't seem to get anyone to listen. We have a problem with some short sighted people and the attitude is that it is not a problem.
There are many teams in the company that do not believe they need to get the admins or even the senior developers involved in designs. That is how this mess got installed in the first place.
Unfortunately, as a consultant, I can only voice the concern and move on. I do try to find fixes but if I get pushback on them, I am SOL. I can't even say "I told you so when it goes south". ☹
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx <mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx> > On Behalf Of Dan Bale
Sent: Thursday, September 4, 2025 11:53 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx <mailto:midrange-l@xxxxxxxxxxxxxxxxxx> >
Subject: RE: Sever pulling a bazillion rows from IBMi via JDBC (I think)
As a systems engineer, I know my team would be heavily involved in any job pulling 100% (or even 70%) of the CPU for hours. Any pushback as you're seeing that doesn't have a VERY GOOD REASON would have our IT director calling a Come To Jesus meeting.
I mean, seriously, a "select * from file"? They couldn't just send the entire file to the other server?
If you're waiting for SLAs to be missed, hopefully you are keeping the receipts.
Dan Bale
-----Original Message-----
From: MIDRANGE-L < <mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx> midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of <mailto:smith5646midrange@xxxxxxxxx> smith5646midrange@xxxxxxxxx
Sent: Thursday, September 4, 2025 11:23 AM
To: 'Midrange Systems Technical Discussion' < <mailto:midrange-l@xxxxxxxxxxxxxxxxxx> midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Sever pulling a bazillion rows from IBMi via JDBC (I think)
A lot of the responses to this question involved looking at the SQL analyzer.
I reread my question and I realized that I omitted the fact that it is pulling the entire file. I do not have access to the program source but apparently it is doing a "select * from file". No where clause, no order by clause. Just a full file pull in whatever order the IBMi hands it to them.
I have gotten nowhere in the discussion on this. The team receiving the data doesn't see a problem with our IBMi CPU being over 100% for hours at a time and therefore does not want to change anything. I'm dropping it for now. We will see if someone listens to the problem when holiday peak shows up and SLAs are missed because the machine is overworked pushing this data to the other server. :(
Thanks everyone for your thoughts.
*** CONFIDENTIALITY NOTICE: The information contained in this communication may be confidential, and is intended only for the use of the recipients named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please return it to the sender immediately and delete the original message and any copy of it from your computer system. If you have any questions concerning this message, please contact the sender. ***
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: <mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx> MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: <
https://lists.midrange.com/mailman/listinfo/midrange-l>
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: <mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx> MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at <
https://archive.midrange.com/midrange-l>
https://archive.midrange.com/midrange-l.
Please contact <mailto:support@xxxxxxxxxxxxxxxxxxxx> support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
midrange.com
