CICS

CICS
Name	CICS
Developer	International Business Machines
Released	1968
Latest release	(see vendor)
Operating system	z/OS, z/VSE
Platform	IBM System/360, IBM Z
License	Proprietary

CICS

CICS is a transaction processing system originally designed for IBM mainframe environments, providing high-volume online transaction processing for applications on IBM System/360 and later IBM Z platforms. It supports integration with middleware and services from vendors and standards bodies, enabling interaction with systems such as IBM Db2, IBM WebSphere, Microsoft Azure, Amazon Web Services, and Oracle Database. Major users include institutions like Bank of America, JPMorgan Chase, United States Department of Defense, British Airways, and Visa Inc..

Overview

CICS is engineered to manage thousands of concurrent transactions per second across hardware from IBM and partners, coordinating resources such as z/OS subsystems, IBM Db2, IBM MQ, CICS Transaction Server, and external services like SOAP and RESTful API endpoints. Enterprises in sectors represented by American Airlines, Lloyds Banking Group, Citigroup, HSBC, and Walmart employ CICS to connect legacy applications with modern web, mobile, and cloud interfaces via adapters to JSON, XML, COBOL, and Java EE runtimes. Standards and consortia such as ISO/IEC, The Open Group, OASIS, and W3C influence interoperability and protocol support.

History and development

CICS originated in the late 1960s on IBM System/360 hardware, developed to support transaction processing requirements similar to those driving systems at AT&T, General Electric, Standard Oil, and Bank of America. Over decades, releases aligned with milestones at IBM and platform advances like MVS and z/OS, integrating with products such as IMS (Information Management System), DB2, MQSeries, and later with middleware from Red Hat, Apache Software Foundation, Spring Framework, and Eclipse Foundation. Major evolutionary steps paralleled events such as the rise of client–server computing, the adoption of Java, and the growth of cloud offerings by Microsoft Azure and Amazon Web Services.

Architecture and components

CICS architecture centers on an address space and region model interacting with system services on z/OS, z/VSE, or related platforms, coordinating with subsystems like IBM Db2 and IBM MQ. Key components include transaction managers, resource definition tables, and communication handlers that interoperate with products such as TCP/IP stacks, WebSphere Application Server, IBM HTTP Server, and adapters to SOAP and REST. Integration points enable use of languages and runtimes like COBOL, PL/I, Assembler, Java, and Node.js through connectors and APIs compatible with toolchains from GitHub, Jenkins, Ansible, and Docker.

Programming and application development

Application development for CICS commonly uses languages and toolsets including COBOL, PL/I, Assembler, Java, and modern scripting via Python or Node.js runtimes, often employing IDEs such as Eclipse, Visual Studio Code, and IBM Developer for z/OS. Developers integrate with databases like IBM Db2 and Oracle Database and messaging products like IBM MQ while following practices from Agile software development frameworks adopted by firms like Accenture, Deloitte, and Capgemini. Toolchains frequently include source control with Git, CI/CD with Jenkins or GitLab, and testing frameworks influenced by JUnit and Selenium.

Deployment and administration

Administrators deploy CICS within enterprise datacenters using automation and orchestration tools from Ansible, Puppet, Chef, and container technologies referenced by Docker and Kubernetes when modernizing interfaces. Operations integrate with monitoring and observability platforms by IBM Instana, Splunk, Dynatrace, and New Relic, and align with compliance requirements enforced by organizations such as PCI DSS, HIPAA, GDPR, and regulatory bodies including Financial Conduct Authority and Federal Reserve System. Migration and modernization projects often involve consulting firms like IBM Global Services, Tata Consultancy Services, and Infosys.

Security and compliance

CICS security integrates with mainframe identity and access management solutions such as IBM RACF, IBM Security zSecure, and federated identity providers supporting SAML and OAuth 2.0. Cryptographic operations rely on cryptographic modules compliant with standards from NIST and FIPS 140-2, while audit and logging integrate with products from Splunk and IBM QRadar. Large organizations including Goldman Sachs, Barclays, and State Farm use CICS in regulated environments subject to standards and regulations like SOX and PCI DSS and audit frameworks from ISACA and COBIT.

Performance and scalability

CICS is optimized for throughput and low-latency transaction processing on IBM Z hardware such as z14, z15, and z16 processors, leveraging features like logical partitioning (LPARs), Parallel Sysplex clustering, and hardware cryptographic accelerators. Performance tuning often involves collaboration with teams experienced in IBM Tivoli, RMF, Omegamon, and workload managers like Workload Manager (WLM), with capacity planning influenced by benchmarks and studies from organizations such as SPEC and consulting arms of Gartner and Forrester Research.

Category:IBM mainframe software