By Dean Meltz
IMS Version 11 (IMS V11) is the latest generation of this cornerstone product. Not many products in today's world can match IMS's speed, reliability, flexibility, longevity, and history of success.
As with every new version, IMS V11 continues to support core applications that are at the heart of business processing and also provides the flexibility that is required for new applications. This new version will be available for ordering on 30 October, 2009.
IMS V11 contains enhancements to all the major components: IMS DB, IMS TM, and IMS System. This article summarizes some of the new IMS V11 enhancements.
1. IMS V11 DB enhancements
A. Open Database
The Open Database function provides direct SQL access to IMS databases. Using the Open Database components, z/OS and distributed Java application programs can directly access any database that is managed by IMS DB on any logical partition (LPAR) in an IMSplex. The components that enable this functionality are new application drivers (the IMS Universal drivers) that communicate with IMS DB (using DRDA protocols) through IMS Connect and the Open Database Manager (ODBM), which is a new Common Service Layer component. See Figure below.
The IMS Universal drivers can be used by distributed Java applications that access IMS Version 9 or IMS Version 10 databases, as long as the IMS Version 9 or IMS Version 10 systems are part of a mixed-version IMSplex that includes an IMS Version 11 system (along with its ODBM, Structured Call Interface (SCI), and IMS Connect address spaces) and the appropriate coexistence APARs/PTFs are installed.
The ODBA interface is also enhanced as part of Open Database enhancement.
For an overview of the Open Database enhancement, go to http://publib.boulder.ibm.com/infocenter/imzic/topic/com.ibm.ims11.doc.rpg/ims_releaseplanningimpact_opendb.htm.
B. Database quiesce
The DB quiesce function enables you to create a coordinated recovery point across an IMSplex for IMS Fast Path data entry databases (DEDBs), Fast Path areas, full-function databases (including High Availability Large Databases - HALDBs), and database groups, without taking your resources offline or causing applications to encounter an unavailable database.
For an overview of the DB quiesce enhancement, go to http://publib.boulder.ibm.com/infocenter/imzic/topic/com.ibm.ims11.doc.rpg/ims_releaseplanningimpact_dbquiesce.htm.
C. Fast Path 64-bit buffer manager
The Fast Path 64-bit buffer manager autonomically controls the number and size of Fast Path buffer pools, including buffer pools for DEDBs, main storage databases (MSDBs), and system services. This autonomic control eliminates the need for users to manually set buffer pool specifications during system definition. The Fast Path 64-bit buffer manager also places the DEDB buffer pools above the bar in 64-bit storage, which reduces the usage of ECSA storage.
For an overview of the Fast Path enhancements, go to http://publib.boulder.ibm.com/infocenter/imzic/topic/com.ibm.ims11.doc.rpg/ims_fpenh_chap.htm.
2. IMS V11 System enhancements
IMS V11 provides enhancements to existing commands and introduces new commands. Most of these enhancements are provided in type-2 commands, which support the IMS strategy of enhancing the capability of single point of control (SPOC) applications that issue type-2 commands through the Operations Manager (OM) API or REXX SPOC API. The command enhancements affect the following areas or functions: DB quiesce, Fast Path, IMS TM, Open Database, and user exits.
DBRC in IMS V11 provides the optional ability to run on Base Primitive Environment (BPE) and also provides new serviceability options for the RECON data sets. A BPE-based DBRC provides improved user exit management and trace support. This support is totally optional. Either start DBRC with current procedures or use a new startup JCL member that uses BPE. One of the advantages of running DBRC on BPE is the ability to update user exits without shutting IMS or DBRC down. Two other enhancements to DBRC are the ability to delete old or expired recovery-related information from the RECON data set (using the new CLEANUP.RECON command) and the ability to override DBRC security for non-production copies of the RECON data set, which enables non-authorized personnel to access and manipulate the data in the RECON.
For an overview of the DBRC enhancements, go to http://publib.boulder.ibm.com/infocenter/imzic/topic/com.ibm.ims11.doc.rpg/ims_dbrcenh_chap.htm.
C. IMS Connect
As mentioned previously, IMS Connect now provides TCP/IP access to IMS DB as part of the Open Database enhancement. IMS Connect also provides many enhancements in its IMS TM functionality.
3. User exits
The user exit enhancements introduce new functions in IMS V11 that apply to the following exit points: Early Initialization, CQS Event and CQS Structure Event (all three introduced in IMS V11), and Restart (introduced in IMS V10). Information about the routines for these exit points can be queried (using the new QUERY USEREXIT command), and can be modified, brought online, or deleted online (using the new REFRESH USEREXIT command).
As part of the user exit enhancements, the standard user exit parameter list (SXPL) is enhanced.
For an overview of the user exit enhancements, go to http://publib.boulder.ibm.com/infocenter/imzic/topic/com.ibm.ims11.doc.rpg/ims_releaseplanningimpactuserexitenh.htm.
3. IMS V11 Transaction Manager enhancements
A. IMS Connect
The enhancements to IMS Connect for IMS TM include ACK timeout improvements, connection improvements, data store-level support for OTMA super member groups, diagnostic improvements, error-checking improvements, exit improvements, transaction expiration support, user-defined message support (without disconnection), improvements in distributed WebSphere Application Server support, and usability improvements.
For an overview of the IMS Connect enhancements for IMS TM, go to http://publib.boulder.ibm.com/infocenter/imzic/topic/com.ibm.ims11.doc.rpg/ims_releaseplanningimpact_icon_1.htm.
The new CM0 ACK timeout support allows you to detect a hang condition in an OTMA transaction pipe and reroute commit mode 0 (commit-then-send) transactions to a timeout message queue so that the remainder of the I/O PCB output on the transaction pipe can continue to flow normally. As part of the command enhancements for IMS TM, five of the new commands provide the ability to monitor the workload of OTMA messages and dynamically change the routing of messages without needing an IMS restart.
C. Transaction expiration
IMS V11 provides the ability to specify an expiration value for transactions, thus providing relief from having to process these unnecessary messages. The expiration value on all messages is checked by IMS when an application issues its first Get Unique (GU) call to the IOPCB for each unit of work. If the time specified in the expiration value has passed, IMS discards the transaction. If the message comes through OTMA, the expiration value is checked by OTMA when the message is received from XCF and is checked again before the message is enqueued to IMS. If the time specified in the expiration value has passed, OTMA discards the transaction.
For an overview of the transaction expiration enhancements, go to http://publib.boulder.ibm.com/infocenter/imzic/topic/com.ibm.ims11.doc.rpg/ims_releaseplanningimpacttransexp.htm.
For further information, here are additional resources:
“IMS: An Exciting Future Ahead” at
"IMS Version 11 Release Planning" at http://publib.boulder.ibm.com/infocenter/imzic/topic/com.ibm.ims11.doc/ims_planhome.htm
"IMS Version 11 Feature Overview" at http://download.boulder.ibm.com/ibmdl/pub/software/data/sw-library/ims//IMS_11_Overview.pdf
"Bank of America touts mainframe work as a safe career" at http://www.computerworld.com/s/article/9138256/Bank_of_America_touts_mainframe_work_as_a_safe_career?source=CTWNLE_nlt_pm_2009-09-18
“Mainframe Computing Set for Rebirth” at
“600+ Universities offer courses in mainframe skills” at