On 3/5/2013 3:32 AM, Miklos Szigetvari wrote:
Hi
We are using the CEE3DMP (LE dump) routine to dump the call stack in some C/C++
program to the SYSPRINT file
It is terrible slow, no CPU just wait (for what ?)
Without this CEE3DMP calls, the program runs in 6 seconds , with dump in 30
minutes, producing 70 small dump (every dump about 60-80 lines).
Well, it's hard to tell with what you've given us.
You do know that by default CEE3DMP writes to CEEDUMP DD,
not SYSPRINT, right? Also, there can be contention to the
dump dataset, whichever it is. So some possiblities:
* re-examine your CEE3DMP parameters (although based on
your comment, they are probably good), however, think
about:
* in your invocation of CEE3DMP, use a separate DDname
for each dump (FNAME parameter)
* pre-allocate these separate dump data sets
* perhaps your MSGFILE is causing contention; the default
DD name is SYSOUT; if you have changed it using run
time parameters, consider adding NOENQ, maybe:
MSGFILE(SYSPRINT,,,NOENQ)
* look at your collective runtime options; maybe there
are some bad choices / defaults for your environment
especially consider: ALL31, HEAPCHK, MSGQ, RPTOPTS,
RPTSTG, STACK, STORAGE, THREADHEAP, THREADSTACK,
TRAP, XPLINK, HEAPPOOLS as well as MSGFILE
Hoe this helps.
--
Kind regards,
-Steve Comstock
The Trainer's Friend, Inc.
303-355-2752
http://www.trainersfriend.com
* To get a good Return on your Investment, first make an investment!
+ Training your people is an excellent investment
* Try our tool for calculating your Return On Investment
for training dollars at
http://www.trainersfriend.com/ROI/roi.html
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
