>Are there disadvantages to ARITH(EXTEND)? Is the only reason to want interm= >ediate results to be compatible with older code is if you need to match pre= >vious less-accurate results? Is there a performance impact at ARCH(11) or l= >ower? -----Original > >Are there disadvantages to ARITH(EXTEND)? Is the only reason to want interm= >ediate results to be compatible with older code is if you need to match pre= >vious less-accurate results? Is there a performance impact at ARCH(11) or l= >ower?
COBOL users normally want the exact same results with a new COBOL compiler after recompiling, or it is a failed migration. ARITH(EXTEND) can give different results than ARTIH(COMPAT) or older compilers. More accurate, but wrong as far as many clients are concerned. ARITH(EXTEND) can be a little bit slower than ARITH(COMPAT), but we have had no complaints from users about this. Now for something completely different (yeah I'm an old Monty Python fan) let's talk about ARCH! "Is there a performance impact at ATCH(11) or lower?" There is not enough info to answer, but I can guess. If you are talking about moving from COBOL V4 to COOBL V6, ARCH(11) would be much faster! If you are asking about moving from COBOL V6 with ARCH(12) to COBOL V6 with ARCH(11), then yes, there is an impact, the programs will be quite a bit slower. Higher ARCH levels give better performance so using lower levels would be a 'performance impact'! If I guessed wrong about what you were asking, please let me know! Cheers, TomR >> COBOL is the Language of the Future! << ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
