On 3/18/2015 10:53 AM, FAULHABER Michael wrote: > "another day another darling", so why do you mind that job1 runs two > days later again? Currently you look for job1, job2 and so on. I > suggest (just for the analysis) to add job and date to one key. So in > the next step you care for the key with the highest phase number.
That's exactly what I did first when I found out I was missing reruns, but it gave me too much output. I don't care how many days a run takes. I just want to know the current status of each one. Oh, and I just noticed the reason I needed that extra record at the start of the file: SELECT SECOND was in effect when I issued the WRITE. That has another unwanted effect of writing a null record at EOF. Instead of adding a record with LITERAL, what I need is to remember to SELECT FIRST before that WRITE. ¬R
