ims connect and ims odbm: an early look

IMS Connect and IMS ODBM: an early lookJim MartinFundi Software

5-Aug-2010Session 7858

Template Documentation

AgendaOverview of open databaseSystems-perspective of Open DatabaseTools that can be used with Open DatabaseFutures


Open Database Environment LPAR ALPAR BLPAR Cz/OSDistributedJCA

1.5TCPIPWebSphereIMS DBCTLIMSPCSOAPTCP/IPXCF


Protocol differenceIMS Connect has always used the IRM protocolNow supports DRDA an open standards based protocol for distributed database accessDefines request flowsDefines Object:Data structure (DDM)ExtensibleControlled by the Open Group


Standards-based tools can analyze the communcation exchange


Key pointsDifferentiatorStandards-basedOpen access from distributed platformsTwo-phase commitWith or without WASImpactOpen DB requires CSL + IMS ConnectNew class of workload through IMS and IMS Connect


ChallengesManaging and configuring new address spacesUnderstanding, debugging, and tuning DRDA requestsNew class of IMS application programmers (hopefully!)


IMS Connect ExtensionsImproves the manageability of IMS ConnectIMS Connect Extensions enhancements for Open Database include:Event collectionRoutingMonitoring of ODBM throughput in GUI or ISPF


Use routing to improve parallelism and redundancyMessagesALIAS+PSBNAMEODBM AALIAS ALIASALIASALIASCEX converts a single ALIAS+PSBNAME to multiple candidate ODBM address spaces and databasesIMS ConnectODBM B1000msg/s4x250msg/s*


IMS ConnectOpen database accessODBMIMSJournalsExtensionsIMS LogOverall request characteristicsFraming for ODBM performanceInput and output for ODBM


IMS Problem InvestigatorThe first interactive log analysis tool for IMSUsed in dozens of Global 2000 enterprises in over 15 countriesActively developed product: significant enhancements being released continuouslyFull detailed support for CEX ODBM event recordsIncludes Code Points and DDM Objects


IMS PI and Open DatabaseOpen database requests are captured in the CEX journalIMS PI can format the requests Interprets standard DDM objectsInterprets IMS-specific extensionsAllows you to connect DRDA requests to data IMS log and monitor data, OMEGAMON ATF


InitiationFileMenuEditModeNavigateFilterTimeLabelsOptionsHelpIMSPICEX000.QADATA.REDBOOK.DRDAT111.ICON.D1003Record00000001More:Command===>Scroll===>CSRForwards/Backwards..00.00.00.000100TimeofDay..16.46.22.845746CodeDescriptionDate2010-03-31WednesdayTime(LOCAL)/--------------------------------------------------------------------------A000IMSConnectExtensionsControlInformation13.26.14.140845A05BDRDA1041EXCSAT-ExchangeServerAttributes13.46.43.550577A05BDRDA106DACCSEC-AccessSecurity13.46.43.550630A05CDRDA1443EXCSATRD-ServerAttributesReplyData13.46.43.550655A04AWRITESocket13.46.43.550715A05BDRDA106ESECCHK-SecurityCheck13.46.44.165876A063ODBMSecurityExitcalled13.46.44.166018A064ODBMSecurityExitreturned13.46.44.166131A05CDRDA1219SECCHKRM-SecurityCheckReplyMessage13.46.44.166155A04AWRITESocket13.46.44.166264A05BDRDA2001ACCRDB-AccessRDB13.46.44.794057A05DODBMbeginAllocatePSB(APSB)Program=AUTPSB1113.46.44.794080A061ODBMRoutingExitcalled13.46.44.794090A062ODBMRoutingExitreturned13.46.44.794258A069MessagesenttoODBM13.46.44.794711A06AMessagereceivedfromODBM13.46.45.067997A05EODBMendAllocatePSB(DPSB)Program=AUTPSB1113.46.45.068131


