|
Hello,
can anyone help me ?
From: Uma Balasubramanian on 09/23/2002 02:53 PM
To: rpg400-l@midrange.com
cc:
Subject: How to analyse Job Trace
Hi,
A) I am using Trace Job Tool in the following manner:
> STRJOBTRC
> Call Program_Name (RPGLE program with just Keyed delete in a do loop for
deleting 6 records - hardcoded the key value)
> ENDJOBTRC MBR(MyMember) LIB(MyLib)
> PRTJOBTRC MBR(MyMember) LIB(MyLib) RPTTYPE(*SUMMARY)
There are 6 records in the physical file with the same key value hardcoded
in the program. After the program is run, these 6 records are not present
and the file is used only by my program
B) I get the following Information:
Trace Analysis Summary Output
P H Y S I C A L I / O
SECONDS CPU SECONDS DB READS NON-DB RDS
WRITES WAIT
WAIT-ACT 3.538
ACTIVE .023
67 14 1
WAIT-ACT 3.487
ACTIVE .138
5 2
WAIT-ACT 9.434
AVERAGE .058
36 7 2
TOTAL .115
72 14 3
Trace Analysis I/O Summary Output
P R O G R A M ******* PROGRAM DATA
BASE
SECONDS SEQNCE NAME CALL INIT GETDR
GETSQ GETKY GETM PUTM
WAIT-ACT 3.538 144
ACTIVE .023 645 QUOMAIN 2
9
WAIT-ACT 3.487 650
ACTIVE .138 896 QUOMAIN
WAIT-ACT 9.434 901
AVERAGE .058 2 1
5
TOTAL .115 2
9
UDR OPN CLS OPN CLS READS WRITES MSGS
6 1 1 1 8 5
1 2 12 4
3 1 1 2 10 5
6 2 1 3 20 9
C) My Question
a) Why CPU Seconds is not shown in Trace Analysis summary ?
b) Why no DB Reads in Trace Analysis summary ?
c) Why My program name is not listed in Trace Analysis I/O summary and only
QUOMAIN is shown?
d) What is the significance of these UDR, OPN, CLS, OPN, CLS, READS, WRITES
and MSGS fields in Trace Analysis I/O summary ?
e) Does the total .115 seconds indicate response time ?
f) How to know which of the lines in Trace Analysis I/O summary is
corresponding to my program ?
g) How to analyse this further for performance improvement ?
Can kindly anyone help me ?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.