I was thinking of batch in z/OS terms, ware there is a distinction. If the OS does not have this distinction then you would treat batch and interactive the same for error handling.
-----Original Message----- From: Adam Thornton [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 28, 2003 1:12 PM To: [EMAIL PROTECTED] Subject: Re: Memory access faults. On Tue, 2003-10-28 at 14:54, Fargusson.Alan wrote: > The answer to this may be: it depends. > > In a batch program it is probably best to abort the program. > In a windowing environment it might be best to ask if the user wants > to continue. Timesharing users might want an option to tell programs > to continue (maybe an environment variable?). Well, OK, but if it's contingent, then there isn't a single best answer, and so you're back to putting it at the feet of the app programmer. The OS won't necessarily know whether I'm an interactive or batch user. Heck, some of my programs, running at the same time, in the same environment, may be considered batch or interactive, simply depending on how I am working with them that day. Adam
