a few years back I was working for a company that was using the same logic to mass update a file as to handle an online update for one record
a cl program was being called over 50 million times that added a library to the library list, called a program and then removed the library from the
library list
it would have been really easy to change so that the library would been added at start and removed at end of job. even the program could have been
called so the cl wasn't needed.
sometimes looking at how it is being run helps
Dave Peters
----- Original Message -----
From: "midrange-l" <midrange-l@xxxxxxxxxxxxxxxxxx>
To: "midrange-l" <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: "Don Brown" <DBrown@xxxxxxxxxx>
Sent: Wednesday, February 19, 2020 1:56:28 PM
Subject: Re: Profiling RPGLE programs
Obviously as others have said the IO is where to start.
And while there are tools that may provide insight when I am faced with
this type of performance investigation I like to just add some debugging
of my own into the code to see what is happening.
And this also depends on the structure of the program if it is poorly
structured then adding debugging with time stamps and counters can provide
great insight.
When I say debugging I am either writing to the joblog or adding a printer
file and writing the details to that.
Good luck
Don
From: "Roger Harman" <roger.harman@xxxxxxxxxxx>
To: "Midrange Systems Technical Discussion"
<midrange-l@xxxxxxxxxxxxxxxxxx>
Date: 20/02/2020 03:04 AM
Subject: Profiling RPGLE programs
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>
I have a request from a sister division to look at (and, hopefully
improve) a program that is VERY long running - like 2 days long.
My first thought was I need to know the hot spots in the program but, in
all my years on this platform, I've never needed to profile a program.
Does anyone have any tips, a simple cheat sheet, or primer on the steps
involved?
Thanks!
Roger Harman
COMMON Certified Application Developer - ILE RPG on IBM i on Power
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.