Re: Profiling RPGLE programs

TRCJOB
Depending on the job you want to trace you may also need STRSRVJOB.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Alan Campin
Sent: Wednesday, February 19, 2020 1:37 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Profiling RPGLE programs

CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know
the content is safe.


File I/O or SQL? If SQL, run your SQL statements through Visual Explain.
There is a program trace utility from IBM. I am trying to find out what the
name is. Maybe somebody else knows. .

On Wed, Feb 19, 2020 at 10:13 AM Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
wrote:

I normally eyeball the code, identify likely culprits and have it write

to

the joblog. I iterate thru that process until I narrow down the cause.

HTH



-----Original Message-----
From: Roger Harman [mailto:roger.harman@xxxxxxxxxxx]
Sent: Wednesday, February 19, 2020 11:04 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx

Subject: Profiling RPGLE programs

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








--
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@xxxxxxxxxxxx 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@xxxxxxxxxxxx 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@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com