not for private storage without specific code to keep the storage around. Several threads in the last couple of months detail storage allocation. CSA/ECSA are true shared memory but most of that is now fetch protected (since MVS/ESA IIRC) Most application programs are compiled RENT now and expect the memory to be initialized to binary 0's. Some programs even count on it.
Mike On 5/19/05, Dave Thorn <[EMAIL PROTECTED]> wrote: > A customer (through an auditor) has posed a question to us: Job 'A' runs > and ends. Job 'B' then comes in and obtains some of the system storage > that Job 'A' had. The question is, can Job 'B' see data in that memory > originally owned by Job 'A'? > > Theoretically, yes, right? Is there a way to prevent this? (which I'm > sure will be the followup question) I know this sounds a little silly but > it seems to be a concern to someone. > > Thanks in advance for any insights. > > > Dave Thorn > Senior Technology Analyst > SunGard eSourcing > 600 Laurel Oak Road > Voorhees, NJ 08043 > Office 856-566-5412 > Fax 856-566-3656 > Cell 609-781-0353 > Email [EMAIL PROTECTED] > ------------------------------------------------------------------------- > Keeping People and Information Connected (TM) > HTTP://www.availability.sungard.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 > -- Mike ---------------------------------------------------------------------- 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
