I would list every process:
myjob1.prg start 99:99 99/99/9999 *(a little ctr showing records or keys)
myjob1.prg done 99:99 99/99/9999
myjob2.prg start 99:99 99/99/9999 * (will show key at error point)
myjob2.prg abort 99:99 99/99/9999
myjob3.prg start 99:99 99/99/9999 * (last key processed)
myjob3.prg done 99:99 99/99/9999
.... more ...

I understand that pending seems important. But these are queued process. You could say next years annual summary is a pending process. Jobs start the run the fail or they finish normally. This is a single thread queue right? The only reason a job would be pending would be if the necessary resources were not available. Why queue a job if it's know it will fail? Have someother timer guy check for necesaary resources. When all the resources are there and all the "programatic" assessments assure the job has a likelyhood of success, then move the job from pending to the queue. Maybe two lists - one of current and processed histpry and another that cannot be queued!



>>The other way around:
>>
>>"Batch Processes: Done"
>>"Batch Processes: To Do"
>
>I have another problem. I need to create 4 new properties for my txtDate class. The UpperBound date and the LowerBound date. If I set them it would mean that my date should not exceed upper bound and should be greater than lower bound. I also need to have error messages for each case, e.g. sort of "Upper" message and "Low" message.
>
>I can have dUpperBound and dLowBound, though I don't not really like these names either. But I'm not sure what to use for messages?
>
>What would you suggest?