[Info-vax] Are queue manager updates written to disk immediately ?

[Jan-Erik Soderholm]

Simon Clubley wrote 2013-04-11 18:28:
> On 2013-04-11, Jan-Erik Soderholm <jan-erik.soderholm at telia.com> wrote:
>>
>> I guess accounting (acc/queue=ba0) also shows both jobs as runed?
>
> There's no accounting entry for the first job even though there is
> a full logfile, but since accounting log updates are buffered, then
> that's not really a major surprise.
>
>> Nothing weird with the start/finish timestamps in accounting?
>>
>> I would look mare at something with the system clock at
>> startup that made the holding job to be released. Such
>> as a startup with wrong time setting or similar.
>>
>
> All the timestamps on the log files and accounting are correct; the only
> time the system clock is corrected on this system is once a day during
> during the night from a NTP source and that job had already run a couple
> of hours previously.

But there was a reboot in between, not ?

> In addition, the queue entry number from the accounting record for the
> second job didn't match the entry number from the submit command in
> the first job.

Higher/later or lower/earlier?

Does it match the entry number from *any* previous job ?
I don't know ho long you keep logs, of course... :-)

Sounds like the quemgr thought that the job hadn't been
run (or hadn't completed) and simply restarted it.

But then, will a restarted batch job not run using the
original entry number? Maybe not...

I would expect the queue database to be updated syncronisly
at the time of batch job "rundown". That is where SHOW QUEUE
looks, not?

Weird.
I guess this could be simulated on a test system. :-)

Jan-Erik.


>
> Thanks for the suggestions however, I do appreciate them.
>
> Simon.
>