®IMS Version 13IMS 13 TM and Integration EnhancementsKenny Blackman – kblackm@us.ibm.comSuzie Wendler – wendler@us.ibm.com...
IMS Version 13AgendaIMS TM Enhancements– OTMA Enhancements– ISC Over TCP/IP– Synchronous Program SwitchIMS IntegrationAuto...
IMS Version 13OTMA EnhancementsOTMA (Open Transaction Manager Access) value proposition– Strengthens IMS as a foundation f...
IMS Version 13IMS 13 OTMA Enhancements ...OTMA early termination notification– Autonomic enhancement for higher availabili...
IMS Version 13IMS 13 OTMA Enhancements ...A new global flood control option that enforces the global flood limit– Rejects ...
IMS Version 13IMS 13 OTMA Enhancements ...A special new client descriptor (optional)– Using existing ‘M’ descriptor type i...
IMS Version 13IMS 13 OTMA Enhancements ...Enhancements to OTMA destination descriptors• Simplify asynchronous messaging to...
IMS Version 13IMS 13 OTMA Enhancements ...New mechanism to differentiate between CM0 versus CM1 outputmessage counts for H...
IMS Version 13IMS 13 OTMA Enhancements ...Additional console WTO messages– Enhances automation capability for environments...
IMS Version 13IMS 13 OTMA Enhancements ...Concerted effort to reduce MIPS in IMS 13 includes OTMA– More efficient hashing ...
IMS Version 13IMS 13 OTMA Enhancements ...Enhancement to ICAL synchronous callout request– Addresses partial response mess...
IMS Version 13IMS 13 ISC Over TCP/IPISC Over TCP/IP value proposition– New option that supports TCP/IP network connectivit...
IMS Version 13IMS 13 ISC Over TCP/IP...Highlights– Supports both static and dynamic terminals• Static terminal definitions...
IMS Version 13IMS 13 ISC Over TCP/IP...Functionality– CICS IPIC (IP Interconnectivity) provides START / RETRIEVE(asynchron...
IMS Version 13IMS 13 ISC Over TCP/IP...IMS terminal definitions– Static terminals:• TYPE, TERMINAL, VTAMPOOL and SUBPOOL m...
IMS Version 13IMS 13 ISC Over TCP/IP...The Common Service Layer (CSL) provides the Structured CallInterface (SCI) for comm...
IMS Version 13IMS 13 ISC Over TCP/IP...IMS1 CICS1Parallel session 1w/ Security context 1TERMINALNAME=CICSA1SUBPOOLNAME=SSN...
IMS Version 13IMS 13 Synchronous Program SwitchNew capability that enhances the DL/I ICAL support– Allows an IMS applicati...
IMS Version 13IMS 13 Synchronous Program Switch...Value Proposition– Modernization of the IMS application infrastructure• ...
IMS Version 13IMS 13 Synchronous Program Switch...Highlights– An enhancement to the DL/I ICAL to invoke another IMS applic...
IMS Version 13IMS 13 Synchronous Program Switch...Uses OTMA Destination Routing Descriptors– Which externalize the routing...
IMS Version 13IMS 13 Synchronous Program Switch...Usage examples– Applications can issue multiple ICALs to different desti...
IMS Version 13IMS 13 Synchronous Program Switch...Usage examples...– The IMS application environment supports recursive re...
IMS Version 13IMS 13 Synchronous Program Switch...Implications– New design considerations• Timeout values• Transaction Exp...
IMS Version 13IMS 13 Integration EnhancementsIMS Enterprise Suite 2.2 SOAP Gateway UpdatesIMS Enterprise Suite 2.2 Connect...
IMS Version 13IMS .NET Data Provider REQUIREMENT.NET Applications access IMS TM transaction processingprograms– SOAP proto...
IMS Version 13IMS .NET Data Provider ArchitectureDRDAIMS 13Application ServerODBMDDMIMS ConnectTCPIPIMS 13SQLcallsSCIOMIMS...
IMS Version 13IMSConnectIMSIMS SOAPGatewayAdapterTaskManagerZ/OS32 0IVTNO DISPLAY LAST1<?xml version="1.0"?><soap:Envelope...
IMS Version 13Advanced Installation and MaintenanceServer is divided into three components• Imsserver – can be mounted as ...
IMS Version 13WS-SecurityWS-Security SAML unsigned tokens for synchronous calloutapplications– Originating Userid (PSTUSID...
IMS Version 13End-to-end Transaction Tracking – Provider Scenario(correlation based on Tracking ID)IMS ES 2.2SOAPGatewayIM...
IMS Version 13IMS ES 2.2 Connect API for JavaIMS and IMS Connect type-2 commandsPerformance EnhancementsSupport for SendOn...
IMS Version 13IMS Service ConsumerSendOnly synchronous callout response messages with acknowledgement– client application ...
IMS Version 13Performance dataFor inbound, 16,000 transactions per second using V2R2 which is a 3%improvement over V2R1For...
IMS Version 13See database relationshipschange DBD fieldattributesIMS Enterprise Suite V2.2 Explorer for Development35Gene...
IMS Version 13IMS ES 2.2 – Importing Data StructuresImporting data structures– metadata field layouts imported from data s...
IMS Version 13Data Source Explorer ViewIndication of the PROCOPTS in effect for each PCBIndication added to Tables (Segmen...
IMS Version 13IBM Data Studio V3.2 support for IMSIBM® Data Studio support for pureQuery with IMS– Can generate pureQuery ...
IMS Version 13DLIModelIMS Enterprise suite for z/OS , V2.1 is the last release to provide theDLIModel Utility plug-in.Expl...
IMS Version 13IMS Explorer for AdministrationWeb Browser– Graphically administer IMS Databases and transactions– View IMSP...
IMS Version 13Explorer for Administration – IMSPlex Resources4141
IMS Version 13Explorer for Administration – Manage Transactions4242
IMS Version 13Explorer for Administration – Programs View4343
IMS Version 13Explorer for Administration – Databases View4444
Upcoming SlideShare
Loading in …5
×

IMS13TM Integration - IMS UG May 2013 Dallas

172 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
172
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

IMS13TM Integration - IMS UG May 2013 Dallas

  1. 1. ®IMS Version 13IMS 13 TM and Integration EnhancementsKenny Blackman – kblackm@us.ibm.comSuzie Wendler – wendler@us.ibm.com© 2013 IBM CorporationSuzie Wendler – wendler@us.ibm.com
  2. 2. IMS Version 13AgendaIMS TM Enhancements– OTMA Enhancements– ISC Over TCP/IP– Synchronous Program SwitchIMS IntegrationAutonomicsModernizationGUI2IMS Integration– IMS Enterprise Suite 2.2 SOAP Gateway Updates– IMS Enterprise Suite 2.2 Connect API for Java Updates– IMS Enterprise Suite 2.2 Explorer for Development– IMS Explorer for Administration
  3. 3. IMS Version 13OTMA EnhancementsOTMA (Open Transaction Manager Access) value proposition– Strengthens IMS as a foundation for open integration technologies• Used by:– IMS Connect: clients include IMS TM resource adapter and WAS,WMB, WESB; DataPower; IMS Soap Gateway, ...– IMS MQ Bridge: clients include WMB, RYO, ...3– IMS MQ Bridge: clients include WMB, RYO, ...– OTMA CI: clients include WOLA– IMS Connect API: clients include WebSphere Smash– ...– All of which support cloud technologies and enterprise mobility
  4. 4. IMS Version 13IMS 13 OTMA Enhancements ...OTMA early termination notification– Autonomic enhancement for higher availability that allows OTMA clients to beinformed of an IMS shutdown earlier in the termination process• Potentially reduces unsuccessful attempts to send in new transactionmessages that cannot be processed– Can expedite shutdown processing4– Can expedite shutdown processing– Planned outages (e.g., /CHE FREEZE | DUMPQ | PURGE)• Sends resource monitor protocol message during Phase 1 of IMS shutdown– Unplanned outages (e.g. abend)• OTMA issues XCF IXCLEAVE immediately after the log buffers are purged• Function being added to IMS 12: APAR PM73869
  5. 5. IMS Version 13IMS 13 OTMA Enhancements ...A new global flood control option that enforces the global flood limit– Rejects new transaction input and protects IMS from storage exhaustion• Versus just a warning message– Note: Individual Member level flood control is unchanged• Warning at 80%, Rejection at 100%, Relief at 50%• Enabled by5• Enabled by– Issuing “/DIS TMEMBER ALL INPUT xxx” command• Previous releases caused only a warning– Specifying INPT value in a special new member client descriptor• Reserved name of DFSOTMA
  6. 6. IMS Version 13IMS 13 OTMA Enhancements ...A special new client descriptor (optional)– Using existing ‘M’ descriptor type in DFSYDTx member of IMS.PROCLIB.M client-name keywordsWhere:client-name is DFSOTMA6client-name is DFSOTMAkeywords are:INPT= <VALID> global flood control limitDRU= <Ignored>T/O= <Ignored>MAXTP= <VALID> global max number of tpipes that can be createdM DFSOTMA INPT=22222– New system client name for all the OTMA members,DFSOTMA, is introduced to set global valuesFor example:
  7. 7. IMS Version 13IMS 13 OTMA Enhancements ...Enhancements to OTMA destination descriptors• Simplify asynchronous messaging to WMQ• Remove the need to code the DFSYPRX0/DFSYDRU0 exits• Provide dynamic change capability with the Type-2 commands– New descriptor TYPE={MQSERIES}7– New descriptor TYPE={MQSERIES}• Provides asynchronous callout and messaging support (ISRT ALTPCB)– Specification of EXIT={YES | NO}• Determines whether or not the OTMA exits are to be called– Corresponding enhancement to IMS Type-2 OTMADESC commands• [CREATE | UPDATE | DELETE |QUERY] OTMADESC– Recoverable across warm and emergency restarts
  8. 8. IMS Version 13IMS 13 OTMA Enhancements ...New mechanism to differentiate between CM0 versus CM1 outputmessage counts for HOLDq-capable clients– Can help analyze potential bottlenecks– Enhancement to /DISPLAY TMEMBER TPIPE command and output• Provides separate counts for the two output queuesHOLDq is a TPIPE secondary queue usedfor three types of messages:• ALTPCB messages chained to thefirst control block used for IOPCB output• Send-only messages• Rejected IOPCB output8– PRIMARY versus HOLDq• Applicable only to HOLDq-capable clients, e.g. IMS Connect– Output messages retrieved using Resume TPIPE protocol• Only affects non-shared queue systems– New OUTPUT display parameter is mutually exclusive with SYNC and QCNTparametersDFS000I MEMBER/TPIPE ENQCT DEQCT QCT INPCT STATUS SMEMDFS000I HWS1DFS000I -CLIENT03 1 1 0 1 PMRYDFS000I -CLIENT03 1 0 1 0 HLDQDFS000I -9999 0 0 0 1 PMRYDFS000I -CLIENT02 1 1 0 1 PMRYDFS000I -CLIENT04 1 1 0 1 PMRYDFS000I -CLIENT04 1 0 1 0 HLDQ
  9. 9. IMS Version 13IMS 13 OTMA Enhancements ...Additional console WTO messages– Enhances automation capability for environments that look at WTOs• Previously just MTO messagesDFS0062W LOAD FAILED FOR DRU exitDFS1281E (N)ACK ON NON-EXISTING TPIPE= tpipe FROM MEMBER= memberDFS1283E (N)ACK ON NON-EXISTING BLOCK IN TPIPE= tpipe MEMBER= member TOKEN= tokenDFS1284E (N)ACK ON NON-WAITING BLOCK IN TPIPE= tpipe MEMBER= member TOKEN= token9DFS1284E (N)ACK ON NON-WAITING BLOCK IN TPIPE= tpipe MEMBER= member TOKEN= tokenDFS1297E OTMA TRANCOMPLETED. NO OUTPUT DUE TO MSG SIZE EXCEEDED 32K (32767)DFS1964E DESTINATION TMEMBER ... TPIPE or DESTINATION NAME= nn NOT ACCESSIBLE,DFS2374W OTMA GROUP NAME HAS CHANGED FROM oldname TO newnameDFS2375W IMS HAS CHANGED ITS OTMA MEMBER NAME FROM oldname TO newnameDFS2376W IMS OTMA MEMBER NAME name IS THE SAME AS A PREVIOUSLY ACTIVE CLIENTDFS2386I OTMA IS CONNECTING TO THE MEMBER xxxxxxxxDFS2391I MESSAGE DEQUEUE FAILED DURING RESYNCH FOR TMEMBER =x TPIPE = xDFS2393I SRVRESYNCH REJECTED BY TMEMBER= xxxxxxxxxxxxxxxxDFS2396I RESET SEQUENCE NUMBER FAILED DURING RESYNCH FOR TMEMBER = TPIPE =
  10. 10. IMS Version 13IMS 13 OTMA Enhancements ...Concerted effort to reduce MIPS in IMS 13 includes OTMA– More efficient hashing technique for control blocks• IMPACT to an environment depends on volume of activity• Example:– Every CM1 (Send-then-commit) transaction request has a control blockassociated with the port TPIPE during processing10associated with the port TPIPE during processing• If a slowdown in IMS or zOS occurs or if the system is activelyprocessing large numbers of requests then an increasing number ofthese blocks remain active• The improved hashing technique results in a more timely and efficientsearch for a specific block during application GU or checkpoint– Usage of the CPOOL and DFSBCB in XCF Message Exit instead ofthe STORAGE OBTAIN macro– Removal of unnecessary MVCL hot spot
  11. 11. IMS Version 13IMS 13 OTMA Enhancements ...Enhancement to ICAL synchronous callout request– Addresses partial response message due to inadequate applicationspecification• Provides the ability to complete the retrieval of a reply message– Without having to re-issue a complete ICAL “SENDRECV” and associatednetwork transmission costs11network transmission costs– New “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’, AIBRS X’00C’)• IMS 13 keeps a copy of the entire response message in the control regionprivate storage– Until a subsequent ICAL “SENDRECV”, syncpoint, or applicationtermination
  12. 12. IMS Version 13IMS 13 ISC Over TCP/IPISC Over TCP/IP value proposition– New option that supports TCP/IP network connectivity for IntersystemCommunication (ISC) connections• IMS – CICS– CICS 5.1 is requires12– Provides a strategic protocol alternative to SNA/VTAM• Allows an all inclusive TCP/IP solution for networks– Supports a communication capability with CICS that is in-line with evolvingtechnologies
  13. 13. IMS Version 13IMS 13 ISC Over TCP/IP...Highlights– Supports both static and dynamic terminals• Static terminal definitions– SYSGEN stage 1 TYPE, TERMINAL, SUBPOOL macros– DFSDCxxx PROCLIB member• Dynamic terminal specification13• Dynamic terminal specification– Logon descriptors in the DFSDSCMx or DFSDSCTy PROCLIB member– Leverages IMS Connect• Enhancements to the HWSCFGxx configuration member– No IMS Connect user message exit changes– Uses CSL to communicate between IMS and IMS Connect• Requires Structured Call Interface (SCI) andOperation Manager (OM)
  14. 14. IMS Version 13IMS 13 ISC Over TCP/IP...Functionality– CICS IPIC (IP Interconnectivity) provides START / RETRIEVE(asynchronous processing) support• When CICS is a front-end system:– IMS response mode transactions are not supported14– IMS response mode transactions are not supported– IMS conversational transactions are not supported– CICS application program cannot use SEND/RECEIVE• When IMS is a front-end system:– Transaction support is the same for both ISC VTAM and ISC TCP/IP– Transaction flow is always asynchronous• No change to existing programs on either side of theconnection
  15. 15. IMS Version 13IMS 13 ISC Over TCP/IP...IMS terminal definitions– Static terminals:• TYPE, TERMINAL, VTAMPOOL and SUBPOOL macros in Stage 1 gen– Continue to be required for static ISC terminals (VTAM or TCP/IP)• New keyword: ISCTCPIP in DFSDCxxx– Specifies that an ISC terminal is to use the TCP/IP support15– Specifies that an ISC terminal is to use the TCP/IP support– Addition, modification, deletion of the ISCTCPIP parameter requires a cold start• If ISCTCPIP is changed and IMS crashes, ERE ignores the change– Dynamic terminals (ETO):• New Logon descriptor information– UNITYPE=ISCTCPIP, LCLICON=name of local IMS Connect• User descriptors are optional– Default user descriptor of DFSUSER will be used
  16. 16. IMS Version 13IMS 13 ISC Over TCP/IP...The Common Service Layer (CSL) provides the Structured CallInterface (SCI) for communications– Each IMS and its local ISC-routing IMS Connect system must be part of the sameIMSplex– IMS Connect’s HWSCFGxx configuration member• New CICSPORT parameter in TCPIP statement• New ISC statement• New RMTCICS statement16• New RMTCICS statement• The Operations Manager (OM) provides type-2 cmd supportIMSIMS ConnectHWSCFGxxISC()IMSPLEX=(MEMBER=lcliconname,TMEMBER=IMSplexname)...DFSDFxxxIMSPLEX =IMSplexname...SCIStatic:ISCTCPIP=(node,lcliconname)Dynamic/ETOLogon descriptor:L descname UNITYPE=ISCTCPIPLCLICON=lcliconnameORTCPIP... CICSPORT()RMTCICS()
  17. 17. IMS Version 13IMS 13 ISC Over TCP/IP...IMS1 CICS1Parallel session 1w/ Security context 1TERMINALNAME=CICSA1SUBPOOLNAME=SSN1APPLID=APPL8TCPIPSERVICE(TS1)PORT(8891)PROTOCOL(IPIC)ICON1TCPIP…CICSPORT(9991)RMTCICS(CICS1)HOST(hostb.com)PORT(8891)USERID(userid)APPL(applname) IPCONN(SSN1)APPLID(SSN1)HOST(hosta.com)hostb.comhosta.comAPPLID=CICSA1ISCTCPIP(CICSA1,ICON1)VTAMPOOLTYPE UNITYPE=LUTYPE6TCP/IPSCI1717NAME=SSN1SUBPOOLNAME=SSN2Parallel session 2w/ Security context 2ISC(ISC1)NODE(CICSA1)RMTCICS(CICS1)CICSPORT(9991)CICSAPPL(CICSA1)LCLIMS=IMS1HOST(hosta.com)PORT(9991)TCPIPSERVICE(TS1)AUTOCONN (Y)IPCONN(SSN2)APPLID(SSN2)HOST(hosta.com)PORT(9991)TCPIPSERVICE(TS1)AUTOCONN (Y)Initiate session from IMS : /OPN NODE CICSA1 USER SSN1ORInitiate session from CICS: F CICSA1, CEMT S IP (SSN1) ACQIMS Connect
  18. 18. IMS Version 13IMS 13 Synchronous Program SwitchNew capability that enhances the DL/I ICAL support– Allows an IMS application program to synchronously call and wait for a replyfrom another IMS application program• Within the calling program’s UOWIMS dependentWebSphere18DatabaseIMS DBservicesIMS dependentregionIMS TMservicesMPP, JMPIFP, MD BMPOTMAApplicationProgramICALIMS SOAP GATEWAYIMSConnectTCP/IPuser-written ClientWebSphereIMS TM resource adapter
  19. 19. IMS Version 13IMS 13 Synchronous Program Switch...Value Proposition– Modernization of the IMS application infrastructure• Provides an internal service flow of IMS transactions to complete abusiness process– In the same IMS or a different IMS19– Implementation of a Process Server or Broker inside IMS• Reduces unnecessary network traffic when accessing multipleapplications in the same IMS or IMSplexWASApplicationWASIMSConnectIMSMPPxMPP4MPP2MPP3ICALICALICALICALWASApplicationWASIMSConnectIMSMPP4MPP2MPP3MPP1MPP1
  20. 20. IMS Version 13IMS 13 Synchronous Program Switch...Highlights– An enhancement to the DL/I ICAL to invoke another IMS application• In the same IMS• In a different IMS– In a Shared Queues back-end– Across an MSC linkMPP1MPP4MPP3ICALICALICALIMS1MPP2IMS XIMS2MSCSharedMsg Queues20– Across an MSC link– And synchronously receive the response back during the same UOW– Where IMS internally schedules the transaction initiated by the ICAL call as anOTMA transaction• Uses a new type of OTMA destination descriptor (TYPE=IMSTRAN) which has beenintroduced specifically for synchronous program switch support– And the target transaction can be• An IFP, MPP, MD BMP, or JMP in IMS TM or TM/DB environmentsMPP4
  21. 21. IMS Version 13IMS 13 Synchronous Program Switch...Uses OTMA Destination Routing Descriptors– Which externalize the routing definitions and specifications for calloutmessages and synchronous program switch messages• Allowing up to 510 destination routing descriptor entries defined inDFSYDTx member of IMS.PROCLIB– With new TYPE= IMSTRAN for synchronous program switches21– With new TYPE= IMSTRAN for synchronous program switchesD entry_name keywords Where entry_name is descriptor entry name and canbe masked by ending in an *keywords are: TYPE=IMSTRANLTERMOVR=nameTMEMBER=nameTPIPE-nameSMEM=NO|YESEXIT= NO|YESREPLYCHK=YES|NOSYNCTP=NO|YESSYNTIMER=timeout valueFor example: D OTMDEST1 TYPE=IMSTRAN SYNTIMER=500D OTMDEST2 TYPE=IMSTRAN TMEMBER=SCOTTHWS1 TPIPE=BRYCE EXIT=YES
  22. 22. IMS Version 13IMS 13 Synchronous Program Switch...Usage examples– Applications can issue multiple ICALs to different destination TYPEs• Synchronous callout• Synchronous program switchTRANAIMS CTL RegionIMSWebSphereIMS TMRAOTMA1 GU, IOPCB22ICAL DEST1ICAL TRANBIMSConnectIMS SOAPGatewayTCP/IPRYO pgmMSG-QDestinationDescriptorTYPE(IMSCON)TRANBGU IOPCBISRT IOPCBDestinationDescriptorTYPE(IMSTRAN)1234567GU, IOPCB
  23. 23. IMS Version 13IMS 13 Synchronous Program Switch...Usage examples...– The IMS application environment supports recursive requests• ICAL to ICAL– Across a single or multiple IMS systemsFE IMS BE IMS or Local IMSTRANA APOL12GU, IOPCB23LTERMLU62OTMABMPSQICAL requestSQ,MSC,Local(FE=BE)ICAL to SKS2ISRT IOPCBSKS2GU, IOPCBICAL to SKS1ISRT IOPCBSKS1ISRT IOPCBGU, IOPCBISRT, IOPCBGU, IOPCBGU, IOPCB1 3456782
  24. 24. IMS Version 13IMS 13 Synchronous Program Switch...Implications– New design considerations• Timeout values• Transaction Expiration24• Late Responses• LTERM Override• ALTPCB destinations• Multiple ICALs• Recursive requests• Holding database locks across an ICAL request– Increased importance for performance tooling
  25. 25. IMS Version 13IMS 13 Integration EnhancementsIMS Enterprise Suite 2.2 SOAP Gateway UpdatesIMS Enterprise Suite 2.2 Connect API for Java UpdatesIMS Enterprise Suite 2.2 Explorer for DevelopmentIMS Explorer for Administration25
  26. 26. IMS Version 13IMS .NET Data Provider REQUIREMENT.NET Applications access IMS TM transaction processingprograms– SOAP protocols• IMS SOAP Gateway• IMS TM ResourceRequirement26Requirement– Customers need access to IMS databases from .NET applicationsSolution– IMS .NET Data Provider• Enables standard ADO.NET SQL access to IMS DB– Connect to IMS– Execute SQL to IMS– Return results from IMS
  27. 27. IMS Version 13IMS .NET Data Provider ArchitectureDRDAIMS 13Application ServerODBMDDMIMS ConnectTCPIPIMS 13SQLcallsSCIOMIMSNativeSQLIMSCommandIMSDataReaderADO.NETApplicationsResult set dataIMSDataAdapterDataSet27DATASTORE(NAME=IMSA)ALIAS(NAME=IMS)z/OSTCP/IPTCPIPDRDAPORT8888SCIDRDADRACCTLODBAIMSDBIMSCatalogPSB1SQLProcessorSQL + ParametersIMSConnectionDRDA ClientConnection Pool drdaserver.ims.com
  28. 28. IMS Version 13IMSConnectIMSIMS SOAPGatewayAdapterTaskManagerZ/OS32 0IVTNO DISPLAY LAST1<?xml version="1.0"?><soap:Envelope><soap:Body><INPUTMSG><in_ll>32</in_ll><in_zz>0</in_zz><in_trcd>IVTNO</in_trcd><in_cmd>DISPLAY</in_cmd><in_name1>LAST1</in_name1></INPUTMSG></soap:Body></soap:Envelope><INPUTMSG><in_ll>32</in_ll><in_zz>0</in_zz><in_trcd>IVTNO</in_trcd><in_cmd>DISPLAY</in_cmd><in_name1>LAST1</in_name1></INPUTMSG>IMSIMS ES 2.2 SOAP GatewayScenario – .NET Client Invokes an IMS COBOL Application as aWeb Service28.NET ClientXML COBOLAdapterIMSAppXMLHTTP/SOAPXML COBOLConvertersIMS WebService<?xml version="1.0"?><soap:Envelope><soap:Body><cbl:OUTPUTMSG><out_ll>93</out_ll><out_zz>0</out_zz><out_msg>ENTRY WAS DISPLAYED</out_msg><out_cmd>DISPLAY</out_cmd><out_name1>LAST1</out_name1><out_name2>FIRST1</out_name2><out_extn>8-111-1111</out_extn><out_zip>D01/R01</out_zip><out_segno>0001</out_segno></cbl:OUTPUTMSG></soap:Body></soap:Envelope><cbl:OUTPUTMSG><out_ll>93</out_ll><out_zz>0</out_zz><out_msg>ENTRY WASDISPLAYED</out_msg><out_cmd>DISPLAY</out_cmd><out_name1>LAST1</out_name1><out_name2>FIRST1</out_name2><out_extn>8-111-1111</out_extn><out_zip>D01/R01</out_zip><out_segno>0001</out_segno></cbl:OUTPUTMSG>93 0ENTRY WAS DISPLAYEDDISPLAYLAST1 FIRST18-111-11111D01/R01 0001
  29. 29. IMS Version 13Advanced Installation and MaintenanceServer is divided into three components• Imsserver – can be mounted as READ only– Contains the servers executable code• Imsbase – can be mounted as READ and WRITE– Contains the servers configurations and log• Imssoap - can be mounted as READ and WRITE– Contains the user-deployed web service-related files– WSDLs , correlators, connection bundlesBenefits29Benefits– easier to apply maintenance– allocate additional disk space when more web services are addedIBM® Installation Manager for z/OS® V1.5.3– Supports centralized repository delivered through the SMP/E process– simplifies maintenance processMultiple SOAP Gateway server instances– share a single instance of the Java™ Virtual Machine (JVM).– reduces the amount of storage required for each additional server instance
  30. 30. IMS Version 13WS-SecurityWS-Security SAML unsigned tokens for synchronous calloutapplications– Originating Userid (PSTUSID) for the IMS synchronous callout applicationis passed to the external web service for further authentication andauthorizationBenefit– Provides message-level security for synchronous callout30– Provides message-level security for synchronous calloutWS-Security enhancement for provider web services– support for Security Assertion Markup Language (SAML) 2.0 sender-vouches signed tokensBenefit– Provides additional message integrity for service provider processing– Extends SOAP Gateway support of WS-Security standards
  31. 31. IMS Version 13End-to-end Transaction Tracking – Provider Scenario(correlation based on Tracking ID)IMS ES 2.2SOAPGatewayIMSConnectOTMAIMS 13IMS AppHorizontalTracking ID +(XML) request datamessageexits*HorizontalTracking ID+ message dataTracking IDHorizontalTracking ID +Request withoptional tracking IDRoute /generateSoap Client31eventexit *Tracking ID(XML) responsedata + CSM HorizontalTracking ID +message dataIMSLog recordSOAPGatewayTransaction logTransaction Tracking APIMonitoringdata*responseHorizontal and VerticalTracking IDsgenerateTracking IDITCAMIMS ConnectExtensionsIMSConnectExtensionsjournalProblemInvestigatorPerformanceAnalyzerIMSPerformance AnalyzerIMSProblem Investigatorrecords events withTracking IDTracking IDSoap ClientHorizontal and VerticalTracking IDs
  32. 32. IMS Version 13IMS ES 2.2 Connect API for JavaIMS and IMS Connect type-2 commandsPerformance EnhancementsSupport for SendOnly synchronous callout response messages withacknowledgement– Function requires that both the following APAR/PTFs are applied32– Function requires that both the following APAR/PTFs are applied• IMS Connect 12: PM39569/UK74666• IMS OTMA 12: PM39562/UK74653Benefits– Custom written IMS Connect TCP/IP Java client applications• Can send and receive commands to IMS and IMS Connect• Can request and receive an indication of response delivery to IMS forsynchronous callout processing
  33. 33. IMS Version 13IMS Service ConsumerSendOnly synchronous callout response messages with acknowledgement– client application gets acknowledgement when the response message is received by IMSINTERACTION_TYPE_DESC_SENDONLYACK_CALLOUT_RESPONSEIMS ES 2.2 Connect API for Java33IMSIMS Appz/OSInitiating ClientJavaBeanWebServiceJMSICALIMSConnectRYOIMS Service ConsumerIMS ESConnect APIFor JavaOTMADescriptorDL/I ICAL or JMS -> SynchronousOTMAResumeTPIPERequest MsgSend OnlyResponse MsgSend OnlyResponse ACK
  34. 34. IMS Version 13Performance dataFor inbound, 16,000 transactions per second using V2R2 which is a 3%improvement over V2R1For callout, 11,000 transactions per second using V2R2 which is a 56%improvement over V2R134
  35. 35. IMS Version 13See database relationshipschange DBD fieldattributesIMS Enterprise Suite V2.2 Explorer for Development35Generate SQL toaccess IMS dataEdit PSB sensitivesegments andattributesAbility to access the IMS Catalog
  36. 36. IMS Version 13IMS ES 2.2 – Importing Data StructuresImporting data structures– metadata field layouts imported from data structure files (COBOL copybooks or PL/Iincludes)ProcedureDBD file– select Import COBOL or PL/I Data Structures.36– select Import COBOL or PL/I Data Structures.– select the data structure file that contains the COBOL copybooks or PL/I includes thatyou want to import.– Optional:• using source from the IMS catalog, specify the map and case name to import thedata structureBenefit– RDz is not required– no need to shell share with RDz
  37. 37. IMS Version 13Data Source Explorer ViewIndication of the PROCOPTS in effect for each PCBIndication added to Tables (Segments) denote the segment hierarchy for the databaseA new IMS Explorer submenu– Launch DBD Editor– Launch DBPCB EditorA new action to launch the graphical PCB editor for a given Schema (PCB)37A new action to launch the graphical PCB editor for a given Schema (PCB)SQL Results View– all SQL Exceptions thrown by the IMS Universal Drivers will be surfaced to the user.– character string representing the fields hexadecimal value will be displayed for fields of data typeBINARYBenefits– Ease of use for working with IMS resource defintions
  38. 38. IMS Version 13IBM Data Studio V3.2 support for IMSIBM® Data Studio support for pureQuery with IMS– Can generate pureQuery code for IMS databases• All generated SQL supported by IMSNew SQL Query Builder for IMS– Prevents graphically building queries that are not supported by IMSData Development projects38Data Development projects– Database Web Services generation enabled for IMS JDBC Connection– WebSphere DataPower added as one of the supported server types• Enhanced support with Firmware V6.0 supports DRDA to IMS 12 DB
  39. 39. IMS Version 13DLIModelIMS Enterprise suite for z/OS , V2.1 is the last release to provide theDLIModel Utility plug-in.Explorer provides ability to import DLIModel projects– Explorer does not support XML DB or DB Web ServicesCustomers using IMS Database Web Services should transition to39Customers using IMS Database Web Services should transition tousing the IBM® Data Studio which leverages the IMS UniversalDrivers
  40. 40. IMS Version 13IMS Explorer for AdministrationWeb Browser– Graphically administer IMS Databases and transactions– View IMSPlex• visualize relationships between various IMS resources– transactions, programs and databases in one view– Replacement for IMS Control Center4040– Replacement for IMS Control CenterSoftware requirements– IMS Tools Admin Console (no-charge)– IMS Version 12– IMS Connect– Common Service Layer OM and SCI– Supported web browser– Firefox, Internet Explorer, Safari
  41. 41. IMS Version 13Explorer for Administration – IMSPlex Resources4141
  42. 42. IMS Version 13Explorer for Administration – Manage Transactions4242
  43. 43. IMS Version 13Explorer for Administration – Programs View4343
  44. 44. IMS Version 13Explorer for Administration – Databases View4444

×