 | This article's Application and Transaction Manager sections contains promotional content .(January 2023) |
 | |
| Initial release | 1966 |
|---|---|
| Stable release | 15 / October 3, 2017 |
| Operating system | z/OS V2.2 or later |
| Platform | IBM System z |
| Type | Database & transaction processing subsystem |
| License | Proprietary |
| Website | www |
The IBM Information Management System (IMS) is a joint hierarchical database and information management system that supports transaction processing. [1]
IBM designed the IMS with Rockwell and Caterpillar starting in 1966 for the Apollo program, where it was used to inventory the very large bill of materials (BOM) for the Saturn V Moon rocket and Apollo space vehicle. [2]
The system was first considered operational when the first "READY" message appeared on an IBM 2740 terminal in Downey, California, on August 14, 1968. [2] In the interim period, IMS has undergone many developments as IBM System/360 technology evolved into the current z/OS and IBM zEnterprise System technologies.
Vern Watts had worked continuously on IMS since the 1960's [3] and was IMS's chief architect for many years. Watts joined IBM in 1956 and worked at IBM's Silicon Valley development labs until his death on April 4, 2009. [4]
IBM Information Management System (IMS) utilizes a hierarchical database model, distinct from IBM's later relational database model as seen in IBM Db2. In IMS, data is organized into segments, each comprising multiple fields, structured hierarchically to manage complex relationships effectively. [5] For instance, in a customer database, a root segment at the top of the hierarchy may include fields such as phone number, name, and age. Child segments can be added beneath, such as order segments under each customer segment, representing orders placed by customers, with further child segments for individual items on each order.
- Originating from the Data Language Interface (DL/I) databases developed for Apollo, full function databases support primary and secondary indexes, accessed via DL/I calls similar to SQL calls in IBM Db2 or Oracle.[ citation needed ] - These databases can be accessed through various methods, with Hierarchical Direct (HDAM) and Hierarchical Indexed Direct (HIDAM) being prominent. Other formats include Simple Hierarchical Indexed Sequential (SHISAM), Hierarchical Sequential (HSAM), and Hierarchical Indexed Sequential (HISAM). [6] - Data in full-function databases is stored using VSAM, a native z/OS access method, or OSAM, an IMS-specific method optimizing I/O for IMS access patterns, particularly benefiting from sequential access (OSAM Sequential Buffering).[ citation needed ]
- Optimized for high transaction rates, Fast Path databases include Data Entry Databases (DEDBs) and Main Storage Databases (MSDBs). [7] [ citation needed ] - DEDBs employ direct (randomizer) access similar to HDAM in full-function databases, offering enhanced performance through high-performance access methods and asynchronous write after commit. They leverage a Unit of Work (UOW) concept for simplified online reorganization utilities starting from IMS Version 11. [8]
- Introduced in IMS V7, HALDBs extend the capabilities of full function databases to enhance availability and handle large data volumes effectively. [9] - IMS V9 introduced online reorganization for HALDBs, supporting continuous availability and accommodating data volumes exceeding 40 terabytes.
IMS is a transaction manager, (IMS TM, also known as IMS DC) which interacts with an end user connected through VTAM or TCP/IP, (including 3270 and Web user interfaces) or another application. It can process a business function (such as a banking account withdrawal), and maintain state throughout the process, making sure that the system records the business function correctly to a data store.
IMS TM uses a messaging and queuing paradigm. An IMS control program receives a transaction entered from a terminal (or Web browser or other application) and then stores the transaction on a message queue (in memory or in a dataset). IMS then invokes its scheduler on the queued transaction to start the business application program in a message processing region. The message processing region retrieves the transaction from the IMS message queue and processes it, reading and updating IMS and/or Db2 databases and ensuring proper recording of the transaction. Then, if required, IMS enqueues a response message back onto the IMS message queue. Once the output message is complete and available, the IMS control program sends it back to the originating terminal. IMS TM can handle this whole process thousands (or even tens of thousands) of times per second. In 2013, IBM completed a benchmark on IMS Version 13 demonstrating the ability to process 100,000 transactions per second on a single IMS system. [10]
IMS TM provides a standard environment for transaction execution. Several Chinese banks had purchased IMS by the late 2000s to support the country's burgeoning financial industry. [11]
IMS complements IBM Db2, IBM's relational database system introduced in 1982. IMS generally performs faster than Db2 for common tasks, but may require more programming effort to design and maintain for non-primary duties.
A relational data warehouse may be used to supplement an IMS database. For example, IMS may provide primary ATM transactions because it performs well for such a specific task.
In computing, a database is an organized collection of data or a type of data store based on the use of a database management system (DBMS), the software that interacts with end users, applications, and the database itself to capture and analyze the data. The DBMS additionally encompasses the core facilities provided to administer the database. The sum total of the database, the DBMS and the associated applications can be referred to as a database system. Often the term "database" is also used loosely to refer to any of the DBMS, the database system or an application associated with the database.
Multiple Virtual Storage, more commonly called MVS, is the most commonly used operating system on the System/370, System/390 and IBM Z IBM mainframe computers. IBM developed MVS, along with OS/VS1 and SVS, as a successor to OS/360. It is unrelated to IBM's other mainframe operating system lines, e.g., VSE, VM, TPF.
Transaction Processing Facility (TPF) is an IBM real-time operating system for mainframe computers descended from the IBM System/360 family, including zSeries and System z9.
Db2 is a family of data management products, including database servers, developed by IBM. It initially supported the relational model, but was extended to support object–relational features and non-relational structures like JSON and XML. The brand name was originally styled as DB2 until 2017, when it changed to its present form.
Indexed Sequential Access Method (ISAM) is a method for creating, maintaining, and manipulating computer files of data so that records can be retrieved sequentially or randomly by one or more keys. Indexes of key fields are maintained to achieve fast retrieval of required file records in indexed files. IBM originally developed ISAM for mainframe computers, but implementations are available for most computer systems.
IBM 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.
Adabas, a contraction of “adaptable database system," is a database package that was developed by Software AG to run on IBM mainframes. It was launched in 1971 as a non-relational database. As of 2019, Adabas is marketed for use on a wider range of platforms, including Linux, Unix, and Windows.
IBM MQ is a family of message-oriented middleware products that IBM launched in December 1993. It was originally called MQSeries, and was renamed WebSphere MQ in 2002 to join the suite of WebSphere products. In April 2014, it was renamed IBM MQ. The products that are included in the MQ family are IBM MQ, IBM MQ Advanced, IBM MQ Appliance, IBM MQ for z/OS, and IBM MQ on IBM Cloud. IBM MQ also has containerised deployment options.
In computing, a Parallel Sysplex is a cluster of IBM mainframes acting together as a single system image with z/OS. Used for disaster recovery, Parallel Sysplex combines data sharing and parallel computing to allow a cluster of up to 32 systems to share a workload for high performance and high availability.
IBM Storage Protect is a data protection platform that gives enterprises a single point of control and administration for backup and recovery. It is the flagship product in the IBM Spectrum Protect family.
A transaction processing system (TPS) is a software system, or software/hardware combination, that supports transaction processing.
In IBM System z9 and successor mainframes, the System z Integrated Information Processor (zIIP) is a special purpose processor. It was initially introduced to relieve the general mainframe central processors (CPs) of specific Db2 processing loads, but currently is used to offload other z/OS workloads as described below. The idea originated with previous special purpose processors, the zAAP, which offloads Java processing, and the IFL, which runs Linux and z/VM but not other IBM operating systems such as z/OS, DOS/VSE and TPF. A System z PU is "characterized" as one of these processor types, or as a CP, or SAP. These processors do not contain microcode or hardware features that accelerate their designated workloads. Instead, by relieving the general CP of particular workloads, they often lead to a higher workload throughput at reduced license fees.
Teleprocessing Network Simulator (TPNS) is an IBM licensed program, first released in 1976 as a test automation tool to simulate the end-user activity of network terminal(s) to a mainframe computer system, for functional testing, regression testing, system testing, capacity management, benchmarking and stress testing.
Information Management Software is one of the brands within IBM Software Group (SWG) division. The major Information Management products include:
An access method is a function of a mainframe operating system that enables access to data on disk, tape or other external devices. Access methods were present in several mainframe operating systems since the late 1950s, under a variety of names; the name access method was introduced in 1963 in the IBM OS/360 operating system. Access methods provide an application programming interface (API) for programmers to transfer data to or from device, and could be compared to device drivers in non-mainframe operating systems, but typically provide a greater level of functionality.
Object access method (OAM) is an access method under z/OS which is designed for the storage of large numbers of large files, such as images. It has a number of distinguishing features, e.g. compared to VSAM:
pureXML is the native XML storage feature in the IBM Db2 data server. pureXML provides query languages, storage technologies, indexing technologies, and other features to support XML data. The word pure in pureXML was chosen to indicate that Db2 natively stores and natively processes XML data in its inherent hierarchical structure, as opposed to treating XML data as plain text or converting it into a relational format.
Data Language One is the language system used to access IBM's IMS databases and its data communication system.
Donald Haderle is an American computer scientist and IBM Fellow, best known for his work on relational database management systems (RDBMS). He led the architecture and design of DB2, one of the first commercial RDBMSs, which led to his moniker "Father of DB2." DB2 debuted on IBM's mainframe system MVS in 1983 and validated the applicability of relational databases for high performance transaction processing. With DB2 enterprises store, retrieve, and analyze their business transaction data. The cited reference describes the early technology hurdles, the shift from a monolithic architecture to a distributed architecture portable across many operating systems and the technology collaborations with IBM Research. DB2 is used in most enterprises around the world.
Distributed Data Management Architecture (DDM) is IBM's open, published software architecture for creating, managing and accessing data on a remote computer. DDM was initially designed to support record-oriented files; it was extended to support hierarchical directories, stream-oriented files, queues, and system command processing; it was further extended to be the base of IBM's Distributed Relational Database Architecture (DRDA); and finally, it was extended to support data description and conversion. Defined in the period from 1980 to 1993, DDM specifies necessary components, messages, and protocols, all based on the principles of object-orientation. DDM is not, in itself, a piece of software; the implementation of DDM takes the form of client and server products. As an open architecture, products can implement subsets of DDM architecture and products can extend DDM to meet additional requirements. Taken together, DDM products implement a distributed file system.
| Authority control databases: National |
|---|
