Hein is in the house :-) (was Re: Recommended HP COBOL way to exit a paragraph or perform early?)
- From: "Richard Maher" <maher_rj@xxxxxxxxxxxxxxxxxx>
- Date: Tue, 4 Sep 2007 19:24:39 +0800
Hi Hein,
Thanks for the reply.
It couldn't. RMS journalling simply keeps all records touched until
commit or rollback. Safe but expensive. Much like manual locking.
Sounds great! Transparency is mostly good.
So COBOL programmers like Paul now need to know (I think Paul said he was
already doing this) that they have to do something like: -
perform with test after until not hard_lock and not soft_lock
cobol i/o verb
maybe stick a lib$wait or retry_count check here (or do it globally in
the Declaratives section)
end-perform
Speaking in terms of the Rdb Rosetta Stone, what Isolation Level does RMS
achieve for its transactions? I normally would assume the basic Read
Committed but RMS just keeps getting better and better so is Repeatable Read
obtainable? Or even Serializable, where if I've previously touched index
nodes for (all records where key(2) Surname starting with "SM") does RMS
lock out all other processes/streams from inserting/writing another "SMITH"?
if your node died?Does it then fire up a recovery process on another node in the cluster
Yes, On finding an ACE on the file on subsequent file access.
Ok, this is all sounding really sexy! I can understand that (on a single
node) the RMS Exec Mode Rundown handler will Rollback any outstanding
transactions that a process may have if/when that particular process gets
zapped. I can also understand that when faced with complete node failure a
subsequent Open of the file from another node would be able to trigger a
Rollback of the failed process' transaction. What I can't see happening is
RMS preventing other processes on other nodes (who had previously opened the
file before the dodgy node died) from seeing the "partial" updates of the
now dead process and *incorrectly* acting on their contents.
In other words "How has RMS implemented the "freeze" lock to stop other
processes on other nodes bypassing the Isolation level that (presumably
through beautiful VMS and inner-mode code) is available with single node con
figurations?
Hold on! Let's just go to pli$examples and see one Tom prepared earlier :-)
Cheers Richard Maher
"Hein RMS van den Heuvel" <heinvandenheuvel@xxxxxxxxx> wrote in message
news:1188875406.236763.181130@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Sep 3, 6:57 pm, "Richard Maher" <maher...@xxxxxxxxxxxxxxxxxx>then
wrote:
Hi Paul,
For example, (if you were not using manual locking) if you updated
stock-on-hand in a record in file_1 from 20 to 18 and then went on to do
other work/updates but before you committed your transaction, another
process subtracted 5 from the same stock-on-hand and committed its txn,
if your node died?
It couldn't. RMS journalling simply keeps all records touched until
commit or rollback. Safe but expensive. Much like manual locking.
you ROLLBACKed *your* txn, what's the stock-on-hand say?
20
Does it then fire up a recovery process on another node in the cluster
Yes, On finding an ACE on the file on subsequent file access.
Hein.
.
- Follow-Ups:
- Hein has left the building?
- From: Richard Maher
- Hein has left the building?
- References:
- Re: Recommended HP COBOL way to exit a paragraph or perform early?
- From: Richard Maher
- RE: Recommended HP COBOL way to exit a paragraph or perform early?
- From: Paul Raulerson
- Re: Recommended HP COBOL way to exit a paragraph or perform early?
- From: Richard Maher
- Re: Recommended HP COBOL way to exit a paragraph or perform early?
- From: Hein RMS van den Heuvel
- Re: Recommended HP COBOL way to exit a paragraph or perform early?
- Prev by Date: Re: cannot ssh login with expired password
- Next by Date: Re: If PL/I is the king of languages...
- Previous by thread: Re: Recommended HP COBOL way to exit a paragraph or perform early?
- Next by thread: Hein has left the building?
- Index(es):
Relevant Pages
|