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

[Simon Clubley]

On 2013-04-11, Paul Sture <nospam at sture.ch> wrote:
> In article <kk6s8q$39e$1 at dont-email.me>,
>  Simon Clubley <clubley at remove_me.eisner.decus.org-Earth.UFP> wrote:
>> 
>> Even if there was some queue manager bug caused by a power failure
>> during some unusual tight timing window of a few milliseconds [*],
>> that still does not explain the disappearing job from the submit
>> command in the first job.
>> 
>> Simon.
>> 
>> [*] A few milliseconds maximum, because don't forget I have a _full_
>> logfile from the first run of the job today.
>
> That sounds like a small window in the batch run down code.  If you 
> think about it there must be a point between the batch job completing 
> and its return status being processed so that the queue manager either 
> deleting or retaining the job in the queue database.
>

The problem with the window theory is that while it explains a repeating
job, it doesn't explain why the submit from the first run went walkies.

_If_ the queue manager is not delaying the on disk updates, then I wonder
if I have come across more than one problem here.

It will be interesting to see what HP have to say.

Thanks everyone,

Simon.

-- 
Simon Clubley, clubley at remove_me.eisner.decus.org-Earth.UFP
Microsoft: Bringing you 1980s technology to a 21st century world