It is an issue due to the customer base. During a previous trial at a
large software shop, my code would occasionally log messages to its log
indicating it could not keep up with the volume of activity being
generated on the machine. Yet, at other shops, it could handle the
volumes just fine. This is just one of the items that can affect
performance, but if I can detect the trap is on, it is at least one
known item out of the way.
--Dave Day
On 5/17/2012 6:37 AM, Peter Relson wrote:
Why is this an issue?
No one should be running with that DIAG trap (or almost any DIAG trap) on
in a production environment, and if not in a production environment, who
cares?
The whole point of these traps is to be used in environments where you can
afford to sacrifice performance.
Peter Relson
z/OS Core Technology Design
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
