In a recent note, Walt Farrell said: > Date: Fri, 20 May 2005 12:10:51 -0400 > > On 5/19/2005 12:41 PM, [log in to unmask] 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. > > For the answer to the auditor, I think you should focus on what happens > with normal application programs. For them, the answer is a definite > "no". And data that an unauthorized program places into memory that it > allocated in job A will not survive into job B. The initiator or other > system functions will free all of that application-related storage at > the end of each job step. > A paranoid might easily suspect that the (apparently naive) auditor was engaged with the task of spreading FUD about mainframes and proving that it's safer to have only one person using each computer.
-- gil -- StorageTek INFORMATION made POWERFUL ---------------------------------------------------------------------- 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
