Re: System shutting down due to memory overload

[Dave <dfx1@xxxxxxxxxxxxxx>]

Thanks for these replies, I had no previous knowledge of these system
parameters. If I understand correctly, it sent a message when there was 5%
storage remaining. The scenario I evoked actually happened apparently. I
say apparently because I wonder if I was told all of the circumstances. One
source said that it was during the daily backup, and the job that "caused"
the failure was running at the same time. This job just shut down
abnormally, but with an entry in the log which suggests to me that it was a
controlled shutdown. Anyhow, the developer who ran this "rogue job" got the
blame and the company was out of action for a whole morning. I'm not sure
it was fair to say it was his fault. Luckily, no heads have rolled - yet!

On Fri, 5 Aug 2022 at 15:31, Dave <dfx1@xxxxxxxxxxxxxx> wrote:

> Hello,
>
> What happens exactly on the i when a job uses so much memory that the
> system shuts down?
> Is it a controlled shutdown or does it just switch off?
> What protection is available from, for example, a batch test that goes
> wrong and creates too many records in a physical file resulting in a memory
> full situation?
> What protection do you yourselves have from such a scenario (apart from
> the programme responsible using his commonsense :-) ) ?