Atomicity: a transaction's changes to the state of resources are atomic; either all happen or none happen.
Consistency: a transaction is a correct transformation of the state. The actions taken as a group do not violate any of the integrity constraints associated with the state.
Isolation: even though transactions execute concurrently, they appear to be serialised. It appears to each transaction that any other transaction executed either before it or after it.
Durability: after a transaction completes successfully (commits), its changes to the state survives failures.
Top
See
servlet
for comparison.
Although "high-level assembler" is now used, the "high-level"
refers to the ability to code "freestyle" i.e. use lower case letters
within instructions, use more than 8 characters for variables or labels
and instructions no longer have to be coded in specific positions
on the line. However, the instructions used are still the pneumonic
representation of the actual machine instructions.
There are different types of APAR. Highly pervasive (HIPER)
APARs are for serious problems, which lead to loss of availability
of the software product or even the whole system. Problems
which can affect data integrity are also usually marked as
HIPER.