IBM Systems Magazine, Mainframe - January 2009 - (Page 10)

Trends Industry signals to keep you in the know Celebrating 40 Successful Years IMS version 10 supports synchronous callout BY KENNETH BLACKMAN, YEE-RONG LAI AND JACK YUAN F orty years ago, the first “IMS READY” message was displayed and the IBM IMS* was open for business. Today, IMS continues to be IBM’s high-per for mance application and data ser ver for the IBM System z* platform. IMS version 10 continues to support new technological innovations by enabling IMS applications to call out to not on l y c om mu n ic at ion de v ic e s a nd Figure 1 application programs managed by IMS, but also to external applications and Web services through open standards. This evolution of f unctionalit y can be leveraged to build an on-demand business environment. IMS’s service oriented architecture (SOA) describes how different application programs can call out to each other as they participate in business processes. Ver sion 10 prov ides SOA-enabli ng functions for IMS application programs to integrate with other products and platforms across the Internet. 2009 Synchronous Versus Asynchronous Callout IMS has evolved to support both asynchronous and synchronous callout to external subsystems–to outside of the IMS runtime environment, and to the Internet. A call-out request is considered asynchronous if the requesting IMS application program doesn’t expect a response, or if the response message is expected to return as a different transaction. In this instance, the application program terminates and doesn’t hold up the IMS-dependent region. If a response is expected to return in the same transaction during the same unit of work, the call-out request is called a synchronous call-out request. T h e I M S a lt e r n at e pr og r a m c ont r ol blo c k (alter nate PCB) concept introduced by the I MS transaction manager (IMS TM) for asynchronous callout support enables access to communication devices and application programs managed by IMS in a logical fashion. This concept provides transparency for the IMS application program and security for end-user messages. The IMS application program doesn’t have to know the characteristics of the communication device or the network protocol when sending data. 10 J A N U A R Y/ F E B R U A R Y ibmsystemsmag.com/mainframe http://www.ibmsystemsmag.com/mainframe

Table of Contents for the Digital Edition of IBM Systems Magazine, Mainframe - January 2009

IBM Systems Magazine, Mainframe - January 2009
Table of Contents
Editor’s Desk
Trends: Celebrating 40 Successful Years
Case Study: The State of Maryland helps law enforcement agencies improve efficiency withmulti-database access."
Perfect Match: BI Solutions give mainframe customers and edge, IBM's Karl Freund says."
Leading the Pack: The business value of IBM System z virtulization leadership
BI and Analytics on the Mainframe: Debunking three myths about deploying BI on System z
Tips & Techniques: Tools Extract DB2 Statistics and DDL From the DB2 Catalog.
Product News
Advertiser’s Index
Stop Run: DB2utor Troy Coleman Danced Into an IT Career

IBM Systems Magazine, Mainframe - January 2009

https://www.nxtbook.com/nxtbooks/mspcomm/ibmsystems_mainframe_200901
https://www.nxtbookmedia.com