Recovering from an batch job failure

     We're a company that is downsizing from mainframe to AS/400.  We're 
     currently implementing BPCS V6.0.04 C/S but we're not yet live.
     
     One of the many problems we're struggling with is : how do BPCS shops 
     recover from a batch update program (= program that does file updates) 
     failure ?  On the mainframe we had a software that would automatically 
     back-out all the changes made by the failing job, so that data is put 
     back into that status of before the job started (BPCS doesn't have 
     such a feature ?).  This way (for batch jobs at night) other jobs can 
     continue with a consistent data base situation or (for batch jobs 
     during the day) on line users don't find their data inconsistent. 
     
     Another possibility is to restore to a back-up taken before the night 
     batch chain, but that solution is less elegant.  During the day it 
     would even be impossible, because updates made by the online users 
     would be discarded. 
     
     Can anyone share his experience with this topic ?  
     Possible answers I heard so far : 
     A BPCS shop simply doesn't have to run jobs at night, because  
     everything is run during the day ?  
     When a batch job during the day fails, the data is rectified manually 
     with DFU ?
     
     
     Luc De Bondt
+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---