× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I'm trying to use the job trace exit program support on V5R1. It doesn't
seem to be working right. Have looked at the APAR knowledge base and the
software knowledge base at iSeries support.

I name a program on the TRCJOB command. This program only takes the trace
record and puts it into a user queue.

This is done so that as little time as possible is spent in processing the
data, so that there is minimal chance of losing trace records.

But some of the data is missing, like number of reads, writes,
instructions, CPU time. These items DO show up in the spoled file that you
get when you *OFF the TRCJOB.

Here's an example, the spooled file and a dump of the user queue that
corresponds.

  5722SS1 V5R1M0  010525                         AS/400 TRACE JOB INFORMATION
   TRACE TYPE  - *ALL     MAX STORAGE- 04096      EXIT PROGRAM-
xxxxxxx   /TESTTRCJOB
   RECORD COUNT- 000096   START TIME - 11:10:44   START DATE  - 03/08/02

                                                                                
    DB
NON-DB   PAGES     NUMBER
TIME         THREAD   SEQNBR FUNCTION PROGRAM LIBRARY ENTRY EXIT CALL LVL
CPU TIME READS   READS    WRITTEN   WAITS
11:10:44.423 00000004 000001 RETURN   QUOCMD  QSYS    0127  00F1
08       0.079    0       9        2         0


QUEUE
MESSAGES-

.
00001-

   .ENQUEUE DATE-              03/08/02    ENQUEUE
TIME-              11:10:44

   .MESSAGE-

   000000   000883EA A4647078 9170D8E4 D6C3D4C4   40404040 D8E2E8E2
40404040 40400008  *  c²uÀøÌjøQUOCMD    QSYS        *
   000020   00000000 00000000 00000000 00000000   00000000 00000000
5CD54040 40404040  *                        *N      *

The first byte (00) is for program flow.
The second (08) is for RETURN.
The next 8 (83EA A4647078 9170) are a timestamp - don't know which kind,
internal or otherwise.
The next 20 (D8E4 D6C3D4C4   40404040 D8E2E8E2 40404040 4040) are program
and library name (QUOCMD    QSYS).
The last byte on line 1 (08) is the call level.

The second line is the problem. It should have all the data for ENTRY,
EXIT, CPU TIME, DB READS, NON-DB READS, PAGES WRITTEN, and NUMBER WAITS.
(The 3 *N's are for module, module library, & procedure name.)

But all the bytes are 00.

What's up?


Vern Hamberg

Would you like to see a challenging little arithmetic puzzle
that might get you or your kids or grandkids more interested
in math? Go to <http://cgi.wff-n-proof.com/MSQ-Ind/I-1E.htm>

Sillygism--

Something is better than nothing.
Nothing is better than a ham sandwich.
Ergo
Something is better than a ham sandwich.



As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.