>>So, what is the point, on today's fast machines, about worrying about the >>>>optimisation of the small stuff?
This statement makes no sense at any level. What constitutes "user code"? Does that only apply to instructions that I've personally crafted? If I read/write an unblocked file, is there no room for improvement simply because I cause an access method to perform an I/O hundreds of more times than I need to? More importantly, why distinguish between a service that a user would have to perform anyway, versus one that is provided by the system? Does microcode count, or only hardware implemented instructions regarding "user code"? If I invoke a REXX built-in function is that user code or vendor code? More importantly you're ignoring the fact that coding is rarely a singular issue, but rather it involves poor designs and implementations. Even if this percentage could be corroborated based on some arbitrary definition of what delineates "user" from "system" code, the point is irrelevant. Systems behave as an aggregate of their code and the requests that are expected to be satisfied. To treat any of them in isolation completely misses the point. Adam ---------------------------------------------------------------------- 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
