On 12/2/2010 6:42 AM, Don Poitras wrote:
The question was, is there a business case for execution about 2G? If CICS isn't putting it's _data_ above 2G, then putting the code up there isn't going to help much. Could the executable size, even for a large CICS address space be more than a few hundred megabytes?
Recently, a large U.S. Government customer asked us if our product(s) would still work if the LPA-eligible modules were moved from PLPA to LNKLST. They're running the latest operating system releases (often participating in the ESP process), the latest subsystems and middle-ware, and are so storage constrained at 2G they're scraping the bottom of the barrel!
I'll take VSCR from wherever I can get it. Leveraging 64-bit private storage for data is a given, and easy to manage with the new storage services introduced with z/OS 1.10. Also, leveraging 64-bit common storage should be a priority for product developers these days. ECSA in large production environments can be huge and common storage takes away from private.
IMHO, there is a lot that can and should be done before we get too worried about whether RMODE(64) executables are necessary.
-- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 310-338-0400 x318 [email protected] http://www.phoenixsoftware.com/ ---------------------------------------------------------------------- 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
