Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Thu, 20 Feb 2003 @ 14:37:48 GMT


     
  <Prev Next>   <<First <Prev Next> Last>>  


Subj:   Re: User Queries holding out Batch
 
From:   Anomy Anom

<-- Anonymously Posted: Thursday, February 20, 2003 09:23 -->

We've run Mloads for years and I've never heard of putting a release mload in front of each job. What we do is to check for the existence of error tables AFTER the mload finishes, and if they're found then we force the job to abend. This gives us time to debug & clean up the problem prior to the next run. I can't imagine releasing an mload lock automatically without knowing what had gone wrong to put it into that state. I'd be curious why this methodology would be recommended...



     
  <Prev Next>   <<First <Prev Next> Last>>  
 
 
 
 
 
 
 
 
  
  Top Home Privacy Feedback  
 
 
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 27 Dec 2016