IMS / Information Management System
IMS Overview
IMS:
=====
IMS (Information Management System) is a database and transaction management system that was first introduced by IBM in 1968. Since then, IMS has gone through many changes in adapting to new programming tools and environments. IMS is one of two major legacy database and transaction management subsystems from IBM that run on mainframe MVS (now z/OS) systems. The other is CICS. It is claimed that, historically, application programs that use either (or both) IMS or CICS services have handled and continue to handle most of the world's banking, insurance, and order entry transactions.
IMS consists of two major components, the IMS Database Management System (IMS DB) and the IMS Transaction Management System (IMS TM). In IMS DB, the data is organized into a hierarchy. The data in each level is dependent on the data in the next higher level. The data is arranged so that its integrity is ensured, and the storage and retrieval process is optimized. IMS TM controls I/O (input/output) processing, provides formatting, logging, and recovery of messages, maintains communications security, and oversees the scheduling and execution of programs. TM uses a messaging mechanism for queuing requests.
IMS's original programming interface was DL/1 (Data Language/1). Today, IMS applications and databases can be connected to CICS applications and DB2 databases. Java programs can access IMS databases and services.
IMS also stands for Intelligent Manufacturing Systems and IP Multimedia Subsystem.
History:
=========
IBM designed IMS with Rockwell and Caterpillar starting in 1966 for the Apollo program. IMS's challenge was to inventory the very large bill of materials (BOM) for the Saturn V moon rocket and Apollo space vehicle. However, by some accounts it was accepted too late in the process to make significant contributions to the Apollo program.
The first "IMS READY" message appeared on an IBM 2740 terminal in Downey, California, on 14 August 1968. IMS is still going strong over 40 years later and, over time, has seen some interesting developments as IBM System/360 technology evolved into the current z/OS and System z9 and z10 technologies. For example, IMS supports the Java programming language, JDBC, XML, and, since late 2005, Web services (though installing the JDBC driver may require licensing additional software from IBM). IMS Connect comes standard with Version 9 and higher and provides a TCP/IP interface to Message Processing Programs running in IMS Message Processing Regions.
Vern Watts was IMS's chief architect for many years. Mr. Watts joined IBM in 1956 and worked at IBM's Silicon Valley development labs until his death April 4, 2009.[1] He had continuously worked on IMS since the 1960s. [2]
IMS is reportedly IBM's highest revenue software product, and it continues to grow.
Transaction Manager:
====================
IMS is also a robust transaction manager (IMS TM, also known as IMS DC) — one of the "big three" classic transaction managers along with CICS and BEA (now Oracle) Tuxedo. A transaction manager interacts with an end user (connected through VTAM or TCP/IP, including 3270 and Web user interfaces) or another application, processes a business function (such as a banking account withdrawal), and maintains state throughout the process, making sure that the system records the business function correctly to a data store. Thus IMS TM is quite like a Web application, operating through a CGI program (for example), to provide an interface to query or update a database. IMS TM typically uses either IMS DB or DB2 as its backend database. When used alone with DB2 the IMS TM component can be purchased without the IMS DB component.
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, assuring 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.
Application
===========
Prior to IMS, businesses and governments had to write their own transaction processing environments. IMS TM provides a straightforward, easy-to-use, reliable, standard environment for high performance transaction execution. In fact, much of the world's banking industry relies on IMS, including the U.S. Federal Reserve. For example, chances are that withdrawing money from an automated teller machine (ATM) will trigger an IMS transaction. Several Chinese banks have recently purchased IMS to support that country's burgeoning financial industry.
Today IMS complements DB2, IBM's relational database system, introduced in 1982. In general, IMS performs faster than DB2 for the common tasks but may require more programming effort to design and maintain for non-primary duties. Relational databases have generally proven superior in cases where the requirements, especially reporting requirements, change frequently or require a variety of viewpoint "angles" outside of the primary or original function.
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. However, nightly copies of the IMS data may be copied to relational systems such that a variety of reports and processing tasks may be performed on the data. This allows each kind of database to focus best on its relative strength.
IMS & SOA re-think what's possible
====================================
With IMS™ and SOA, you can reuse your existing assets to offer new services quickly.
"Successfully proven in large, Web-based applications. IMS is still a viable, even unmatched, platform to implement very large OLTP systems, and, in combination with Web Application Server technology, it can be a foundation for a new generation of Web-based, high-workload applications." – Gartner Group
To adapt quickly to the constantly changing global marketplace, businesses require IT systems that combine speed, reliability, and efficiency. For companies around the world, IMS provides the technology to keep critical applications running non-stop.
The IMS Service Oriented Architecture (SOA) Integration Suite offers capabilities to extend and reuse valuable assets managed by IMS. When you couple the speed and reliability of IMS with the flexibility of SOA, It's time to re-think what's possible.
In high-performance computing, IMS is:
* fast
* green
* reliable
IMS has proven that it can handle complex transactions and high workloads over the last 40 years. And while many products claim high transaction rates, none matches the efficiency of IMS. Today, this scalability helps clients maintain high responsiveness to constantly changing environments. Many companies routinely run millions of IMS transactions per day:
* At an IBM® lab, a single instance of IMS 10 completed 22,000 transactions per second, translating to high throughput (transactions per second) and low cost (MIPS per transaction).
* One U.S. shipping company completes 200 million IMS transactions per day that originate from various application servers, including external sources. Despite trying other systems, the company found that only IMS reliably handles that volume of data and meets their required response time goals.
* Several large companies run over 100 million transactions per day.
IMS provides the most efficient runtime environment by requiring less resource per unit of work than any other system available, in turn reducing a company's carbon footprint.
* IBM System z10™ uses 85% less energy than earlier versions and runs the same workload as 300 UNIX® boxes.
IMS is a mission-critical business processing environment, and its resilience provides a stable, reliable production environment. This reliability means that IMS is always ready for business. IMS proactively prevents outages instead of waiting for them to occur:
* In a banking demonstration, an IMS system using standard functions, and running 4,000 transactions per second, was stopped. IMS automatically moved to work on another IMS image, without a disruption in service.
* IMS supports mission-critical applications addressing FAA flight plans and aircraft maintenance for one large company in the southern U.S. An outage, which would ground the company, has never occurred.
* Several companies report going thousands of days without an unplanned outage. One Canadian bank reports 99.998% availability over 10 years, and only 1.5 hours of planned outages.
SOA enablement and scalability:
* open
* seamless
* reusable
* and you already own it!
SOA is a business-centric IT architectural approach that facilitates the reuse of existing assets. SOA allows for open, standard interfaces that provide any data source solution package access to any other solution package. The scalability of SOA and IMS enables your business to grow.
Get more from your IMS investment by using the tools and functions of the IMS SOA Integration Suite and re-think what's possible:
* Open: The IMS SOA Integration Suite uses the standard protocols of SOA. IMS is a provider and a consumer of services, because IMS can access any platform, and any platform can access IMS.
* Seamless: The integration of new application development into an existing application integrated development environment is seamless. Leverage skills that already exist because programmers need not learn IMS to use the tools.
* Reusable: Leverage existing IMS assets, utilize existing programming skills, and modernize existing IMS applications by using IMS technology, while opening IMS data and applications to SOA protocols. Instead of rewriting IMS code in newer programming languages, reuse the code, providing time-tested functions with stable code.
Enable IMS services
* Access existing IMS business logic with industry standard Web services
* Enable IMS as both a provider and a consumer of Web services
* Use industry standard Java™ EE applications to access existing IMS business logic
* Include IMS assets as part of your Web mashups
* Write new IMS applications in Java
* Provide rapid IMS application development and deployment, using Rational® tools
Access IMS information
* Access IMS databases from any system, anywhere, including AIX®, Linux® on System z®, Linux, HP-UX, Sun Solaris, z/OS®, and Windows®
* Use industry standard Java EE or JDBC applications to access IMS databases
* Store and retrieve XML documents in IMS databases
* View IMS databases with graphical tooling that simplifies application and Web service development
* Provide rapid IMS application development and deployment, using Rational tools
Embrace IMS and SOA now
SOA liberates business constraints by restructuring existing services so that future growth is faster, easier, and more affordable. The flexibility and agility of the IMS SOA Integration Suite help businesses respond to customer demands for new services and enter new markets more quickly.
Did we mention that you already own it?
You can derive more from your current IMS investment by using the IMS SOA Integration Suite.
* IMS SOA Integration Suite is available to IMS customers at no additional cost.
o The suite is a collection of IMS tools and functions that expands IMS application development and extends the reach of your existing IMS assets, enabling maximum participation of your IMS assets in an On-Demand or service-oriented architecture.
o Included in the IMS SOA Integration Suite is the IMS Enterprise Suite. The IMS Enterprise Suite provides components for z/OS and distributed platforms to facilitate application development, simplify IMS metadata generation, and enable IMS business event data monitoring.
* Improve programmer productivity and reduce your company's maintenance and application backlog, in turn shifting development focus from maintenance to application development.
o A financial institution in the U.S. used SOA to eliminate duplicate business logic and reduce IT maintenance costs by allowing their four million customers to access their accounts online.
* IBM IMS Tools and Tivoli® tools can help to manage your SOA systems, improving staff productivity and helping you meet service-level goals.
o A manufacturing company in Europe uses Web browsers to view existing data. The Web browsers are easier to use and retain complete security and control of the data with IMS.
* Solutions can be deployed rapidly, which means a faster time to market.
o A bank in central Europe was able to develop a new WebSphere® Application Server Web service quickly and reuse approximately 80% of existing IMS-based services.
o A European bank was able to seamlessly integrate Java workload into their banking system within one month.
IMS Overview
IMS:
=====
IMS (Information Management System) is a database and transaction management system that was first introduced by IBM in 1968. Since then, IMS has gone through many changes in adapting to new programming tools and environments. IMS is one of two major legacy database and transaction management subsystems from IBM that run on mainframe MVS (now z/OS) systems. The other is CICS. It is claimed that, historically, application programs that use either (or both) IMS or CICS services have handled and continue to handle most of the world's banking, insurance, and order entry transactions.
IMS consists of two major components, the IMS Database Management System (IMS DB) and the IMS Transaction Management System (IMS TM). In IMS DB, the data is organized into a hierarchy. The data in each level is dependent on the data in the next higher level. The data is arranged so that its integrity is ensured, and the storage and retrieval process is optimized. IMS TM controls I/O (input/output) processing, provides formatting, logging, and recovery of messages, maintains communications security, and oversees the scheduling and execution of programs. TM uses a messaging mechanism for queuing requests.
IMS's original programming interface was DL/1 (Data Language/1). Today, IMS applications and databases can be connected to CICS applications and DB2 databases. Java programs can access IMS databases and services.
IMS also stands for Intelligent Manufacturing Systems and IP Multimedia Subsystem.
History:
=========
IBM designed IMS with Rockwell and Caterpillar starting in 1966 for the Apollo program. IMS's challenge was to inventory the very large bill of materials (BOM) for the Saturn V moon rocket and Apollo space vehicle. However, by some accounts it was accepted too late in the process to make significant contributions to the Apollo program.
The first "IMS READY" message appeared on an IBM 2740 terminal in Downey, California, on 14 August 1968. IMS is still going strong over 40 years later and, over time, has seen some interesting developments as IBM System/360 technology evolved into the current z/OS and System z9 and z10 technologies. For example, IMS supports the Java programming language, JDBC, XML, and, since late 2005, Web services (though installing the JDBC driver may require licensing additional software from IBM). IMS Connect comes standard with Version 9 and higher and provides a TCP/IP interface to Message Processing Programs running in IMS Message Processing Regions.
Vern Watts was IMS's chief architect for many years. Mr. Watts joined IBM in 1956 and worked at IBM's Silicon Valley development labs until his death April 4, 2009.[1] He had continuously worked on IMS since the 1960s. [2]
IMS is reportedly IBM's highest revenue software product, and it continues to grow.
Transaction Manager:
====================
IMS is also a robust transaction manager (IMS TM, also known as IMS DC) — one of the "big three" classic transaction managers along with CICS and BEA (now Oracle) Tuxedo. A transaction manager interacts with an end user (connected through VTAM or TCP/IP, including 3270 and Web user interfaces) or another application, processes a business function (such as a banking account withdrawal), and maintains state throughout the process, making sure that the system records the business function correctly to a data store. Thus IMS TM is quite like a Web application, operating through a CGI program (for example), to provide an interface to query or update a database. IMS TM typically uses either IMS DB or DB2 as its backend database. When used alone with DB2 the IMS TM component can be purchased without the IMS DB component.
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, assuring 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.
Application
===========
Prior to IMS, businesses and governments had to write their own transaction processing environments. IMS TM provides a straightforward, easy-to-use, reliable, standard environment for high performance transaction execution. In fact, much of the world's banking industry relies on IMS, including the U.S. Federal Reserve. For example, chances are that withdrawing money from an automated teller machine (ATM) will trigger an IMS transaction. Several Chinese banks have recently purchased IMS to support that country's burgeoning financial industry.
Today IMS complements DB2, IBM's relational database system, introduced in 1982. In general, IMS performs faster than DB2 for the common tasks but may require more programming effort to design and maintain for non-primary duties. Relational databases have generally proven superior in cases where the requirements, especially reporting requirements, change frequently or require a variety of viewpoint "angles" outside of the primary or original function.
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. However, nightly copies of the IMS data may be copied to relational systems such that a variety of reports and processing tasks may be performed on the data. This allows each kind of database to focus best on its relative strength.
IMS & SOA re-think what's possible
====================================
With IMS™ and SOA, you can reuse your existing assets to offer new services quickly.
"Successfully proven in large, Web-based applications. IMS is still a viable, even unmatched, platform to implement very large OLTP systems, and, in combination with Web Application Server technology, it can be a foundation for a new generation of Web-based, high-workload applications." – Gartner Group
To adapt quickly to the constantly changing global marketplace, businesses require IT systems that combine speed, reliability, and efficiency. For companies around the world, IMS provides the technology to keep critical applications running non-stop.
The IMS Service Oriented Architecture (SOA) Integration Suite offers capabilities to extend and reuse valuable assets managed by IMS. When you couple the speed and reliability of IMS with the flexibility of SOA, It's time to re-think what's possible.
In high-performance computing, IMS is:
* fast
* green
* reliable
IMS has proven that it can handle complex transactions and high workloads over the last 40 years. And while many products claim high transaction rates, none matches the efficiency of IMS. Today, this scalability helps clients maintain high responsiveness to constantly changing environments. Many companies routinely run millions of IMS transactions per day:
* At an IBM® lab, a single instance of IMS 10 completed 22,000 transactions per second, translating to high throughput (transactions per second) and low cost (MIPS per transaction).
* One U.S. shipping company completes 200 million IMS transactions per day that originate from various application servers, including external sources. Despite trying other systems, the company found that only IMS reliably handles that volume of data and meets their required response time goals.
* Several large companies run over 100 million transactions per day.
IMS provides the most efficient runtime environment by requiring less resource per unit of work than any other system available, in turn reducing a company's carbon footprint.
* IBM System z10™ uses 85% less energy than earlier versions and runs the same workload as 300 UNIX® boxes.
IMS is a mission-critical business processing environment, and its resilience provides a stable, reliable production environment. This reliability means that IMS is always ready for business. IMS proactively prevents outages instead of waiting for them to occur:
* In a banking demonstration, an IMS system using standard functions, and running 4,000 transactions per second, was stopped. IMS automatically moved to work on another IMS image, without a disruption in service.
* IMS supports mission-critical applications addressing FAA flight plans and aircraft maintenance for one large company in the southern U.S. An outage, which would ground the company, has never occurred.
* Several companies report going thousands of days without an unplanned outage. One Canadian bank reports 99.998% availability over 10 years, and only 1.5 hours of planned outages.
SOA enablement and scalability:
* open
* seamless
* reusable
* and you already own it!
SOA is a business-centric IT architectural approach that facilitates the reuse of existing assets. SOA allows for open, standard interfaces that provide any data source solution package access to any other solution package. The scalability of SOA and IMS enables your business to grow.
Get more from your IMS investment by using the tools and functions of the IMS SOA Integration Suite and re-think what's possible:
* Open: The IMS SOA Integration Suite uses the standard protocols of SOA. IMS is a provider and a consumer of services, because IMS can access any platform, and any platform can access IMS.
* Seamless: The integration of new application development into an existing application integrated development environment is seamless. Leverage skills that already exist because programmers need not learn IMS to use the tools.
* Reusable: Leverage existing IMS assets, utilize existing programming skills, and modernize existing IMS applications by using IMS technology, while opening IMS data and applications to SOA protocols. Instead of rewriting IMS code in newer programming languages, reuse the code, providing time-tested functions with stable code.
Enable IMS services
* Access existing IMS business logic with industry standard Web services
* Enable IMS as both a provider and a consumer of Web services
* Use industry standard Java™ EE applications to access existing IMS business logic
* Include IMS assets as part of your Web mashups
* Write new IMS applications in Java
* Provide rapid IMS application development and deployment, using Rational® tools
Access IMS information
* Access IMS databases from any system, anywhere, including AIX®, Linux® on System z®, Linux, HP-UX, Sun Solaris, z/OS®, and Windows®
* Use industry standard Java EE or JDBC applications to access IMS databases
* Store and retrieve XML documents in IMS databases
* View IMS databases with graphical tooling that simplifies application and Web service development
* Provide rapid IMS application development and deployment, using Rational tools
Embrace IMS and SOA now
SOA liberates business constraints by restructuring existing services so that future growth is faster, easier, and more affordable. The flexibility and agility of the IMS SOA Integration Suite help businesses respond to customer demands for new services and enter new markets more quickly.
Did we mention that you already own it?
You can derive more from your current IMS investment by using the IMS SOA Integration Suite.
* IMS SOA Integration Suite is available to IMS customers at no additional cost.
o The suite is a collection of IMS tools and functions that expands IMS application development and extends the reach of your existing IMS assets, enabling maximum participation of your IMS assets in an On-Demand or service-oriented architecture.
o Included in the IMS SOA Integration Suite is the IMS Enterprise Suite. The IMS Enterprise Suite provides components for z/OS and distributed platforms to facilitate application development, simplify IMS metadata generation, and enable IMS business event data monitoring.
* Improve programmer productivity and reduce your company's maintenance and application backlog, in turn shifting development focus from maintenance to application development.
o A financial institution in the U.S. used SOA to eliminate duplicate business logic and reduce IT maintenance costs by allowing their four million customers to access their accounts online.
* IBM IMS Tools and Tivoli® tools can help to manage your SOA systems, improving staff productivity and helping you meet service-level goals.
o A manufacturing company in Europe uses Web browsers to view existing data. The Web browsers are easier to use and retain complete security and control of the data with IMS.
* Solutions can be deployed rapidly, which means a faster time to market.
o A bank in central Europe was able to develop a new WebSphere® Application Server Web service quickly and reuse approximately 80% of existing IMS-based services.
o A European bank was able to seamlessly integrate Java workload into their banking system within one month.
Comments
Post a Comment