freeze

(redirected from blood frozen)
Also found in: Dictionary, Thesaurus, Medical.

freeze

1. Meteorol a spell of temperatures below freezing point, usually over a wide area
2. the fixing of incomes, prices, etc., by legislation

freeze

[frēz]
(engineering)
To permit drilling tools, casing, drivepipe, or drill rods to become lodged in a borehole by reason of caving walls or impaction of sand, mud, or drill cuttings, to the extent that they cannot be pulled out. Also known as bind-seize.
To burn in a bit. Also known as burn-in.
The premature setting of cement, especially when cement slurry hardens before it can be ejected fully from pumps or drill rods during a borehole cementation operation.
The act or process of drilling a borehole by utilizing a drill fluid chilled to minus 30-40°F, (minus 34-40°C) as a means of consolidating, by freezing, the borehole wall materials or core as the drill penetrates a water-saturated formation, such as sand or gravel.
(physical chemistry)
To solidify a liquid by removal of heat.

freeze

Terms used in referring to arrivals that have been assigned ACLTs (actual calculated landing time) and to the lists in which they are displayed. See also actual calculated landing time.

freeze

To lock an evolving software distribution or document against changes so it can be released with some hope of stability. Carries the strong implication that the item in question will "unfreeze" at some future date.

There are more specific constructions on this term. A "feature freeze", for example, locks out modifications intended to introduce new features but still allows bugfixes and completion of existing features; a "code freeze" connotes no more changes at all. At Sun Microsystems and elsewhere, one may also hear references to "code slush" - that is, an almost-but-not-quite frozen state.

abend

(ABnormal END) Pronounced "ab-end." An abend is an unexpected termination that causes the computer, smartphone or tablet to stop responding. The abend occurs either when the processor is presented with instructions or data it cannot recognize, or a program tries to address memory beyond a defined boundary. Abends are generally the result of erroneous software logic in the application or operating system (see anomaly).

Crash, Freeze, Lock Up and Hang
A "crash" occurs when the computer issues a "fault" and deliberately halts that line of execution. The terms "freeze," "lock up" or "hang" may refer to software that is actually still running but has erroneously wound up in an endless, internal loop that renders the program useless. In practice, the terms "crash," "freeze," "lock up" and "hang" are used synonymously. See infinite loop.

Bad Hardware Can Look Like Bad Software
A serious hardware failure will stop a computer-based device that has no redundant components. For example, a short circuit on the motherboard will halt the operation; however, a failing memory cell can cause an instruction to point to an erroneous location, making it look like a software failure.

It Depends on the OS
If the abend occurs due to a bug in an application and the operating system is not resilient, the computer locks up and has to be rebooted. Modern operating systems attempt to halt only the offending application and allow the remaining applications to continue. As operating systems evolve through the years, they become more bug-free themselves and more tolerant of application bugs. However, all operating systems are not 100% foolproof, and bad applications do cause operating systems to crash; a major motivation for virtualizing computers (see virtualization and virtual machine).

A Miracle It All Works
If you consider what goes on inside a computer, you might wonder why it does not crash more often. An ordinary home computer can easily have 64 billion memory (RAM) cells. Every second, millions of them switch their status between charged and uncharged (1 to 0; 0 to 1). If only one cell fails, it can cause an instruction to be invalid, and an abend can occur. See head crash, GPF, active area and transistor concept.



Abending
The green blocks are machine instructions executed by the CPU one after the other until a branch (jump) instruction breaks the sequence and points to an instruction elsewhere in the program. Abending (crashing, hanging, etc.) occurs when the program erroneously points outside of its address space, typically due to bad logic.