That would only work if the virtual machine resets, which it would do if it is IPLed or it logs off. But, if it just dies and sits there without a VM or CP read (or the 15 minute timebomb is disabled) then your spool file wouldn't be sent.
Maybe your server could use the timebomb diagnose (diag 288) via the timebomb package on the VM download page. Then, if your server crashes, you wouldn't reset the timebomb and it would reboot. Of course, a better answer is use some kind of monitoring software (commerical product, a tool, or home grown) that would know that your server died and react accordingly. On Wed, May 4, 2011 at 1:29 PM, Paul Gilmartin <[email protected]> wrote: > I tend a service machine that mostly runs unattended, processing > work requests that are sent to its reader (email, actually, from > UNIX systems.) Yesterday, someone complained that his request had > not been processed. The service machine had crashed 32 days before! > > I can't diagnose it from the spooled console log -- our site purges > spool files after two weeks. > > So, I get a weird idea. In PROFILE EXEC: > > CP DEFINE PUNCH ... /* Not 00D */ > CP SPOOL ... to RSCS CONT > > Use NETDATA, etc. stages to create an email image addressed to > me, and leave it in the CONT spooled punch. > > When the server crashes, the punch will be closed and the > RSCS will deliver the email to me. > > o Will this work? > > o Is it abusive of system resources? > > o Is there a better way? > > Thanks, > gil > -- Bruce Hayden z/VM and Linux on System z ATS IBM, Endicott, NY