Open database queryFileMenuEditModeNavigateFilterTimeLabelsOptionsHelpIMSPICEX000.QADATA.REDBOOK.DRDAT111.ICON.D1003Record00000057More:Command===>Scroll===>CSRForwards/Backwards..00.00.00.000100TimeofDay..16.46.22.845746CodeDescriptionDate2010-03-31WednesdayTime(LOCAL)/--------------------------------------------------------------------------A048TriggerEventforODBMMSG13.46.47.193554A05BDRDA200COPNQRY-OpenQuery13.46.48.120747A05BDRDACC05DLIFUNC-DL/Ifunction13.46.48.120837A05BDRDACC01INAIB-AIBdata13.46.48.120890A05BDRDACC04RTRVFLD-Fieldclientwantstoretrievedata13.46.48.120943A05BDRDACC04RTRVFLD-Fieldclientwantstoretrievedata13.46.48.121013A05BDRDACC06SSALIST-Listofsegmentsearchargument13.46.48.121066A069MessagesenttoODBM13.46.48.121224A06AMessagereceivedfromODBM13.46.48.124238A05CDRDA2205OPNQRYRM-OpenQueryComplete13.46.48.124345A04AWRITESocket13.46.48.124514A048TriggerEventforODBMMSG13.46.48.124552A05BDRDA200COPNQRY-OpenQuery13.46.49.009514A05BDRDACC05DLIFUNC-DL/Ifunction13.46.49.009586A05BDRDACC01INAIB-AIBdata13.46.49.009637A05BDRDACC04RTRVFLD-Fieldclientwantstoretrievedata13.46.49.010758A05BDRDACC04RTRVFLD-Fieldclientwantstoretrievedata13.46.49.010828


Elapsed timesFileMenuEditModeNavigateFilterTimeLabelsOptionsHelpIMSPICEX000.QADATA.REDBOOK.DRDAT111.ICON.D1003Record00000001More:Command===>Scroll===>CSRForwards/Backwards..00.00.00.000100TimeofDay..16.46.22.845746CodeDescriptionDate2010-03-31WednesdayTime(Elapsed)/--------------------------------------------------------------------------A000IMSConnectExtensionsControlInformation13.26.14.140845A05BDRDA1041EXCSAT-ExchangeServerAttributes20.29.409732A05BDRDA106DACCSEC-AccessSecurity0.000052A05CDRDA1443EXCSATRD-ServerAttributesReplyData0.000024A04AWRITESocket0.000060A05BDRDA106ESECCHK-SecurityCheck0.615160A063ODBMSecurityExitcalled0.000142A064ODBMSecurityExitreturned0.000113A05CDRDA1219SECCHKRM-SecurityCheckReplyMessage0.000023A04AWRITESocket0.000109A05BDRDA2001ACCRDB-AccessRDB0.627793A05DODBMbeginAllocatePSB(APSB)Program=AUTPSB110.000022A061ODBMRoutingExitcalled0.000010A062ODBMRoutingExitreturned0.000168A069MessagesenttoODBM0.000452A06AMessagereceivedfromODBM0.273286A05EODBMendAllocatePSB(DPSB)Program=AUTPSB110.000133


Standard DDM FileMenuFormatHelpIMSPICEX000.QADATA.REDBOOK.DRDAT111.ICON.DRecord00000021Line00000019Command===>Scroll===>CSRForm===>+UseForminFilterFormat===>FORM+001DType.......01RQSCRR.....0001+0020Object.....2001ACCRDB-AccessRDB+0020Length.....+60CP.........2001+0024Object.....2110RDBNAM-RelationalDatabaseName+0024Length.....+17CP.........2110+0028Data.......'AUTPSB11.ODB1'+0035Object.....210FRDBACCCL-RDBAccessManagerClass+0035Length.....+6CP.........210FData.......2407+003BObject.....112EPRDID-Product-specificIdentifier+003BLength.....+20CP.........112E+003FData.......'IMSOPENDBV1.0'+004FObject.....002FTYPDEFNAM-DataTypeDefinitionName+004FLength.....+13CP.........002F+0053Data.......'QTDSQL370'


Sequence in detailFileMenuFormatHelpIMSPICEX000.QADATA.REDBOOK.DRDAT111.ICON.DRecord00000035Line00000019Command===>Scroll===>CSRForm===>+UseForminFilterFormat===>FORM+001DType.......01RQSCRR.....0001+0020Object.....200COPNQRY-OpenQuery+0020Length.....+37CP.........200C+0024Object.....2141MAXBLKEXT-MaximumNumberofExtraBlocks+0024Length.....+6CP.........2141Data.......0000+002AObject.....C907PCBNAME-PCBname+002ALength.....+11CP.........C907Data.......'EMPLPCB'+0035Object.....2114QRYBLKSZ-QueryBlockSize+0035Length.....+8CP.........2114Data.......00008000+003DObject.....2156QRYROWSET-QueryRowsetSize+003DLength.....+8CP.........2156Data.......00000001*********************************Endofdata*********************************


