Partial updates in a RPG SQL programme -- RPG400-L

We have a batch job which writes up to 2000 records to a file and once the 
batch is finished these records have their status updated from LOT to INI , 
thus releasing them to a monitor for further processing. This monitor then 
updates the status from INI to CRS by SQL and  each record  with a status CRS 
is processed accordingly by calling the appropriate programme which processes 
this record type. From what we can determine from the journal,the SQL does not 
update all the records from INI to CRS such that the moniteur would appear to 
process the remaining ones as a 'seperate batch' in a subsequent cycle.

This is causing a duplicate key problem later on in the processing.

In orange is the batch reference, the last 4 digits being a  serial number 
within the batch. 

As one can see from the Journal the update for serial number 1373 from INI to 
CRS (in blue) was several minutes before the update for serial 1374 (in green) 

 

       TIMESTAMP              Job      SUBSTR(Data)showing bath no/serial no   
Status                 

                              NUMBER                                            
               

 2006-10-25-02.32.41.804944  160.765   753SW20061025000038000000000001373POSTIT 
   LOT         

 2006-10-25-02.32.41.804944  160.765   753SW20061025000038000000000001373POSTIT 
   INI         

 2006-10-25-02.32.41.815824  160.765   753SW20061025000038000000000001372POSTIT 
   LOT         

 2006-10-25-02.32.41.815824  160.765   753SW20061025000038000000000001372POSTIT 
   INI         

 2006-10-25-02.32.41.815984  160.765   753SW20061025000038000000000001375POSTIT 
   LOT         

 2006-10-25-02.32.41.815984  160.765   753SW20061025000038000000000001375POSTIT 
   INI         

 2006-10-25-02.32.41.816160  160.765   753SW20061025000038000000000001374POSTIT 
   LOT         

 2006-10-25-02.32.41.816160  160.765   753SW20061025000038000000000001374POSTIT 
   INI         

 2006-10-25-02.33.00.261632  125.090   753SW20061025000038000000000001372POSTIT 
   CRS         

 2006-10-25-02.33.00.262224  125.090   753SW20061025000038000000000001373POSTIT 
   CRS  blue       

 2006-10-25-02.42.05.996768  125.090   753SW20061025000038000000000001373POSTIT 
   TRT         

 2006-10-25-02.42.06.107264  125.090   753SW20061025000038000000000001372POSTIT 
   TRT         

 2006-10-25-02.50.21.532016  125.090   753SW20061025000038000000000001374POSTIT 
   CRS  green       

 2006-10-25-02.50.21.538368  125.090   753SW20061025000038000000000001375POSTIT 
   CRS         

 2006-10-25-02.50.24.401280  125.090   753SW20061025000038000000000001375POSTIT 
   TRT         

 2006-10-25-02.50.24.446672  125.090   753SW20061025000038000000000001374POSTIT 
   TRT         

 

 

The SQL in in question is performed from an RPGLE SQL programme (the monitor) 

 

The SQL is optimised 

 

I have noticed many cccurences of the following message in the log. 

 

Origine  . . . . . . . :   FO_EXP853     Gravité  . . . . . . . :   00        

 Type de message  . . . :   Information                                        

 Date d'envoi . . . . . :   30/10/06      Heure d'envoi  . . . . :   16:04:01  

                                                                               

 Message . . . . :   Outer QQQQUERY starting over with CQE before OPTIM.       

 

Does anybody have any idea  what is going on here , as we pretty sure that this 
is not a programme bug as such.