Monday, 12 October 2009

IMS Version 11

I mentioned last week about IMS Version 11, which has been around in a pre-release version for nearly a year. Well, the good news is that it becomes generally available on 30 October 2009.

Here are some of the highlights.

Database Manager enhancements:

• IMS Open Database support offers direct distributed TCP/IP access to IMS data, providing cost efficiency, enabling application growth, and improving resilience.
• Broadened Java and XML support and tools can ease IMS development and access to IMS data.
• IMS Fast Path Buffer Manager, Application Control Block library, and Local System Queue Area storage reduction utilize 64-bit storage to improve availability and overall system performance.
• Enhanced commands and user exits simplify operations and improve availability.

Transaction Manager enhancements:

• IMS Connect (the TCP/IP gateway to IMS transactions, operations, and now data) enhancements offer improved IMS flexibility, availability, resilience, and security.
• Broadened Java and XML tooling eases IMS application development and connectivity, and enhances IMS Web services to assist developers with business transformation.
• Enhanced commands and user exits simplify operations and improve availability.
• IMS Application Control Block library and Local System Queue Area reduction utilize 64-bit storage to improve availability and system performance.

Also, last week saw latest webinar from Virtual IMS Connection (www.virtualims.com), which was entitled, "Mainframe integration is not a strategy - get your MIPS back while delivering value today", and was presented by Rob Morris, Chief Strategy Officer with GT Software.

Rob suggested that the goals for integration were: fast, agile; flexible; adaptable; consistent; and justifiable. And Rob went on to pose the question whether the goals for mainframe integration should be any different. He then suggested that the mainframe was different, saying:

• Platform:
  • Cost of mainframe operations
  • Proprietary sub-systems and APIs
  • Limited resources.
• It goes beyond combining the words Mainframe, Web, and Services
• "Free Tools" are not free:
  • MIPS costs
  • Simplistic design requires additional tools.

Dusty Rivers, who is described on the GT Software blog as an IMS SOA Evangelist, was also on hand to give the user group a rapid demonstration of GT Software's Ivory product.

Some of the advantages they listed with Ivory are that:

• Services are deployed instantly
• Can be deployed to mainframe (CICS, started task, z/Linux) or off-mainframe (Windows or Linux)
• Leverages zLinux and specialty engines to slash costs.

Rob also explained how users could save money because the work is moved from the GPP (General Purpose Processor) to the IFL specialty processor. Which, as we've seen in these blogs, is the route being taken by a number of software vendors.

So, as I said last week, IMS is an interesting technology.

If you need anything written, contact Trevor Eddolls at iTech-Ed.
Telephone number and street address are shown here.