Edward Jaffe wrote:
An instruction timings book is not intended for use by management.
Agreed, but some managers consider any activity not directly related to productive work (e.g., cranking out mindless code) to be suspect, and grounds for discipline, unless of course it's their idea to check into performance of a particular application.
As an extreme example, about ten years ago I worked on a consulting contract; they had a production job that ran close to 24 hours CPU time. Several months into the contract they asked a colleague to look at it; he moved one statement and got the CPU time down to 2 minutes.
For my own use I have a subroutine with TIMEUSED, that I can run at diverse times and load conditions, and it provides at least some indication of what's inefficient.
Gerhard Postpischil Bradford, VT ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