Details of input and outputFileMenuFormatHelpIMSPICEX000.QADATA.REDBOOK.DRDAT111.ICON.DRecord00000050Line00000019Command===>Scroll===>CSRForm===>+UseForminFilterFormat===>FORM+001DType.......03RQSCRR.....0001+0020Object.....CC06SSALIST-Listofsegmentsearchargument+0020Length.....+55CP.........CC06+0024Object.....C905SSACOUNT-Numberofsegmentsearcharguments+0024Length.....+6CP.........C905Data.......0002+002AObject.....C906SSA-Segmentsearchargument+002ALength.....+32CP.........C906+002EData.......'EMPL*D(EMPNOGE)'+004AObject.....C906SSA-Segmentsearchargument+004ALength.....+13CP.........C906+004EData.......'EMPLINFO'*********************************Endofdata*********************************


Solving problemsSession errors: these are conditions that generate distinct error. For example, specifying the wrong alias name, trying to access a stopped PSB.Performance problems: IMS provides an output but processing time is slow.Unexpected responses: the client receives information from IMS but it is not the feedback that the client was expecting.


FilteringFileMenuViewHelpIMSPIFilterRow1of1More:Command===>Scroll===>CSRFilter.....+Description...NewLogRecordFilterActivateTracking/LogCode+ExcDescriptionCONA047SessionErrorLevel1ConditionsNoForm+REXX------------------------------------------------------------------------------*******************************Bottomofdata********************************

FileMenuEditModeNavigateFilterTimeLabelsOptionsHelpIMSPICEX000.QADATA.REDBOOK.ERR01.ICON.D100331Record00000027More:Command===>Scroll===>CSRForwards/Backwards..00.00.00.000100TimeofDay..16.46.22.845746CodeDescriptionDate2010-03-31WednesdayTime(LOCAL)/--------------------------------------------------------------------------A047SessionError11.54.55.710442A047SessionError12.03.02.490039A047SessionError12.32.09.670281********************************BottomofData*******************************


Details of errorFileMenuFormatHelpIMSPICEX000.QADATA.REDBOOK.ERR01.ICON.D100Record00000027Line00000016Command===>Scroll===>CSRForm===>+UseForminFilterFormat===>FORM+001ACERE_47_VAR_MSG....134bytemessagearea+0000C8E6E2D2F2F8F7F5E640D5D640D6C4C2*HWSK2875WNOODB*+0010D440C9E240C1E5C1C9D3C1C2D3C540C6*MISAVAILABLEF*+0020D6D940D4C5E2E2C1C7C540D9D6E4E3C9*ORMESSAGEROUTI*+0030D5C75E40C37ED6C4C2F3C3F0F4F16B40*NG;C=ODB3C041,*+0040C9D4E2C17ED3C1D3C16B40D77EF4F8F8*IMSA=LALA,P=488*+0050F5F54040406B40C9D4E2C1F17E404040*55,IMSA1=*+0060406B40D6C4C2D47E4040404040404040*,ODBM=*+00706B40D97EC9D4E2C1D5C6D5C46B40D47E*,R=IMSANFND,M=*+0080D4D9C3E50000*MRCV..*+00A0CERE_47_VAR_SESRSN.........'WRITE'+00A8CERE_47_VAR_TOKEN..........0000000000000000*********************************Endofdata*********************************


OMEGAMON ATFApplication-level accountingIdentify DLI call times and CPU utilizationUse with IMS PI filtering and tracking to proactively identify problemsResolve problems by tracking from ATF records to all other available records (in the IMS log, DB2, etc)


Combining ATF with Open DBFileMenuEditModeNavigateFilterTimeLabelsOptionsHelpBROWSECEX000.QADATA.REDBOOK.DRDAT111.ICON.D1003Record00000308More:Command===>Scroll===>CSRForwards/Backwards..00.00.00.000100TimeofDay..16.46.22.845746CodeDescriptionDate2010-03-31WednesdayTime(LOCAL)/--------------------------------------------------------------------------A049READSocket13.46.47.095038A05BDRDACC06SSALIST-Listofsegmentsearchargument13.46.47.095045A0AAODBMTrace:MessagesenttoODBM13.46.47.095985A069MessagesenttoODBM13.46.47.09601606OSAMIWAITstartTranCode=ODBA02CDRegion=000313.46.47.14289120DatabaseOpen Database=EMPDB2Region=000313.46.47.14364706OSAMIWAITstartTranCode=ODBA02CDRegion=000313.46.47.18150620DatabaseOpen Database=AUTODBRegion=000313.46.47.18225206OSAMIWAITstartTranCode=ODBA02CDRegion=000313.46.47.19144201DLIGHUDatabase=EMPLDB2SC=''Elapse=0.09587513.46.47.096570B021DLIDatabaseTraceDatabase=EMPLDB2Func=GHU13.46.47.192378A0AAODBMTrace:MessagereceivedfromODBM13.46.47.192881A06AMessagereceivedfromODBM13.46.47.192909A05CDRDA2205OPNQRYRM-OpenQueryComplete13.46.47.193186A04AWRITESocket13.46.47.193515A048TriggerEventforODBMMSG13.46.47.193554A03CPrepareREADSocket13.46.48.120636


