So far it seems like something I can work on that can be done in stages and I can learn a lot in the process. First getting the SRB working, then reading a bit of memory, then adding recovery routines, etc.
So far all my other "great" ideas required a huge effort before getting any results at all. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Gerhard Postpischil Sent: 19. elokuuta 2008 20:36 To: [email protected] Subject: Re: A couple of memory/storage questions Lindy Mayfield wrote: > So you mean that if I read a control block that points to another one, > etc, and this points to memory, then I need to basically stop the > address space from doing anything until I'm all done reading. Is that > about right? I've been doing this for more than twenty years without holding any locks. The code in the SRB establishes an FRR, and the recovery routine decides what to do - quit with an error condition (and originator can retry later), or retry immediately (with a counter to prevent indefinite recursion). What's more interesting is getting information from address spaces that are not available (e.g., timesharing session in a terminal input wait). Gerhard Postpischil Bradford, VT ---------------------------------------------------------------------- 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
