20 Facts About CICS

CICS manages the entire transaction such that if for any reason a part of the transaction fails all recoverable changes can be backed out.

CICS was preceded by an earlier, single-threaded transaction processing system, IBM MTCS.

An 'MTCS-CICS bridge' was later developed to allow these transactions to execute under CICS with no change to the original application programs.

CICS was originally developed in the United States at an IBM Development Center in Des Plaines, Illinois, beginning in 1966 to address requirements from the public utility industry.

The first CICS product was announced in 1968, named Public Utility Customer Information Control System, or PU-CICS.

Related searches

CICS owes its early popularity to its relatively efficient implementation when hardware was very expensive, its multi-threaded processing architecture, its relative simplicity for developing terminal-based real-time transaction applications, and many open-source customer contributions, including both debugging and feature enhancement.

Part of CICS was formalized using the Z notation in the 1980s and 1990s in collaboration with the Oxford University Computing Laboratory, under the leadership of Tony Hoare.

Tools were included for taking traditional CICS programs written in languages such as COBOL, and converting them into WSDL defined Web Services, with little or no program changes.

Many of the newer web facing technologies were made available for earlier releases of CICS using delivery models other than a traditional product release.

JSON technology in CICS is similar to earlier SOAP technology, both of which allowed programs hosted in CICS to be wrapped with a modern facade.

Program corruption and CICS control block corruption was a frequent cause of system downtime.

When CICS was first released, it only supported application transaction programs written in IBM 360 Assembler.

CICS allows the programmer to access and manipulate these by passing the address of the list as the first argument to the program.

Command-level-only CICS introduced in the early 1990s offered some advantages over earlier versions of CICS.

Plug-ins for Maven and Gradle are provided to simplify automated building of CICS bundles, using familiar IDEs like Eclipse, IntelliJ IDEA, and Visual Studio Code.

CICS provides the same run-time container as IBM's WebSphere product family so Java EE applications are portable between CICS and Websphere and there is common tooling for the development and deployment of Java EE applications.

CICS transaction is a set of operations that perform a task together.

CICS screens are usually sent as a construct called a map, a module created with Basic Mapping Support assembler macros or third-party tools.

Under CICS, following are some of the resources which are considered recoverable.

Original CICS nucleus consisted of a number of functional modules written in 370 assembler until V3:.