© 2013 IBM CorporationIMS CalloutIMS Regional User GroupSao Paulo, June 6
© 2013 IBM CorporationAcknowledgements and DisclaimersAvailability. References in this presentation to IBM products, progr...
© 2013 IBM CorporationIMS SOA Integration Suitehttp://www.ibm.com/software/data/ims/toolkit/Modernize, reuse andexpand IMS...
© 2013 IBM CorporationInbound Connectivity to IMS TMor Print utilityIMS Performance Analyzer IMS Problem InvestigatorIMSCo...
© 2013 IBM CorporationOutbound Connectivity from IMS TMIMSConnectOTMAIMS DB &XML DBIMSDB2WOLA• Asynchronous and synchronou...
© 2013 IBM CorporationIMS Callout Techniques• Asynchronous callout using insert to ALTPCB via OTMA• Synchronous Callout us...
© 2013 IBM CorporationIMS Callout• Enable IMS applications as Service Requesters– IMS Application can be an integration fo...
© 2013 IBM CorporationAsynchronous Callout• Asynchronous Callout– IMS application invokes external applications without wa...
© 2013 IBM CorporationSynchronous Callout• Synchronous Callout– IMS application invokes external application and waits for...
© 2013 IBM CorporationIMS Asynchronous and Synchronous CalloutSync CalloutResponseCallout RequestAsync CalloutResponseIMS ...
© 2013 IBM CorporationIMS Synchronous Callout
© 2013 IBM CorporationIMS Synchronous Callout Overview• IMS 10 added DLI “ICAL” call for synchronous callout request• Time...
© 2013 IBM CorporationIMS application - DL/I ICALCALL AIBTDLI USING ICAL, AIB, REQ-AREA, RESP-AREA.where:• ICAL is the cal...
© 2013 IBM CorporationIMS application - DL/I ICAL …• AIB– AIBSFUNC = SENDRECV– AIBRSNM1 = 8 byte OTMA Descriptor name– AIB...
© 2013 IBM CorporationIMS application - DL/I ICAL…AIBFor example:DescriptornameTimeoutRequest Area LengthResponse Area Len...
© 2013 IBM CorporationD destname keywordsWhere:destname is destination names and can be masked by ending in an *keywords a...
© 2013 IBM CorporationManaging Callout
© 2013 IBM Corporation• /DISPLAY ACTIVE REGION– New status for region waiting on synchronouscallout response• WAIT-CALLOUT...
© 2013 IBM CorporationAfter ICAL request is sent …RegionStatusTPIPEStatusSample Commands output
© 2013 IBM Corporation• Monitor synchronous callout processing• Minimize resource contention– Try to issue ICAL requests b...
© 2013 IBM CorporationIMS 13 Callout Enhancements
© 2013 IBM CorporationSynchronous Program Switch• Extend IMS Synchronous Callout to invoke another IMS Application– Synchr...
© 2013 IBM CorporationRetrieve Truncated Messages• New ICAL “RECEIVE” subfunction code– With an expanded response area• Re...
© 2013 IBM CorporationIMSApplicationWebSphereMQIMSOTMAAsync Callout to WebSphere MQ via MQ Bridge• OTMA Descriptor enhance...
© 2013 IBM CorporationThank You!
Upcoming SlideShare
Loading in …5
×

IMS Callout - IMS UG June 2013 Sao Paulo

498 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
498
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
26
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

