IMS V13 Overview_ATSkrb - IMS UG April 2013 San Ramon

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

No notes for slide

IMS V13 Overview_ATSkrb - IMS UG April 2013 San Ramon

  1. 1. ®IMS Version 13IMS 13 Overview© 2011 IBM CorporationIBM Advanced Technical Skills
  2. 2. IMS Version 13IMS 13 System EnhancementsIMS Connect EnhancementsConcurrent Application ThreadsReduced Total Cost of Ownership (TCO)IMS Command EnhancementsIMS CQS Enhancement2IMS CQS EnhancementIMS DRD EnhancementIMS User Exit EnhancementsIMS Security Enhancements/DIAG Command Enhancements
  3. 3. IMS Version 13XML Converter EnhancementsSupport for extending the current limit of 100 up to 2000 for themaximum number of XML converters• New IMS Connect configuration parameter MAXCVRTADAPTER(…, MAXCVRT= value)• IMS 12 (PM64487 / UK79728)Capability to view converters that are currently loaded– New Type-2 Command: QUERY IMSCON TYPE(CONVERTER)3– New Type-2 Command: QUERY IMSCON TYPE(CONVERTER)• Requests detailed information about XML converters in IMS ConnectBenefits– Enhances the flexibility of converter usage• Directly impacts IMS Soap Gateway environments
  4. 4. IMS Version 13Auto-restart of the Language Environment (LE)Automated mechanism to reinitialize the Language Environmentwhen an XML converter ABENDs– Without restarting IMS Connect– Converters will be reloaded as they are neededAutomatic refresh of the BPE User Exit for the XML Adapters(HWSXMLA0) after the ABEND limit ABLIM has been reached4(HWSXMLA0) after the ABEND limit ABLIM has been reachedBenefit– Improved efficiencies during error conditions• Eliminates IMS Connect restart and user interactions
  5. 5. IMS Version 13Expanded Recorder Trace RecordsThe Recorder trace records have been expanded to:– Capture entire messages sent and received using:• All TCP/IP communications– Including DRDA sockets and ISC TCP/IP• SCI (OM, ODBM, MSC, and ISC communications)• Requires a Trace Level HIGH and use of the external trace data set5• Requires a Trace Level HIGH and use of the external trace data setUPDATE TRACETABLE NAME(RCTR) OWNER(HWS) LEVEL(HIGH) EXTERNAL(YES | NO)Benefits– Improved diagnostics and problem determination
  6. 6. IMS Version 13RACF Event Notification Facility (ENF) SupportBackground– IMS Connect V12 provided the option to cache RACF UserIDs (UIDs) alongwith a command to refresh themIMS Connect V13: RACF ENF Support for Cached UserIDs (UID)– Automatically refreshes cached UIDs by listening to RACF events (ENFsignals) indicating that a change has been made to a UID6signals) indicating that a change has been made to a UID– NOTE: This function applies only when RACF UID caching has beenenabled in IMS ConnectBenefit– Allows IMS Connect to listen for certain RACF events indicating that achange has been made to a specific UserID• Avoids manual intervention
  7. 7. IMS Version 13Reporting of Overall Health to WLMWLM (Workload Manager) Health Report– New function to automatically report the overall health of IMS Connect• Allows Sysplex Distributor to use and take into account thisinformation for workload balancingBenefit– Allows WLM to know when resources are constrained or available7– Allows WLM to know when resources are constrained or available– Minimizes the possibility of Sysplex Distributor assigning work that IMSConnect is unable to handle
  8. 8. IMS Version 13Configurable TCP/IP backlog (Queue) sizeNew parameter TCPIPQ– Allows users to configure the length of the queue in TCP/IP forconnection requests that have not yet been assigned a socket.• Connection requests are held on this queue until IMS Connect canassign a socket– Overrides the default which is equal to the maxsoc value8• Actual value used is the smaller of IMS Connect’s TCPIPQ valueand SOMAXCONN in TCP/IPBenefit– Provides a configurable option to increase the backlog queue size inTCP/IP
  9. 9. IMS Version 13Concurrent Application Threads EnhancementPartition Specification Table (PST) used for– Active dependent regions (MSG/BMP/IFP/JMP/JBP)– CICS/DBCTL threads– Open Database Access threadsCustomers continue to require more PSTs!– 31 dependent regions - 1980 (IMS 1.1.6)9– 31 dependent regions - 1980 (IMS 1.1.6)– 999 dependent regions - 1995 (IMS 5.1)– 4095 dependent regions - 2013 (IMS 13)Related parameters– MAXPST=– PST=– MAXTHRDS= for ODBM– MAXTHRDS=, MINTHRDS= for DBCTL
  10. 10. IMS Version 13Reduced Total Cost of OwnershipCross-platform focus on reducing mainframe software costsMajor focus on reducing CPU usageChanges throughout IMS to improve performance, reduce storageusage and reduce CPU used to run IMS– Using more efficient storage services– Improved algorithms– Reducing pathlength10– Reducing pathlength– Optimizing frequently used processes– Latch / lock improvements– Storage reductions– Use of zEnterprise hardware functionsBenefits– Improved performance, lower cost per transaction, reduced cost ofownership.
  11. 11. IMS Version 13ESAF support in Java Dependent Regions (JDR)With IMS 13, there are two methods for accessing DB2 from JDRs– Access via the previously existing DB2 RRSAF interface– Access via the standard ESAF interfaceWith IMS 13, the ESAF interface can be used in JMP/JBP regions toaccess any ESAF defined to the IMS control region– WebSphere MQ, DB2, WOLA (WebSphere Optimized Local Adapter)11Support for the SSM= parameter on the JMP/JBP dependent regionstartup JCLOnly one ESS connection method allowed per JMP/JBP– Default ESS connection method is DB2 RRSAF• No impact to existing usersBenefits– Simpler, more efficient, and more consistent interface
  12. 12. IMS Version 13IMS Command EnhancementsEnhancements are focused on type-2 commands for the OperationsManager (OM) environmentBenefits– Support of new IMS 13 functions12– Improved manageability
  13. 13. IMS Version 13IMS CQS EnhancementWhen IMS Common Queue Server (CQS) rejects a z/OS STOPcqsjobname command because CQS clients are still connected(CQS0300I), CQS issues a new message, CQS0301I, for eachconnected client– Enables the operator to shut down or quiesce the connected CQS clientsso that the CQS address space can be stopped13Benefits– Improved manageability for CQS
  14. 14. IMS Version 13IMS 13 User Exit EnhancementsEnhanced user exit services extended to additional IMS controlregion user exitsUsers can now dynamically refresh more IMS user exit routines tobring in an updated version of the exit (or add/delete)– Significantly reduces downtime since IMS control region no longerrequires restart14Users can now display information about more user exits that aredefined in the USER_EXITS section of DFSDFxxx– Provides useful exit information to the userUsers can now code an exit to leverage IMS’s ability to call multipleroutines of the same type from a single point within the exit
  15. 15. IMS Version 13IMS Security EnhancementsAll IMS security settings can now be defined as IMS startupparameters– Updates to SECURITY macro in system definition (SYSGEN) no longerrequired due to its removal– Previously, certain settings could only be defined in SECURITY macro15Move security user exits out of the IMS nucleus into 31-bit storage– DFSCSGN0 Signon/off Security– DFSCTRN0 Transaction Authorization– DFSCTSE0 Security Reverification
  16. 16. IMS Version 13/DIAGNOSE Command EnhancementsBenefits– Cost effective, non-disruptive alternative to console dumps– /DIAGNOSE command is now more interactive• Can be used more as a tool for easing the real-time diagnosis process– Decreased time and effort required in capturing diagnostic information– Improved turn-around time in problem resolution16– Improved turn-around time in problem resolution
  17. 17. IMS Version 13IMS 13 Transaction Manager and ConnectivityEnhancementsCallout function enhancementsISC Over TCP/IPOTMA enhancementsNon-Discardable Message Exit (DFSNDMX0) enhancements17
  18. 18. IMS Version 13Callout function enhancementsSynchronous program switchEnhancements to RECEIVE function for handling truncated messagesOTMA destination descriptors support asynchronous messages that aregoing to IBM WebSphere® MQ.18
  19. 19. IMS Version 13Synchronous Program SwitchNew capability that enhances the DL/I ICAL supportBenefits– 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 IMS• Reduces unnecessary network traffic when accessing multiple applications19• Reduces unnecessary network traffic when accessing multiple applicationsin the same IMS or IMSplexWASApplicationWASIMSConnectIMSMPPxJMP4JMP2MPP3ICALICALICALICALWASApplicationWASIMSConnectIMSJMP4JMP2MPP3MPP1MPP1Before ICAL supportprocessing FlowICAL support processingFlow
  20. 20. IMS Version 13Support for Truncated MessagesNew subfunction capability that enhances the DL/I ICAL supportNew “RECEIVE” subfunction code can be used to get truncatedmessage– IMS 13 keeps a copy of the entire response message in the control regionprivate storageBenefit20Benefit– Provides the ability to complete the retrieval of a reply message• Without having to re-issue a complete ICAL “SENDRECV” and associatednetwork transmission costs
  21. 21. IMS Version 13ISC Over TCP/IPISC Over TCP/IP value proposition– New option that supports TCP/IP network connectivity for IntersystemCommunication (ISC) connections• IMS – CICSProvides a strategic protocol alternative to SNA/VTAM• Allows an all inclusive TCP/IP solution for networks21• Allows an all inclusive TCP/IP solution for networks
  22. 22. IMS Version 13OTMA EnhancementsOTMA early termination notification– Enhancement that allows OTMA to leave the XCF group earlier intermination processing• Allows OTMA clients (IMS Connect, WebSphere MQ, OTMA C/I) to benotified of the termination via their XCF Group Exit– Can route requests to other systems22– Addresses issues associated with transactions messages being accepted butnot processed– Function being added to IMS 12: APAR PM73869
  23. 23. IMS Version 13OTMA Enhancements …OTMA destination descriptor enhancements– TYPE={MQSERIES}• Provides asynchronous callout and messaging support (ISRT ALTPCB)– EXIT={YES | NO}• Specifies whether or not the OTMA exits are to be calledCorresponding enhancement to IMS Type-2 OTMADESC commands23Corresponding enhancement to IMS Type-2 OTMADESC commands– [CREATE | UPDATE | DELETE |QUERY] OTMADESC• Recovered across warm and emergency restartsBenefits– Simplifies asynchronous messaging to WMQ– Removes the need to code the OTMA exits, DFSYPRX0 and DFSYDRU0– Provides dynamic change capability with the Type-2 commands
  24. 24. IMS Version 13Enhancements for the Non-Discardable Messages ExitRoutineCustomer requirement for a new function to PSTOP an abendingtransaction– Stops scheduling but allows queueing to continueNew functions provided by for the DFSNDMX0, the Non-DiscardableMessages exit routine24Messages exit routine– IMS 11 APAR PM67950 / PTF UK81040– IMS 12 APAR PM45943 / PTF UK71989– Included in IMS 13
  25. 25. IMS Version 13IMS 13 Database and DBRC EnhancementsDatabase VersioningHALDB AlterDEDB AlterDBRC Enhancements25
  26. 26. IMS Version 13Database Versioning OverviewDatabase Versioning provides the ability to assign user-definedversion identifiers to different versions of a database structure– Enables structural changes to a database while providing multiple views ofthe physical IMS data to application programsApplications referencing a new physical database structure can bebrought online without affecting applications that use previousdatabase structures26database structures– Applications which do not require sensitivity to the new physical structure,do not need to be modified and can continue to access the databaseBenefit– Minimizes impact and reduces cost associated with making andcoordinating coding changes to affected application programs when aphysical database structure changes
  27. 27. IMS Version 13HALDB Alter OverviewStructural changes can be made to HALDB databases while thedatabase remains online– Add a new field to space at the end of an existing segment– Increase the length of an existing segment– Define new fields that remap existing fields and space in an existingsegment27Benefit– Make structural changes to a database while maintaining databaseavailability
  28. 28. IMS Version 13FIELD 1FIELD 2 SpaceFIELD 2 SpaceNewFIELD 3Add a new field to space at the end of a segmentExample 1FIELD 128FIELD 1FIELD 3Example 2FIELD 1 FIELD 2FIELD 2 SpaceNewFIELD 3Space
  29. 29. IMS Version 13FIELD 1FIELD 2New SpaceFIELD 2Increase the length of an existing segmentExample 1FIELD 129FIELD 1Example 2FIELD 1 FIELD 2FIELD 2New SpaceSpaceSpace
  30. 30. IMS Version 13DEDB AlterIMS 13 adds ability to dynamically change DEDB specifications– Users can dynamically change UOW, SIZE, ROOT, Randomizer while DEDB isonline– New DEDB Alter utility is used for DEDB changes– DRD is not required for DEDB Alter– Supports VSO Areas if /VUNLOAD is done before DEDB Alter is executed30– Supports VSO Areas if /VUNLOAD is done before DEDB Alter is executedBenefits– Improved management of DEDB definitions• Eliminate system down time for modifications to DEDB definitions• Improve data availability since changes are done while DEDB is online
  31. 31. IMS Version 13DBRC EnhancementsCommand support for HALDB AlterCommand support for DEDB AlterMINVERS value of ’13.1’ must be set to use HALDB Alter, DEDB Alter,or synchronous program switch in a shared queues environmentSupported Migration and Coexistence– IMS 11 to IMS 1331– IMS 11 to IMS 13• Apply DBRC coexistence SPE APAR PM53134 to IMS 11– PTF UK80026• Allow IMS 11 to understand IMS 13 RECON records– IMS 12 to IMS 13• Apply DBRC coexistence SPE APAR PM53139 to IMS 12– PTF UK80027• Allow IMS 12 to understand IMS 13 RECON records
  32. 32. IMS Version 13IMS SOA Integration EnhancementsIMS Enterprise Suite V2.2– SOAP Gateway– Explorer for Development32
  33. 33. 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 +(XML) responsedata + CSMHorizontalTracking ID +Transaction Tracking APIRequest withoptional tracking IDresponseRoute /generateTracking IDSoapClient33eventexit *message dataIMSLog recordSOAPGatewayTransaction logTransaction Tracking APIMonitoringdata*Horizontal and VerticalTracking IDsITCAMIMS ConnectExtensionsIMSConnectExtensionsjournalProblemInvestigatorPerformanceAnalyzerIMSPerformance AnalyzerIMSProblem Investigatorrecords events withTracking IDTracking IDHorizontal and VerticalTracking IDs
  34. 34. IMS Version 13IMSSOAPGatewayIMS SOAP Gateway WS-Security SAML unsignedtokens for synchronous callout applicationsz/OSIMSTM/CTLServicesIMSConnectHWS1WebServiceApplicationProgramICALDEST1ResumeTPIPETPSTPSDEST1TPSHWS1HWSXMLA0CORTKNUSERAXMLUSERAInitiating ClientUSERACORTKNUSERAJava34HWS1 DEST1OTMAHWSXMLA0XMLCNV1DACKSend_ONLYHWSXMLA0XML ConverterXMLCNV1DCORTKNUSERAXMLUSERARequestdataResponsedataXMLUSERAXMLUSERAConnectionBundleTPSUSERACORTKNUSERACustomAuthentication
  35. 35. IMS Version 13IMS ES 2.2 ExplorerImporting data structuresImporting data structures– metadata field layouts imported from data structure files (COBOL copybooksor PL/I includes)ProcedureDBD file– select Import COBOL or PL/I Data Structures.35– select Import COBOL or PL/I Data Structures.– select the data structure file that contains the COBOL copybooks or PL/Iincludes that you want to import.– Optional:• using source from the IMS catalog, specify the map and case name toimport the data structureBenefit– RDz is not required– no need to shell share with RDz
  36. 36. IMS Version 13IMS Explorer V2.2 Joint Project with IBM Data Studio V3.2IBM® Data Studio support for pureQuery with IMS– Can generate pureQuery code for IMS databases• All generated SQL supported by IMS36Annotated pureQuery interface
  37. 37. IMS Version 13SQL Parsing in IMSIMS intends to invest in SQL Call HandlerExample with IMS SQL call handler– How much money has my insurance company paid out in claims for the year2011?– SELECT SUM(CLAIMAMOUNT) FROM CLAIMS WHERE YEAR=2011z/OSClient ApplicationSQL Call37IMS DBIMSJDBCDriverClaims$2432$41…$6255+ ________$797439097Claims$2432$41…$6255IMS SQLCall Handler$797439097Total Claims$797439097
  38. 38. IMS Version 13SQL Parsing in IMSIMS intends to invest in SQL Call HandlerOpen Database End to End flow with native SQLz/OSIMSJDBCDriver ODBMIMSConnectDRDADRDA38RYO IMS DBIMSCatalogIMSJDBCDriverIMS JavaenabledDep RegionType 4Type 2IMS DBIMSCatalogSQLSQLIMSSQLCallHandler DLI
  39. 39. IMS Version 13IMS SQL Support for COBOLRequirement– Customers need access to IMS databases using SQL from IMS managedCOBOL application programsSolution– IMS intends to invest in COBOL SQL Calls– Convert SQL statements to DL/I database calls• Handle SQL errors39• Handle SQL errorsBenefits– Reduce application development cost by leveraging existing SQL skills– Expands IMS database access for application and database developers.
  40. 40. IMS Version 13.NET Data Provider RequirementDRDAIMSApplication ServerODBMDDMIMS Connect SQLcallsSCIOMIMSSQLCall HandlerCommandSQL + ParametersDataReaderADO.NETApplicationsResult set dataDataAdapterDataSet40ODBMDATASTORE(NAME=IMSA)ALIAS(NAME=IMS)z/OSTCP/IPDDMTCPIPDRDAPORT8888SCIDRDAcallsDRACCTLODBAIMSDBIMSCatalogPSB1Call HandlerConnectionDRDA ClientConnection Pooldrdaserver.ims.com
  41. 41. IMS Version 13Requirement: DataPower to IMS DBDataPowerIMSJDBCRouting/dataSQL DRDAsends /ODBMIMSConnectDRDABack41JDBCDriverdatatransformationsends /receivessends /receivesIMS DBIMSCatalogIMS DBIMSCatalogSQLIMSSQLCallHandlerDLIEndservices
  42. 42. IMS Version 13SSA Enhancement - Get by OffsetSolution– IMS 12 APAR PM65139 / PTF UK81837 & UK81838• New SSA command code “O”• Enhanced database SSA processing with ability to search for datain a segment by specifying a field position and length instead of afield name• Contains core IMS database codeAPAR & PTFsCLOSED4242• Contains core IMS database code– IMS 12 APAR PM69378 / PTF UK81917• Enhanced IMS Universal Drivers to allow SQL predicatescontaining ‘columns’ not defined in the DBD by internallyconverting ‘columns’ to position and length for SSA qualification• Contains IMS universal driver codeAPAR & PTFCLOSED
  43. 43. IMS Version 13IMS 13 HighlightsSystem– IMS CONNECT enhancements• XML Converter Enhancements• Expanded Recorder TraceRecords• Reporting of overall health toWorkload Manager (WLM)Database and DBRC– HALDB Alter– DEDB Alter– Database Versioning– DBRC support for HALDB Alter andDEDB AlterTM and Connectivity43Workload Manager (WLM)– Concurrent application threads– Reduced Total Cost of Ownership(TCO)– Elimination of SECURITY Macro– User Exit enhancements– JDR support for ESAF– DIAG command enhancementsTM and Connectivity– Synchronous program switch– ISC TCP/IP Links– OTMA destination descriptorenhancements– and more!43
  44. 44. IMS Version 13Status of IMS VersionsIMS Version 9– End of service was November 7, 2010IMS Version 10– Generally available on October 26, 2007– End of service was November 5, 2012IMS Version 11– Generally available on October 30, 200944– Generally available on October 30, 2009– End of service has not been announcedIMS Version 12– Generally available on October 28, 2011– End of service has not been announcedIMS Version 13– Announced on October 3, 2012– Currently in QPP program– General availability has not been announced
  45. 45. IMS Version 13Software PrerequisitesMinimum software level prerequisites– z/OS V1R13 (5694-A01)• RACF (included in separately orderable SecureWay Security Server), orequivalent, if security is used• High Level Assembler Toolkit Release 5 (5696-234)• APAR OA39392 / PTF UA66823 is required for z/OS 1.13 for IMS V1345• APAR OA39392 / PTF UA66823 is required for z/OS 1.13 for IMS V13– IRLM 2.3 if the IRLM is used* subject to change
  46. 46. IMS Version 13Software Prerequisites ...Minimum software levels for optional functions– Java Dependent Regions requires JDK 6.0.1– ISC TCP/IP requires CICS 5.1– Depending on the environment, the IMS Universal Drivers require:• IBM JDK 6.0.1 or later• DB2 V9.1 or later46• WAS V7 or later• CICS V4.1 or later– DB Versioning requires implementation of the IMS Catalog* subject to change
  47. 47. IMS Version 13Software Prerequisites ...Minimum software levels for optional functions ...– IMS 13 supports interactions with• DB2: Versions 9, 10• CICS: Versions 3.2, 4.1, 4.2, 5.1– CICS 5.1 (newly announced) is required for ISC TCP/IP support• Requires z/OS 1.1347• Requires z/OS 1.13• MQ for z/OS: Versions V7.0.1, V7.1– Note V6 EOS was September 2012– 7.01 introduced MQ message expiry interfacing with IMS transaction expiration– 7.1 enhanced the expiry support and support for OTMA resource monitoringprotocol messages* subject to change
  48. 48. IMS Version 13Hardware PrerequisitesIMS 13 runs only on 64 bit processors running in z/Architecture mode– Processors must also support the Long-Displacement Facility of thez/Architecture– ESA mode is not supported– For a list of z/Series machines see: www.ibm.com/systems/z/hardware/z900 machines must be at GA2 level (microcode level 3G or later)48z900 machines must be at GA2 level (microcode level 3G or later)
  49. 49. IMS Version 13Hardware Prerequisites ...Sysplex Data Sharing (including Data Caching and VSO Data Sharing)– Coupling Facility (CF) level 9, or laterShared Queues and Shared EMH support– Coupling Facility level 9 or later– System-managed CF Duplexing49• CF level 12, or later and bidirectional CF to CF linksEAV support for non-VSAM data sets– EAVs are supported on DS8000 at microcode level R4.0 via bundle64.0.175.0 (Sept 2008) or higher
  50. 50. IMS Version 13Supported Migrations and CoexistenceIMS 12 to IMS 13– Upgrade RECONs from IMS 12 to IMS 13– Databases are compatible– Application programs are compatible50IMS 11 to IMS 13– Upgrade RECONs from IMS 11 to IMS 13– Databases are compatible– Application programs are compatibleCheck Release Planning documentation at GA for additionalprerequisites/coexistence/migration items

×