RSWWDHEX - Failed to restart

[Rick Sample]

After speaking with our basis folks we determined 
we had a unix hardware / software issue due to upgrades. 

I don't think this note would have made a difference since 
I see nothing about alerts. i.e. the program is not running, raise
alarm and 
notify someone. There was a reason that we could not do this with 
our TIDAL batch system but I don't recall the why. 

How do you monitor if RSWWDHEX is running and when it fails?
Depending on the time of day, 15 minutes not running could cause LOTS 
of headaches.

Thanks
Rick




>>> keohan at ll.mit.edu 3/15/2006 4:09:31 >>>
Hi Rick,

We had the a similar issue... RSWWDHEX failed to reschedule itself and

nobody knew about it....
Try OSS note 842246.

Regards,
Sue

Rick Sample wrote:

>In 4.6c SWWDHEX is scheduled to run. It failed to re-start 
>for some reason. (Still doing post mortem) It is scheduled via an 
>admin user ID in BASIS group.
>
>We have production control re-start instructions any time the system
is
>re-cycled 
>but since it died unexpectantly, know one was informed! 
>This is the second time in a matter of a couple of months it failed
and
>
>I think it is time to re-think how we monitor this job.
>
>I am curious to know how others monitor if this job is running? 
>
>Any suggestions welcome.
>
>Thanks
>Rick
>
>
>
>
>_______________________________________________
>SAP-WUG mailing list
>SAP-WUG at mit.edu 
>http://mailman.mit.edu/mailman/listinfo/sap-wug 
>
>  
>
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu 
http://mailman.mit.edu/mailman/listinfo/sap-wug