On the one hand it might be easy to accept a product that is of limited or no use in certain environments or under certain conditions. The same thing could be said for an increase in resource costs that frequently accompanies upgrades.
However, this is not a product we just brought in house and found that we needed to change SOPs to fully utilize it. This is something that has worked day in and day out under our normal configuration. In my two years of nearly daily use I have encountered a handful of "optimize" issues that I could circumvent on an as needed basis. The same can be said for my several years of Xpediter use. In reality an increase in CPU could be absorbed and maybe not even noticed (even though one ususally expects the higher costs to bring additional functionality). Then there is perception. Questions will be asked. Are there good answers? Why did it work before? Are you sure this isn't an operating system issue? We can't optimize our COBOL? We need to add another compile to our cutover procedures? We need to retest everything after the last compile? We are promoting load module we have not tested? What surprises will the next upgrade bring? Paul P ---------------------------------------------------------------------- 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