IMS Callout - IMS UG June 2013 Sao Paulo

  1. 1. © 2013 IBM CorporationIMS CalloutIMS Regional User GroupSao Paulo, June 6
  2. 2. © 2013 IBM CorporationAcknowledgements and DisclaimersAvailability. References in this presentation to IBM products, programs, or services do not imply that they will be available in allcountries in which IBM operates.© Copyright IBM Corporation 2013. All rights reserved.– U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.IBM, the IBM logo, ibm.com, IMS, DB2, CICS and WebSphere MQ are trademarks or registered trademarks of International BusinessMachines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their firstoccurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarksowned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in othercountries. A current list of IBM trademarks is available on the Web at “Copyright and trademark information” atwww.ibm.com/legal/copytrade.shtmlOther company, product, or service names may be trademarks or service marks of others.The workshops, sessions and materials have been prepared by IBM or the session speakers and reflect their own views. They areprovided for informational purposes only, and are neither intended to, nor shall have the effect of being, legal or other guidance or adviceto any participant. While efforts were made to verify the completeness and accuracy of the information contained in this presentation, it isprovided AS-IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of,or otherwise related to, this presentation or any other materials. Nothing contained in this presentation is intended to, nor shall have theeffect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of theapplicable license agreement governing the use of IBM software.All customer examples described are presented as illustrations of how those customers have used IBM products and the results they mayhave achieved. Actual environmental costs and performance characteristics may vary by customer. Nothing contained in thesematerials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specificsales, revenue growth or other results.
  3. 3. © 2013 IBM CorporationIMS SOA Integration Suitehttp://www.ibm.com/software/data/ims/toolkit/Modernize, reuse andexpand IMS transactionOpen and directaccess to IMS DataIMSTMIMSDBCJavaMFSDL/I DataIMS ConnectAPIIMS Enterprise SuiteSOAPGatewayIMS TMResourceAdapterIMS MFSWeb SolutionsIMS Web 2.0SolutionsXML DataPL/ICOBOLFull Java EE, webservice and SOA accessto and from IMStransactionsLight-weight webservice provider andconsumer solution forIMSSimplify use of writingIMS Connect User-written applicationsModernize, web andSOA enabled MFS-based IMS transactionsCreate feeds andintegrate IMStransactions withWeb 2.0 appWebSphere Write and run IMSapplication in Javato leverage newskillsIMS Web 2.0SolutionsIMS Open DBand UniversalJDBC driversIMS Explorerfor DevIMS UniversalDB ResourceAdapterWebSphereCreate feeds andintegrate IMS datawith Web 2.0 appAccess IMS Data usingSQL directly fromSystem z anddistributed platforms viaIMS ConnectStore and RetrieveXML data from IMSDBProvide visual view of IMSdata and generatemetadata classes for newapplication developmentAccess IMS Data fromJava EE appIMS DBWeb ServicesExpose an IMSdatabase query asWeb ServicesNo additional cost for IMS license usersLeverage open standards
  4. 4. © 2013 IBM CorporationInbound Connectivity to IMS TMor Print utilityIMS Performance Analyzer IMS Problem InvestigatorIMSConnectOTMAIMS DB &XML DBIMSWebSphere ServersWAS, WESB, WTX,WMB, BPMIMS SOAPGatewayWebSphereDataPowerConnect API(Java, C)WMQMQ ClientRYO ClientMobileWebServiceConsumerIMS TMResourceAdapterWAS – WebSphere Application ServerWOLA - WebSphere z/OS Optimized Local AdaptersWESB – WebSphere Enterprise Service BusWTX – WebSphere Transformation ExtenderWMB – WebSphere Message BrokerBPM - IBM Business Process Manager (BPM) AdvancedIBM MashupCenter /WebSpheresMashWeb 2.0ClientDB2WOLAJCAJMS or MQ APISOAPover IPWMB &DataPowerMQ IMSBridgeMQ TriggerMonitorIMSIMSCONNECTCONNECTExtensionsExtensionsArchivejournalXCFTCP/IPCloudIMSAPPIMSCatalog
  5. 5. © 2013 IBM CorporationOutbound Connectivity from IMS TMIMSConnectOTMAIMS DB &XML DBIMSDB2WOLA• Asynchronous and synchronous capabilitiesIMS TMResourceAdapterWASIMS SOAPGatewayWMQMQ ServerRYO ServerWebServiceProviderEventProcessingWBE, WBMWAS – WebSphere Application ServerWOLA - WebSphere z/OS Optimized Local AdaptersWBE – WebSphere Business EventsWBM – WebSphere Business MonitorWMB – WebSphere Message BrokerRYO Server - .Net, BizTalk, Oracle SP, SAP, PayPalservices, and any application server, etc.WMBIMSAPPIMSCatalogDB2 for z/OSGatewayAny DB2PlatformWebSphereDataPower
  6. 6. © 2013 IBM CorporationIMS Callout Techniques• Asynchronous callout using insert to ALTPCB via OTMA• Synchronous Callout using ICAL• Asynchronous program switch• Synchronous program switch (IMS 13)• Callout via External Subystem Attach Facility– DB2 Stored Procedure– WebSphere MQ– Websphere Optimized Local Adapter• User Written TCP/IP Synchronous• Advanced Program-to-Program Communication (APPC)
  7. 7. © 2013 IBM CorporationIMS Callout• Enable IMS applications as Service Requesters– IMS Application can be an integration focal point in the enterprise– Interoperate with business logic outside the IMS environment– Callout to Java EE apps (EJB and MDB) and Web Services using WebSphereApplication Server and IMS TM Resource Adapter– Callout to Web services providers (e.g. Microsoft .NET) using SOAP Gateway– Callout to other applications• Two Flavors– Asynchronous– Synchronous
  8. 8. © 2013 IBM CorporationAsynchronous Callout• Asynchronous Callout– IMS application invokes external applications without waiting for response.• DL/I ISRT ALTPCB• Destination can be– Another IMS application (program switch)– An OTMA destination» Sent to any OTMA clients, such as IMS Connect or WMQ» Tpipe name specified via DRU exits or OTMA descriptor.– Any response sent back is a new transaction
  9. 9. © 2013 IBM CorporationSynchronous Callout• Synchronous Callout– IMS application invokes external application and waits for the response.• DL/I ICAL• Supports timeout capability and large messages• Secondary application is not in the same two-phase commit scope– IMS application waits until the response is returned or the request receives atimeout– Callout response is sent back to the same transaction that initiated it
  10. 10. © 2013 IBM CorporationIMS Asynchronous and Synchronous CalloutSync CalloutResponseCallout RequestAsync CalloutResponseIMS Application 1IMS Application 2Async: ISRT ALTPCBSync: ICAL
  11. 11. © 2013 IBM CorporationIMS Synchronous Callout
  12. 12. © 2013 IBM CorporationIMS Synchronous Callout Overview• IMS 10 added DLI “ICAL” call for synchronous callout request• Timeout support to optionally terminate callout request and free thedependent region• Enhanced IMS commands to view synchronous callout status and stopthe callout processing• Support messages larger than 32K without segmentation• Provide management of the correlation of a synchronous callout requestand response• Enhanced OTMA Resume TPIPE/Send Only protocol and RoutingDescriptor function for retrieving synchronous callout requests andsending responses
  13. 13. © 2013 IBM CorporationIMS application - DL/I ICALCALL AIBTDLI USING ICAL, AIB, REQ-AREA, RESP-AREA.where:• ICAL is the call verb (available on AIBTDLI only) and SENDRECV is thesub-function code• REQ-AREA is the Request data area for sync callout• RESP-AREA is the Response data area for returned dataNote: REQ-AREA and RESP-AREA do not specify LLZZ, data can be > 32KFor example:ICALIOAreas
  14. 14. © 2013 IBM CorporationIMS application - DL/I ICAL …• AIB– AIBSFUNC = SENDRECV– AIBRSNM1 = 8 byte OTMA Descriptor name– AIBRSFLD = Timeout value• 4 byte field for time value in 100th seconds. System default is 10 sec.– AIBOALEN = Request area length• As an input parameter: 4 byte field contains the length of the request area• As an output parameter: Actual length of the response message updatedby IMS only when partial data is returned (AIB return code x100, AIBreason code x00C‘).– AIBOAUSE = Response area length• As an input parameter: 4 byte field contains the length of the responsearea• As an output parameter: Length of the response message placed in theresponse area. When partial data is returned because the response area isnot large enough, AIBOAUSE contains the length of data returned in theresponse area and AIBOALEN contains the actual length of the responsemessage.
  15. 15. © 2013 IBM CorporationIMS application - DL/I ICAL…AIBFor example:DescriptornameTimeoutRequest Area LengthResponse Area LengthOutput returncodes
  16. 16. © 2013 IBM CorporationD destname keywordsWhere:destname is destination names and can be masked by ending in an *keywords are: TYPE=IMSCONTMEMBER=nameTPIPE-nameSMEM=YES|NOADAPTER=adapnameCONVERTR=convnameSYNTIMER=timeout (If both ICAL & Descriptor specify timeout, the lower value is used)D OTMDEST1 TYPE=IMSCON TMEMBER=HWS1 TPIPE=TPIPE1 SYNTIMER=5000OTMA Destination Routing Descriptor• IMS OTMA Destination Routing Descriptors externalize the routing definitions andspecifications for callout messages without IMS user exits. It is read and initialized at IMSstartup.– Use ‘D’ descriptor type in DFSYDTx member of IMS.PROCLIB.• IMS 11 provides Type-2 UPDATE commands to dynamically create, update,or query the descriptorsUPDATE OTMADESC NAME(OTMASYN) SET(SYNTIMER(5000))For example:For example:D SOAPGW1 TYPE=IMSCON TMEMBER=HWS1 TPIPE=HWS2SOAPD SOAPGW1 ADAPTER=HWSXMLA0 CONVERTR=XMLCNVTR SYNTIMER=2000
  17. 17. © 2013 IBM CorporationManaging Callout
  18. 18. © 2013 IBM Corporation• /DISPLAY ACTIVE REGION– New status for region waiting on synchronouscallout response• WAIT-CALLOUT– Continuation line for region waiting onsynchronous callout response• TMEMBER name TPIPE: tpipename• /DIS TMEMBER TPIPE– WAIT-S (WT-S)• The transaction pipe is waiting for an ACK or NAKfor a synchronous callout message• /DIS TMEMBER TPIPE SYNC– Display the detailed sync callout messagecount and status• /PSTOP– Clear the wait in the region– Dequeues synchronous callout messages from theTPIPE• /STOP REG ABDUMP– Clear the wait in the region and terminate theapplication program• /STOP TMEMBER TPIPE– Clear state of all messages for the TPIPE• /STOP OTMA– Clear all the ICAL messages for all the TPIPEs.– New ICAL synchronous callout requests rejectedNote: The stop commands return AIBRETRN= 100 and AIBREASN = 10C to ICALEnhanced IMS commands
  19. 19. © 2013 IBM CorporationAfter ICAL request is sent …RegionStatusTPIPEStatusSample Commands output
  20. 20. © 2013 IBM Corporation• Monitor synchronous callout processing• Minimize resource contention– Try to issue ICAL requests before obtaining locks• Define appropriate number of dependent regions– You may want additional transaction classes to segregate workloads• Define timeout values for ICAL and/or OTMA descriptors• Manage commit, backout and timeout -- UOWs areindependent• Multiple response messages from synchronous programswitch (IMS V13)Some Callout Considerations
  21. 21. © 2013 IBM CorporationIMS 13 Callout Enhancements
  22. 22. © 2013 IBM CorporationSynchronous Program Switch• Extend IMS Synchronous Callout to invoke another IMS Application– Synchronous flows use DL/I ICAL– Asynchronous flows still use DL/I ISRT• OTMA Descriptor defines the destinationBenefits– Provides a single DL/I call to request a synchronous service regardless of where that service resides– Simplifies integration and improves usabilityICAL DEST1ICAL TRANBTRANAIMS CTL RegionIMSConnectWebSphereIMS TMRAIMS SOAPGatewayTCP/IPRYO pgmOTMAMSG-QDestinationDescriptorTYPE(IMSCON)TRANBGU IOPCBISRT IOPCBDestinationDescriptorTYPE(IMSTRAN)1234567GU, IOPCBApplications can issue multiple ICALs to differentdestination TYPEsSynchronous calloutSynchronous program switchWebSphereDataPower
  23. 23. © 2013 IBM CorporationRetrieve Truncated Messages• New ICAL “RECEIVE” subfunction code– With an expanded response area• Retrieves the response message after an ICAL “SENDRECV” is issued with aninadequate response area specification and gets partial data (AIB RC X’100’,AIB RS X’00C’)– IMS keeps a copy of the entire response message in the control regionprivate storage• Until a subsequent ICAL “SENDRECV”, syncpoint, or application termination• Benefit– Provides the ability to complete the retrieval of a reply message that hadbeen truncated due to a too small output area• Without having to re-issue a complete ICAL “SENDRECV” and associatednetwork transmission costs
  24. 24. © 2013 IBM CorporationIMSApplicationWebSphereMQIMSOTMAAsync Callout to WebSphere MQ via MQ Bridge• OTMA Descriptor enhancements– New TYPE=MQSERIES to define WebSphere MQ destination• Provides asynchronous callout and messaging support (DL/I ISRT ALTPCB)– New option to allow exits to be called to override descriptor• Applies to all destination descriptorsBenefits– Eliminates need to write an OTMA user exit to recognize an MQ destination– Simplifies integration and improves usability
  25. 25. © 2013 IBM CorporationThank You!

×