Edward Gould wrote: >The following Christmas party I got brave and went over to the CEO and got >into a conversation about the issue.
Wow! You're that brave! >... The VP said that is all we don’t have to upgrade our machine? ... I said >one caveat, and I saw everyone look at me, and I said this issue would need to >be implemented by program redesign. I said the programming area would have to >be involved. I thought I heard someone get out a gun but it was something like >a sigh. I got the COBOL upgrade, and we pushed the end of the day back about >an hour. A few months later we were told we were going to get a major hardware >upgrade and software as well. Great! You deserve a medal! I have seen that scenario a few times in my career. Something breaks or is causing high CPU, excessive memory usage and swapping or slow transaction response time. Result - everyone screamed for a major upgrade (hardware or software) Sometimes a simple redesign of a program resolved most of the problems. One example - I have handled a bad program problem scenario. It repeately opened a VSAM dsn, do its thing and close. Repeat - wash, rinse, repeat all of this. Result - slow program, slow transaction times and lots of RACF SMF records (access attempt) and SYSLOG messages. I told the programmers after looking at their programs, just please move the OPEN outside the loop and the CLOSE after the loop. Voila, all were happy. ... no, I did NOT get a T-shirt ... ;-) Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