IMS Performance AnalyzerIMS PA provides performance reportsProactive and reactive toolHelp identify problemsMeet SLAsPlan and optimize capacity


IMS Configuration ManagerIMS Configuration Manager is a rebranding of IMS Parameter ManagerRepresents the introduction of significant new features and a refocus of the productFocus changes from managing IMS parameters to managing IMS resourcesRetains most parameter management functionalityAdds ability to edit, browse, and install IMS resourcesLeverages DRD


Open databaseNow: helps you set up ODBM and IMS Connect address spaceFuture requirement: provides a control web interface where you can manage your IMS environment


Future suggestionsImproved reporting in IMS PA ODBM End to End reportingMore flexible forms of tracking in IMS PIBetter address-space management and GUI-based administration (ICM)


ConclusionsOpen database is a significant enhancement to IMSSimplifies application development for IMSCreates challenges for system administration IMS Tools are evolving to help address these challengesYour thoughts?


LiteratureUpcoming IMS Open Database RedbookIMS Application Programming APITechnical Standard: DRDA, Version 4, Volume 1 and V3


More informationIBM DB2 and IMS Tools website: http://www.ibm.com/software/data/db2imstools/

Jim Martin, US Representative, Fundi Software:[email protected]


The current solution (whether or not we are talking about distributed or local access to IMS DB) leverages ODBA as the API to access IMS database resources. ODBA is capable of making address space to address space calls (PC calls) in the same logical partition. The net effect of this is that the ODBA modules need to be on the same LPAR as the IMS CTL region. These modules (ODBA) are loaded in the address space of the application, which is in turn loaded in the address space of the container. In this case the container is WebSphere AS. The result of this is that the WAS installation has to be on the same LPAR as the IMS DB itself. There is no isolation.

What we are doing is creating a new Common Server Layer (CSL) address space to house the ODBA modules. This interface will use SCI as its communication mechanism. The ODBA modules are no longer tightly coupled with the applications themselves (and therefore the containers).

By leveraging SCI, the applications can be on any LPAR in an IMSplex. SCI uses either PC or XCF calls to communicate with other SCI components. XCF allows calls to go across LPARs in an IMSplex. This allows applications (and their containers) to be isolated on their own LPARs.

The IMS Open Database environment leverages IMS Connect as the complete gateway solution for IMS TM, OM, and now DB. IMS Connect will become an ODBM client. This will allow distributed applications to leverage the TCP/IP protocol to communicate with IMS Connect, which can then access any database in the entire IMSplex.-------IMS Connect becomes the IMS Gateway to both IMS TM and IMS DB. WebSphere and DB2 Stored Procedures no longer have to be on the same LPAR with IMS when they interface with the IMS ODBM (Open Database Manager) address space. The ODBM address space must be on the same LPAR with IMS due to the use of the ODBA (Open Database Access) interface.Distributed clients would now have the option of going directly to IMS Connect for IMS DB requests.The Protocol we have chosen to communicate to IMS Connect is DRDADRDA is the industry standard for DB access in a distributed transaction processing environmentThe Two Phase Commit and Security flows are imbedded in DRDAThe DLI API will be both IMS DLI traditional and advanced concepts (Like DELETE does not require the caller to make a hold call first)

Typically, customers use IMS Connect Extensions routing to improve availability and simplify the management of IMS Connect clients. However, here we can see how IMS Connect Extensions routing can be used to improve performance. In this case, we are using generic routing to map a single dest id to multiple datastores (i.e. TCBs) pointing to the same phyisical IMS system. The advantage of this is that you can introduce greater parallelism in OTMA and this can often (but not always) help improve overall transactional performance.

ims connect and ims odbm: an early look

Documents

ims odbm

data ims log

open standards

open databasetools

odbm performanceinput

monitor data

cex journalims pi

significant enhancements