Hello John, One "thing" which happened to our CICS transactions after we increased our ECSA size were "random" wild branches.
Not every instance of a transaction would break.....but many did. Why? Increasing our ECSA size moved the EDSA up the region, so that many transaction programs etc were being loaded higher up in memory. The transaction that broke were accessing storage above "1,000,000,000". The transactions, written in COBOL, were making use of the ADDRESSING (I think I have that correct), but had been compiled with TRUNC(OPT). The COBOL variable to hold the address was adequate for a hex number, but were being truncated at the high order because the arithmetic was being performed in decimal. Addresses greater than 9 digits were being used. We re-IPLd with smaller ECSA to allow more of the transactions to complete....until all affected programs had been recompiled with TRUNC(BIN). We were able to expand our ECSA safely about 6 months later. Regards Bruce Hewson ---------------------------------------------------------------------- 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
