Modifying Richard Ecuyer's example from February 2006:the API calls or in the DSPLY statement, I added a couple of timestamps,
c Eval pm_counter=1
c movel 'QDBUDR ' Pm_CSEntry
and then, if the first QMHSNDPM call fails with CPF2479, calling it
c movel 'QDBPUT ' Pm_CSEntry
I get the name of the program that immediately tripped the trigger.
I noticed a lag in the response time, so to determine whether it was in
one before the first QMHSNDPM call, and one after the QMHRCVPM call,DSPLYing them both just before the final DSPLY with my result, and found
that the API calls only took 2-4 milliseconds on a "slim" 170 runningV4R4, so I guess I'm OK on time.
stack level beyond the QDBUDR/QDBPUT call might fail to return the
But can anybody think of a case (or an OS release) where climbing one call
right program? Or explain why Ecuyer's example just climbed a straight 5call stack levels, overshooting the target by 2 levels?
James H. H. Lampert
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
No virus found in this incoming message.
Checked by AVG.
Version: 8.0.101 / Virus Database: 270.6.14/1646 - Release Date: 1-9-2008
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.