Martin Kline wrote: >I've always interpreted that 'first time' reference to only include things that actually happen. For example: programming errors occur, so there must have been a FIRST program error, or bad vendor products are sold, so there must have been a first bad product. But to assume something bad that has not happened will eventually happen is a pessimistic view of things. Although less likely to occur, I could use the same logic to assert that there will be a first time for the planet Earth to suddenly leave its orbit around Sol, change to antimatter, and instantaneously transport itself across the universe. The first time that happens, my boss won't be very happy either.
>Nevertheless, part of my responsibility in undertaking such a potentially dangerous task is to do everything I can to ensure there is no first time failure and subsequent unpleasant boss zapping. Here I agree to agree with you! Thanks for sharing your view. I've also done potentially dangerous tasks just to keep things up and running and to avoid first time failures. You'll have to balance things with all available information and risks and then decide how to take matters further including zapping or IPL. Just like you and others I have to invent solutions to a 'first time' problems. Please keep up with your postings on this list! ;-D Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- 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
