CICS Tutorial
  • cics - Tutorial
  • - Css
  • - W3css
  • cics - Useful Resources
  • Cics - Ebook Download

  • CICS

    Customer Information Control System CICS is a family of mixed language application servers that provide online transaction management and connectivity for applications on IBM mainframe systems under z/OS and z/VSE.

    CICS is middleware designed to support rapid, high-volume online transaction processing. A CICS transaction is a unit of processing initiated by a single request that may affect one or more objects. This processing is usually interactive screen-oriented, but background transactions are possible.

    CICS provides services that extend or replace the functions of the operating system and are more efficient than the generalized services in the operating system and simpler for programmers to use, particularly with respect to communication with diverse terminal devices.

    Applications developed for CICS may be written in a variety of programming languages and use CICS-supplied language extensions to interact with resources such as files, database connections, terminals, or to invoke functions such as web services. CICS manages the entire transaction such that if for any reason a part of the transaction fails all recoverable changes can be backed out.

    While CICS has its highest profile among financial institutions such as banks and insurance companies, many Fortune 500 companies are reported to run CICS along with many government entities. CICS is also widely used by many smaller organizations. CICS is used in bank-teller applications, ATM systems, industrial production control systems, insurance applications, and many other types of interactive applications.

    Recent CICS Transaction Server enhancements include support for Web services and Java, event processing, Atom feeds, and RESTful interfaces. CICS Transaction Server 5.5, which generally became available on December 14, 2018, reinforced CICS reputation as a mixed language application server, with the introduction of Node.JS support as well as new and enhanced capabilities in security, resilience and system management.


    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 Program Product on July 8, 1969, not long after IMS database management system.

    For the next few years, CICS was developed in Palo Alto and was considered a less important "smaller" product than IMS which IBM then considered more strategic. Customer pressure kept it alive, however. When IBM decided to end development of CICS in 1974 to concentrate on IMS, the CICS development responsibility was picked up by the IBM Hursley Site in the United Kingdom, which had just ceased work on the PL/I compiler and so knew many of the same customers as CICS. The core of the development work continues in Hursley today alongside contributions from labs in India, China, Russia, Australia and United States.

    CICS originally only supported a few IBM-brand devices like the 1965 IBM 2741 Selectric golf ball typewriter based terminal. The 1964 IBM 2260 and 1972 IBM 3270 video display terminals were widely used later.

    In the early days of IBM mainframes, computer software was free – bundled at no extra charge with computer hardware. The OS/360 operating system and application support software like CICS were "open" to IBM customers long before the open source software initiative. Corporations like Standard Oil of Indiana Amoco made major contributions to CICS.

    The IBM Des Plaines team tried to add support for popular non-IBM terminals like the ASCII Teletype Model 33 ASR, but the small low-budget software development team could not afford the $100-per-month hardware to test it. IBM executives incorrectly felt that the future would be like the past with batch processing using traditional punch cards.

    IBM reluctantly provided only minimal funding when public utility companies, banks and credit-card companies demanded a cost-effective interactive system similar to the 1965 IBM Airline Control Program used by the American Airlines Sabre computer reservations system for high-speed data access-and-update to customer information for their telephone operators without waiting for overnight batch processing punch card systems.

    When CICS was delivered to Amoco with Teletype Model 33 ASR support, it caused the entire OS/360 operating system to crash including non-CICS application programs. The majority of the CICS Terminal Control Program TCP – the heart of CICS and part of OS/360 had to be laboriously redesigned and rewritten by Amoco Production Company in Tulsa Oklahoma. It was then given back to IBM for free distribution to others.

    In a few years,[] CICS generated over $60 billion in new hardware revenue for IBM, and became their most-successful mainframe software product.

    In 1972, CICS was available in three versions – DOS-ENTRY program number 5736-XX6 for DOS/360 machines with very limited memory, DOS-STANDARD program number 5736-XX7, for DOS/360 machines with more memory, and OS-STANDARD V2 program number 5734-XX7 for the larger machines which ran OS/360.

    In early 1970, a number of the original developers, including Ben Riggins the principal architect of the early releases relocated to California and continued CICS development at IBM's Palo Alto Development Center. IBM executives did not recognize value in software as a revenue-generation product until after federal law required software unbundling. In 1980, IBM executives failed to heed Ben Riggins' strong suggestions that IBM should provide their own EBCDIC-based operating system and integrated-circuit microprocessor chip for use in the IBM Personal Computer as a CICS intelligent terminal instead of the incompatible Intel chip, and immature ASCII-based Microsoft 1980 DOS.

    Because of the limited capacity of even large processors of that era every CICS installation was required to assemble the source code for all of the CICS system modules after completing a process similar to system generation sysgen, called CICSGEN, to establish values for conditional assembly language statements. This process allowed each customer to exclude support from CICS itself for any feature they did not intend to use, such as device support for terminal types not in use.

    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. This work won a Queen's Award for Technological Achievement.

    In 1986, IBM announced CICS support for the record-oriented file services defined by Distributed Data Management Architecture DDM. This enabled programs on remote, network-connected computers to create, manage, and access files that had previously been available only within the CICS/MVS and CICS/VSE transaction processing environments.

    In newer versions of CICS, support for DDM has been removed. Support for the DDM component of CICS z/OS was discontinued at the end of 2003, and was removed from CICS for z/OS in version 5.2 onwards. In CICS TS for z/VSE, support for DDM was stabilised at V1.1.1 level, with an announced intention to discontinue it in a future release In CICS for z/VSE 2.1 onwards, CICS/DDM is not supported.

    CICS Transaction Server first introduced a native HTTP interface in version 1.2, together with a Web Bridge technology for wrapping green-screen Terminal based programs with an HTML facade. CICS Web and Document APIs were enhanced in CICS TS V1.3 to enable web-aware applications to be written to interact more effectively with web browsers.

    CICS TS versions 2.1 through 2.3 focused on introducing CORBA and EJB technologies to CICS, offering new ways to integrate CICS assets into distributed application component models. These technologies relied on hosting Java applications in CICS. The Java hosting environment saw numerous improvements over many releases, ultimately resulting in the embedding of the WebSphere Liberty Profile into CICS Transaction Server V5.1. Numerous web facing technologies could be hosted in CICS using Java, this ultimately resulted in the removal of the native CORBA and EJB technologies.

    CICS TS V3.1 added a native implementation of the SOAP and WSDL technologies for CICS, together with client side HTTP APIs for outbound communication. These twin technologies enabled easier integration of CICS components with other Enterprise applications, and saw widespread adoption. 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. This technology saw regular enhancements over successive releases of CICS.

    CICS TS V4.1 and V4.2 saw further enhancements to web connectivity, including a native implementation of the ATOM publishing protocol.

    Many of the newer web facing technologies were made available for earlier releases of CICS using delivery models other than a traditional product release. This allowed early adopters to provide constructive feedback that could influence the final design of the integrated technology. Examples include the Soap for CICS technology preview SupportPac for TS V2.2, or the ATOM SupportPac for TS V3.1. This approach was used to introduce JSON support for CICS TS V4.2, a technology that went on to be integrated into CICS TS V5.2.

    The 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. The JSON technology was in turn enhanced in z/OS Connect Enterprise Edition, an IBM product for composing JSON APIs that can leverage assets from several mainframe subsystems.

    Many partner products have also been used to interact with CICS. Popular examples include using the CICS Transaction Gateway for connecting to CICS from JCA compliant Java application servers, and IBM DataPower appliances for filtering web traffic before it reaches CICS.

    Modern versions of CICS provide many ways for both existing and new software assets to be integrated into distributed application flows. CICS assets can be accessed from remote systems, and can access remote systems; user identity and transactional context can be propagated; RESTful APIs can be composed and managed; devices, users and servers can interact with CICS using standards based technologies; and the IBM WebSphere Liberty environment in CICS promotes the rapid adoption of new technologies.

    Although when CICS is mentioned, people usually mean CICS Transaction Server, the CICS Family refers to a portfolio of transaction servers, connectors called CICS Transaction Gateway and CICS Tools.

    CICS on distributed platforms—not mainframes—is called IBM TXSeries. TXSeries is distributed transaction processing middleware. It supports C, C++, COBOL, Java™ and PL/I applications in cloud environments and traditional data centers. TXSeries is available on AIX, Linux x86, Windows, Solaris and HP-UX platforms. CICS is also available on other operating systems, notably IBM i and OS/2. The z/OS implementation i.e., CICS Transaction Server for z/OS is by far the most popular and significant.

    Two versions of CICS were previously available for VM/CMS, but both have since been discontinued. In 1986, IBM released CICS/CMS which was a single-user version of CICS designed for development use, the applications later being transferred to an MVS or DOS/VS system for production execution. Later, in 1988, IBM released CICS/VM. CICS/VM was intended for use on the IBM 9370, a low-end mainframe targeted at departmental use; IBM positioned CICS/VM running on departmental or branch office mainframes for use in conjunction with a central mainframe running CICS for MVS.

    Provisioning, management and analysis of CICS systems and applications is provided by CICS Tools. This includes performance management as well as deployment and management of CICS resources. In 2015, the four core foundational CICS tools and the CICS Optimization Solution Pack for z/OS were updated with the release of CICS Transaction Server for z/OS 5.3. The four core CICS Tools: CICS Interdependency Analyzer for z/OS, CICS Deployment Assistant for z/OS, CICS Performance Analyzer for z/OS and CICS Configuration Manager for z/OS.


    Multiple-user interactive-transaction application programs were required to be quasi-reentrant in order to support multiple concurrent transaction threads. A software coding error in one application could block all users from the system. The modular design of CICS reentrant / reusable control programs meant that, with judicious "pruning," multiple users with multiple applications could be executed on a computer with just 32K of expensive magnetic core physical memory including the operating system.

    Considerable effort was required by CICS application programmers to make their transactions as efficient as possible. A common technique was to limit the size of individual programs to no more than 4,096 bytes, or 4K, so that CICS could easily reuse the memory occupied by any program not currently in use for another program or other application storage needs. When virtual memory was added to versions OS/360 in 1972, the 4K strategy became even more important to reduce paging and thrashing unproductive resource-contention overhead.

    The efficiency of compiled high-level COBOL and PL/I language programs left much to be desired. Many CICS application programs continued to be written in assembler language, even after COBOL and PL/I support became available.

    With 1960s-and-1970s hardware resources expensive and scarce, a competitive "game" developed among system optimization analysts. When critical path code was identified, a code snippet was passed around from one analyst to another. Each person had to either a reduce the number of bytes of code required, or b reduce the number of CPU cycles required. Younger analysts learned from what more-experienced mentors did. Eventually, when no one could do a or b, the code was considered optimized, and they moved on to other snippets. Small shops with only one analyst learned CICS optimization very slowly or not at all.

    Because application programs could be shared by many concurrent threads, the use of static variables embedded within a program or use of operating system memory was restricted by convention only.

    Unfortunately, many of the "rules" were frequently broken, especially by COBOL programmers who might not understand the internals of their programs or fail to use the necessary restrictive compile time options. This resulted in "non-re-entrant" code that was often unreliable, leading to spurious storage violations and entire CICS system crashes.

    Originally, the entire partition, or Multiple Virtual Storage MVS region, operated with the same memory protection key including the CICS kernel code. Program corruption and CICS control block corruption was a frequent cause of system downtime. A software error in one application program could overwrite the memory code or data of one or all currently running application transactions. Locating the offending application code for complex transient timing errors could be a very-difficult operating-system analyst problem.

    These shortcomings persisted for multiple new releases of CICS over a period of more than 20 years, in spite of their severity and the fact that top-quality CICS skills were in high demand and short supply. They were addressed in TS V3.3, V4.1 and V5.2 with the Storage Protection, Transaction Isolation and Subspace features respectively, which utilize operating system hardware features to protect the application code and the data within the same address space even though the applications were not written to be separated. CICS application transactions remain mission-critical for many public utility companies, large banks and other multibillion-dollar financial institutions.

    Additionally, it is possible to provide a measure of advance application protection by performing test under control of a monitoring program that also serves to provide Test and Debug features.

    When CICS was first released, it only supported application transaction programs written in IBM 360 Assembler. COBOL and PL/I support were added years later. Because of the initial assembler orientation, requests for CICS services were made using assembler language macros. For example, the request to read a record from a file were made by a macro call to the "File Control Program" of CICS might look like this:


    This gave rise to the later terminology "Macro-level CICS."

    When high-level language support was added, the macros were retained and the code was converted by a pre-compiler that expanded the macros to their COBOL or PL/I CALL statement equivalents. Thus preparing a HLL application was effectively a "two-stage" compile – output from the preprocessor fed into the HLL compiler as input.

    COBOL considerations: unlike PL/I, IBM COBOL does not normally provide for the manipulation of pointers addresses. In order to allow COBOL programmers to access CICS control blocks and dynamic storage the designers resorted to what was essentially a hack. The COBOL Linkage Section was normally used for inter-program communication, such as parameter passing. The compiler generates a list of addresses, each called a Base Locator for Linkage BLL which were set on entry to the called program. The first BLL corresponds to the first item in the Linkage Section and so on. CICS allows the programmer to access and manipulate these by passing the address of the list as the first argument to the program. The BLLs can then be dynamically set, either by CICS or by the application to allow access to the corresponding structure in the Linkage Section.

    During the 1980s, IBM at Hursley Park produced a version of CICS that supported what became known as "Command-level CICS" which still supported the older programs but introduced a new API style to application programs.

    A typical Command-level call might look like the following:


    The values given in the SEND MAPSET command correspond to the names used on the first DFHMSD macro in the map definition given below for the MAPSET argument, and the DFHMSI macro for the MAP argument. This is pre-processed by a pre-compile batch translation stage, which converts the embedded commands EXECs into call statements to a stub subroutine. So, preparing application programs for later execution still required two stages. It was possible to write "Mixed mode" applications using both Macro-level and Command-level statements.

    Initially, at execution time, the command-level commands were converted using a run-time translator, "The EXEC Interface Program", to the old Macro-level call, which was then executed by the mostly unchanged CICS nucleus programs. But when the CICS Kernel was re-written for TS V3, EXEC CICS became the only way to program CICS applications, as many of the underlying interfaces had changed.

    The Command-level-only CICS introduced in the early 1990s offered some advantages over earlier versions of CICS. However, IBM also dropped support for Macro-level application programs written for earlier versions. This meant that many application programs had to be converted or completely rewritten to use Command-level EXEC commands only.

    By this time, there were perhaps millions of programs worldwide that had been in production for decades in many cases. Rewriting them often introduced new bugs without necessarily adding new features. There were a significant number of users who ran CICS V2 application-owning regions AORs to continue to run macro code for many years after the change to V3.

    It was also possible to execute old Macro-level programs using conversion software such as APT International's Command CICS.

    Recent CICS Transaction Server enhancements include support for a number of modern programming styles.

    CICS Transaction Server Version 2.1 introduced support for Java. CICS Transaction Server Version 2.2 supported the Software Developers Toolkit. CICS provides the same run-time container as IBM's WebSphere product family so EJB applications are portable between CICS and Websphere and there is common tooling for the development and deployment of EJB applications.

    In addition, newer CICS versions have placed an emphasis on "wrapping" existing application programs inside modern interfaces so that long-established business functions can be incorporated into more modern services. These include WSDL, SOAP and JSON interfaces that wrap legacy code so that a web or mobile application can obtain and update the core business objects without requiring a major rewrite of the back-end functions.


    A CICS transaction is a set of operations that perform a task together. Usually, the majority of transactions are relatively simple tasks such as requesting an inventory list or entering a debit or credit to an account. A primary characteristic of a transaction is that it should be atomic. On IBM System z servers, CICS easily supports thousands of transactions per second, making it a mainstay of enterprise computing.

    CICS applications comprise transactions, which can be written in numerous programming languages, including COBOL, PL/I, C, C++, IBM Basic assembly language, REXX, and Java.

    Each CICS program is initiated using a transaction identifier. CICS screens are usually sent as a construct called a map, a module created with Basic Mapping Support BMS assembler macros or third-party tools. CICS screens may contain text that is highlighted, has different colors, and/or blinks depending on the terminal type used. An example of how a map can be sent through COBOL is given below. The end user inputs data, which is made accessible to the program by receiving a map from CICS.


    For technical reasons, the arguments to some command parameters must be quoted and some must not be quoted, depending on what is being referenced. Most programmers will code out of a reference book until they get the "hang" or concept of which arguments are quoted, or they'll typically use a "canned template" where they have example code that they just copy and paste, then edit to change the values.

    Basic Mapping Support defines the screen format through assembler macros such as the following. This was assembled to generate both the physical map set – a load module in a CICS load library – and a symbolic map set – a structure definition or DSECT in PL/I, COBOL, assembler, etc. which was copied into the source program.

     LOSMATT DFHMSD TYPE=MAP,                                               X
                    MODE=INOUT,                                             X
                    TIOAPFX=YES,                                            X
                    TERM=3270-2,                                            X
                    LANG=COBOL,                                             X
                    MAPATTS=COLOR,HILIGHT,                                X
                    DSATTS=COLOR,HILIGHT,                                 X
                    STORAGE=AUTO,                                           X
     LOSATT  DFHMDI SIZE=24,80,                                           X
                    LINE=1,                                                 X
     LSSTDII DFHMDF POS=1,01,                                             X
                    LENGTH=04,                                              X
                    COLOR=BLUE,                                             X
                    INITIAL='MQCM',                                         X
             DFHMDF POS=24,01,                                            X
                    LENGTH=79,                                              X
                    COLOR=BLUE                                              X
                    ATTRB=ASKIP,                                            X
                    INITIAL='PF7-          8-           9-          10-     X
                        11-            12-CANCEL'                            
               DFHMSD   TYPE=FINAL                                           


    In the started task. Whether a batch job or a started task, CICS regions may run for days, weeks, or even months before shutting down for maintenance MVS or CICS. Upon restart a parameter determines if the start should be "Cold" no recovery or "Warm"/"Emergency" using a warm shutdown or restarting from the log after a crash. Cold starts of large CICS regions with many resources can take a long time as all the definitions are re-processed.

    Installations are divided into multiple address spaces for a wide variety of reasons, such as:

    A typical installation consists of a number of distinct applications that make up a service. Each service usually has a number of "Terminal-Owning Region" TORs that route transactions to multiple "Application-Owning Regions" AORs, though other topologies are possible. For example, the AORs might not perform File I/O. Instead there would be a "File-Owning Region" FOR that performed the File I/O on behalf of transactions in the AOR – given that, at the time, a VSAM file could only support recoverable write access from one address space at a time.

    But not all CICS applications use VSAM as the primary data source or historically other single address space at a time datastores such as CA Datacom- many use either IMS/DB or Db2 as the database, and/or MQ as a queue manager. For all these cases, TORs can load-balance transactions to sets of AORs which then directly use the shared databases/queues. CICS supports XA two-phase commit between data stores and so transactions that spanned MQ, VSAM/RLS and Db2, for example, are possible with ACID properties.

    CICS supports distributed transactions using SNA LU6.2 protocol between the address spaces which can be running on the same or different clusters. This allows ACID updates of multiple datastores by cooperating distributed applications. In practice there are issues with this if a system or communications failure occurs because the transaction disposition backout or commit may be in-doubt if one of the communicating nodes has not recovered. Thus the use of these facilities has never been very widespread.

    Sysplex exploitation

    At the time of CICS ESA V3.2, in the early 1990s, IBM faced the challenge of how to get CICS to exploit the new zOS Sysplex mainframe line.

    The Sysplex was to be based on CMOS Complementary Metal Oxide Silicon rather than the existing ECL Emitter Coupled Logic hardware. The cost of scaling the mainframe-unique ECL was much higher than CMOS which was being developed by a keiretsu with high-volume use cases such as Sony PlayStation to reduce the unit cost of each generation's CPUs. The ECL was also expensive for users to run because the gate drain current produced so much heat that the CPU had to packaged into a special module called a Thermal Conduction Module TCM that had inert gas pistons and needed plumbed to be high-volume chilled water to be cooled. But the air-cooled CMOS technology's CPU speed initially was much slower than the ECL notably the boxes available from the mainframe-clone makers Amdahl and Hitachi. This was especially concerning to IBM in the CICS context as almost all the largest mainframe customers were running CICS and for many of them it was the primary mainframe workload.

    To achieve the same total transaction throughput on a Sysplex multiple boxes would need to be used in parallel for each workload but a CICS address space, due to its semi-reentrant application programming model, could not exploit more than about 1.5 processors on one box at the time – even with use of MVS sub-tasks. Without a solution, these customers would tend to move to the competitors rather than Sysplex as they scaled up the CICS workloads. There was considerable debate inside IBM as to whether the right approach would be to break upwards compatibility for applications and move to a model like IMS/DC which was fully reentrant, or to extend the approach customers had adopted to more fully exploit a single mainframe's power – using multi-region operation MRO.

    Eventually the second path was adopted after the CICS user community was consulted and vehemently opposed breaking upward compatibility given that they had the prospect of Y2K to contend with at that time and did not see the value in re-writing and testing millions of lines of mainly COBOL, PL/1 or assembler code.

    The IBM recommended structure for CICS on Sysplex was that at least one CICS Terminal Owning Region was placed on each Sysplex node which dispatched transactions to many Application Owning Regions AORs spread across the entire Sysplex. If these applications needed to access shared resources they either used a Sysplex-exploiting datastore such as Db2 or IMS/DB or concentrated, by function-shipping, the resource requests into singular-per-resource Resource Owing Regions RORs including File Owning Regions FORs for VSAM and CICS Data Tables, Queue Owning Regions QORs for MQ, CICS Transient Data TD and CICS Temporary Storage TS. This preserved compatibility for legacy applications at the expense of operational complexity to configure and manage many CICS regions.

    In subsequent releases and versions, CICS was able to exploit new Sysplex-exploiting facilities in VSAM/RLS, MQ for zOS and placed its own Data Tables, TD and TS resources into the architected shared resource manager for the Sysplex -> the Coupling Facility or CF, dispensing with the need for most RORs. The CF provides a mapped view of resources including a shared timebase, buffer pools, locks and counters with hardware messaging assists that made sharing resources across the Sysplex both more efficient than polling and reliable utilizing a semi-synchronized backup CF for use in case of failure.

    By this time, the CMOS line had individual boxes that exceeded the power available by the fastest ECL box with more processors per CPU and when these were coupled together 32 or more nodes would be able to scale two orders of magnitude larger in total power for a single workload. For example, by 2002, Charles Schwab was running a "MetroPlex" consisting of a redundant pair of its mainframe Sysplexes in two locations in Phoenix, AZ each with 32 nodes driven by one shared CICS/DB/2 workload to support the vast volume of pre-dotcom-bubble web client inquiry requests.

    This cheaper, much more scalable CMOS technology base, and the huge investment costs of having to both get to 64bit addressing and independently produce cloned CF functionality drove the IBM-mainframe clone makers out of the business one by one.

    CICS Recovery/Restart

    The objective of recovery/restart in CICS is to minimize and if possible eliminate damage done to Online System when a failure occurs, so that system and data integrity is maintained. If the CICS region was shutdown instead of failing it will perform a "Warm" start exploiting the checkpoint written at shutdown. The CICS region can also be forced to "Cold" start which reloads all definitions and wipes out the log, leaving the resources in whatever state they are in.

    Under CICS, following are some of the resources which are considered recoverable. If one wishes these resources to be recoverable then special options must be specified in relevant CICS definitions:

    CICS also offers extensive recovery/restart facilities for users to establish their own recovery/restart capability in their CICS system. Commonly used recovery/restart facilities include:


    Each CICS region comprises one major task on which every transaction runs, although certain services such as access to Db2 data use other tasks TCBs. Within a region transactions are cooperatively multitasked – they are expected to be well-behaved and yield the CPU rather than wait. CICS services handle this automatically.

    Each unique CICS "Task" or transaction is allocated its own dynamic memory at start-up and subsequent requests for additional memory were handled by a call to the "Storage Control program" part of the CICS nucleus or "kernel", which is analogous to an operating system.

    A CICS system consists of the online nucleus, batch support programs, and applications services.

    The original CICS nucleus consisted of a number of functional modules written in 370 assembler until V3.

    Starting in V3, the CICS nucleus was rewritten into a kernel and domain structure using IBM's PL/AS language – which is compiled into assembler.

    The prior structure did not enforce separation of concerns and so had many inter-program dependencies which led to bugs unless exhaustive code analysis was done. The new structure was more modular and so resilient because it was easier to change without impact. The first domains were often built with the name of the prior program but without the trailing "P". For example, Program Control Domain DFHPC or Transient Data Domain DFHTD. The kernel operated as a switcher for inter-domain requests – initially this proved expensive for frequently called domains such as Trace but by utilizing PL/AS macros these calls were in-lined without compromising on the separate domain design.

    In later versions, completely redesigned domains were added like the Logging Domain DFHLG and Transaction Domain DFHTM that replaced the Journal Control Program JCP.

    In addition to the online functions CICS has several support programs that run as batch jobs. :pp.34–35

    The following components of CICS support application development.:pp.35–37


    Different countries have differing pronunciations