GetWiki
Coupling Facility
ARTICLE SUBJECTS
being →
database →
ethics →
fiction →
history →
internet →
language →
linux →
logic →
method →
news →
policy →
purpose →
religion →
science →
software →
truth →
unix →
wiki →
ARTICLE TYPES
essay →
feed →
help →
system →
wiki →
ARTICLE ORIGINS
critical →
forked →
imported →
original →
Coupling Facility
please note:
- the content below is remote from Wikipedia
- it has been imported raw for GetWiki
{{short description|Hardware or LPAR that allows coordination among multiple IBM System/390 and IBM Z mainframes}}{{More citations needed|date=January 2021}}In IBM System/390 and IBM Z mainframe computers, a Coupling Facility or CF is a piece of computer hardware or virtual machine that coordinates multiple processors.A Parallel SysplexJOURNAL
- the content below is remote from Wikipedia
- it has been imported raw for GetWiki
, IBM Systems Journal
, S/390 Cluster Technology: Parallel Sysplex
, 36
, 2
, 1997
, 172â201
, 10.1147/sj.362.0172
, 0018-8670
,weblink
, IBM
, Nick
, J. M.
, Moore
, B. B.
, Chung
, J.-Y.
, Bowen
, N. S.
,
CONFERENCE
, S/390 Cluster Technology: Parallel Sysplex
, 36
, 2
, 1997
, 172â201
, 10.1147/sj.362.0172
, 0018-8670
,weblink
, IBM
, Nick
, J. M.
, Moore
, B. B.
, Chung
, J.-Y.
, Bowen
, N. S.
,
, International Conference on Parallel Processing, Honolulu, 15-19 April 1996
, Overview of IBM system/390 Parallel Sysplex - A commercial parallel processing system
, Nick
, Jeffrey
, Chung
, Jen-Yao
, Bowen
, Nicholas
, 1996
, 10.1109/IPPS.1996.508100
, 0-8186-7255-2
,weblink
, IEEE
,
MANUAL
, Overview of IBM system/390 Parallel Sysplex - A commercial parallel processing system
, Nick
, Jeffrey
, Chung
, Jen-Yao
, Bowen
, Nicholas
, 1996
, 10.1109/IPPS.1996.508100
, 0-8186-7255-2
,weblink
, IEEE
,
, The flexible solution to your enterprise computing requirements IBM Parallel Sysplex clustering technology
, GG221-4101-05
,weblink
, IBM
,
relies on one or more Coupling Facilities (CFs). A coupling facility is a mainframe processor (runs in an own LPAR, with dedicated physical CP, defined through Hardware Management Console (HMC)), with memory and special channels (CF Links), and a specialized operating system called Coupling Facility Control Code (CFCC). It has no I/O devices, other than the CF links. The information in the CF resides entirely in memory as CFCC is not a virtual memory operating system. A CF typically has a large memory â of the order of several tens of gigabytes. The CF runs no application software.
When originally introduced, the CFCC executed in a separate 9674 mainframe unit that was essentially a processor without I/O facilities other than the CF links. Later{hide}efn|on the , GG221-4101-05
,weblink
, IBM
,
relies on one or more Coupling Facilities (CFs). A coupling facility is a mainframe processor (runs in an own LPAR, with dedicated physical CP, defined through Hardware Management Console (HMC)), with memory and special channels (CF Links), and a specialized operating system called Coupling Facility Control Code (CFCC). It has no I/O devices, other than the CF links. The information in the CF resides entirely in memory as CFCC is not a virtual memory operating system. A CF typically has a large memory â of the order of several tens of gigabytes. The CF runs no application software.
- IBM zSeries model 900 processor
- IBM 9672 S/390 Parallel Enterprise Server G3 or higher
- all subsequent z processors{edih} IBM enabled the use of an Internal Coupling Facility where the CFCC runs in a logical partition (LPAR) defined in standard processor complex and communicates over internal links within that processor complex hardware. Internal links are simulated, whereas links to another processor unit are over copper or optical fiber cables. More than one CF is typically configured in a Sysplex cluster for reliability and availability. Recovery support in the z/OS operating system allows structures to be rebuilt in the alternate CF in the event of a failure.
Coupling Facility structures
A CF is used for three purposes:- Locking information that is shared among all attached systems
- Cache information (such as for a data base) that is shared among all attached systems (or maintaining coherency between local buffer pools in each system).
- Data list information that is shared among all attached systems
- Lock
- Cache
- List (and the variant Serialised List)
Structure duplexing
Structures may be duplexed across different CFs, allowing two copies of the same structure to be kept synchronized. Duplexing is often used as part of an installation's drive to remove single points of failure, with the aim of reducing the incidence and duration of application outages. In the event of the failure of one CF, the other copy of the structure is used to satisfy all requests.Coupling Facility requests
A request to a CF structure is of one of two kinds:- Synchronous (sync) requests. When a z/OS system issues a request it waits for the request to complete, actively spinning on one of its own processors. Sync requests are quick but the response time is the same as the coupled system's spinning CPU loss. So Sync requests are relatively expensive in CPU terms â from the coupled system's perspective.
- Asynchronous (async) requests. When a z/OS system issues a request it doesn't wait for the request to complete. Async requests are slower than sync requests (as they have a lower priority in the CF) but don't lead to the coupled system's processor spinning.
Dynamic Request Conversion
In z/OS Release 2, the Dynamic Request Conversion heuristic algorithm was introduced. This uses sampled response times to decide whether to convert Sync requests to Async or not. These decisions are based on such criteria as coupled processor speed. The greater the distance between the coupled z/OS system and the CF the greater the likelihood requests will be converted to Async from Sync.Async requests are never converted to Sync.This heuristic algorithm complements a previously-existing algorithm that automatically (but not heuristically) converted requests, based on conditions such as path busy and on request data size. The difference is the new algorithm samples response times dynamically.CFs are unique to S/390, zSeries and System z mainframes. They are key to Parallel Sysplex technology.Coupling Facility Levels and Exploiting Software Levels
The CFCC code is released as Levels, usually denoted by their CFLEVEL. For example, CFLEVEL 15 was announced in April 2007. Each level brings new function and sometimes improved performance. In most cases the new function or performance improvement requires a corequisite release of z/OS and perhaps new function in some subsystem (such as Db2). One such example is Coupling Facility Structure Duplexing. (Sometimes support from the operating system and subsystems is available via PTFs rather than a full release.)Notes
{{Notelist}}References
{{Reflist}}- content above as imported from Wikipedia
- "Coupling Facility" does not exist on GetWiki (yet)
- time: 5:07am EDT - Sat, May 18 2024
- "Coupling Facility" does not exist on GetWiki (yet)
- time: 5:07am EDT - Sat, May 18 2024
[ this remote article is provided by Wikipedia ]
LATEST EDITS [ see all ]
GETWIKI 23 MAY 2022
The Illusion of Choice
Culture
Culture
GETWIKI 09 JUL 2019
Eastern Philosophy
History of Philosophy
History of Philosophy
GETWIKI 09 MAY 2016
GetMeta:About
GetWiki
GetWiki
GETWIKI 18 OCT 2015
M.R.M. Parrott
Biographies
Biographies
GETWIKI 20 AUG 2014
GetMeta:News
GetWiki
GetWiki
© 2024 M.R.M. PARROTT | ALL RIGHTS RESERVED