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