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

[VAXman- at SendSpamHere.ORG]

In article <e5ee91c0-5b97-44b0-ac45-faac78537556 at e13g2000vbn.googlegroups.com>, AEF <spamsink2001 at yahoo.com> writes:
>On Apr 11, 3:27=A0pm, Simon Clubley <clubley at remove_me.eisner.decus.org-
>Earth.UFP> wrote:
>> On 2013-04-11, Paul Sture <nos... at sture.ch> wrote:
>
>> > In article <kk6s8q$39... at dont-email.me>,
>> > =A0Simon 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. =A0If 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.
>
>"Walkies"? What's that?

Walkies:  lost or missing.


-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

Well I speak to machines with the voice of humanity.