Advanced DBA – High Availability for MUF

World®’16

AdvancedDBA–HighAvailabilityforMUFKevinShumaVP,ProductManagementCATechnologies

MFX64E

MAINFRAMEANDWORKLOADAUTOMATION

2 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

Abstract

ThissessiondescribestheavailableoptionsforsitesthatneedtokeeptheirCADatacomenvironments(MUFs)operationalforextendedperiodsoftime.ThisincludefunctionalitytocoverIPLs,systemsoutagesandevenCADatacomsoftwareupgrades.

ThissessionwillprimarilycoverthenewfeaturesavailableintheCADatacom®/DBprocessingthatallowstheCADatacomenvironment(MUF)tomigratefromoneaddressspacetoanotherwithoutanoticeableoutagetotheendusers.

KevinShuma

CATechnologiesVP,ProductManagement


Agenda

WHATISHIGH-AVAILABILITYFORDATABASEENVIRONMENTS

DATASHARINGSHADOWTECHNOLOGY

ACTIVE-QUERY(ACTIVE-ACTIVEARCHITECTURE)

SUMMARY

1

2

3

4


Whatishigh-availability?

“Highavailabilityisacharacteristicofasystem,whichaimstoensureanagreedlevelofoperationalperformance,usuallyuptime,forahigherthannormalperiod.”

“Ifausercannotaccessthesystem,itis- fromtheuserspointofview– unavailable.Generally,thetermdowntimeisusedtorefertoperiodswhenasystemisunavailable.”

AccordingtoWikipedia

24x7


Whatishigh-availabilityfordatabaseenvironments

§ TheabilityfortheDatacomenvironment(MUF)toremainupormigratefromoneaddressspacetopanotherwithoutanoticeableoutagetotheend-user– Donotinterruptuserdataaccessfor

§ MUFfailures§ IPLs§ Softwaremaintenance§ Softwareupgrades(newreleases)§ JustabouteverythingaSYSPROG“needs”todotokeepasystemrunning

FromaCADatacomperspective


Datasharingshadowtechnology


§ CADatacomsupports3differentdatasharingtechniques

§ TheShadowMUFistherecommendedandmostusedtechnique– Provides24x7failover– ProvidesmigratecapabilitiesforuseduringIPLs– Providescapabilitiesforimplementingsoftwaremaintenance– (V15.0)Providescapabilitiesforimplementinganewrelease

AspecialformofDataSharingShadowTechnology


§ PrimaryMUF– istheMUFinstanceupandenabledatthatmomentoftime

§ ShadowMUF– isthesecondinstanceoftheMUFthatisconsiderednotenabledbutrunningonsameLPARoradifferentLPARonthesameSYSPLEX

§ BothMUFssharethesamesetofdatabases(DASD)

AspecialformofDataSharing

Primary

Shadow

ShadowTechnology(cont’d)


§ XCFisusedasthemessageservicebetweentheshadowandtheprimaryMUF

§ IfXCFserviceisstoppedorabends– Possiblelossofcommunicationbetween

thePrimaryandShadowMUFispossible– ShadowMUFcannottakeover,must

beforcedtotakeover– Thisisveryrareintoday’sworld


Primary

Shadow



§ XCFmessages– PrimaryMUFDSNZMFM1

DSNZMFM1:MUFM1:DB02330W- SHADOWSTART,JOB=DSNZMFM2SYSTEM=CA31

– ShadowMUFDSNZMFM2DSNZMFM2:*:DB02301I- XESGROUPJOINED(QAPLEX1,SHADOW$$071)

DSNZMFM2:*:DB02325I- SHADOWMUFNOWWAITING


Primary

Shadow




§ Unplannedoutage– PrimaryMUFfails– LPARfails

§ Plannedoutage– ScheduledIPL– NeedtochangeMUFstart-upoptions– Scheduledsoftwaremaintenance– Scheduledreleaseupgrade(V14toV15)


Primary

Shadow


ShadowTechnology– Unplannedoutage

§ UnplannedShadowMUF– NoCFStructures– OnlyoneMUFupatatime,nointersection

oftwoMUFinstancescanoccur– NoworriesaboutMRDF,CBSandPXX

beingshared


Primary

Shadow


§ Applicationregionsuse“accessanywhere”toconnecttoprimaryMUF

§ ShadowMUFisstarted(sameordifferentLPAR)

§ XCFisusedtoSYNCMUFs

§ Shadow“watches”primary

§ ShadowopensallMUFdatasets,butdoesnotdorequestprocessing

LPAR

1

CICSPLEXBATCH

CICSPLEXXCF

LPAR

2

CICSTOR

CICSTOR

DSNZMFM1

DSNZMFM2RemoteShadow

ShadowMUFPLEX

Allocation/Openonly

FullAccess

XMEM

ShadowTechnology– UnplannedoutageAspecialformofDataSharing


§ PrimaryMUF(MUFPLX1)fails

§ ExistingtransactionsnotifiedofMUFfailure

§ RemoteShadowautomaticallydetectsfailure

§ RemoteShadowbeginsclean-upoffailedMUF

§ Newrequestscanbetoldto“wait”

§ RemoteShadowbecomesMUFPLX1

ShadowTechnology– Unplannedoutage(cont’d)LPAR

1

CICSPLEXBATCH

CICSPLEXXCF

LPAR

2

CICSTOR

CICSTOR

DSNZMFM1

BATCHNewDBreqwait NewDBreqwait

Fullaccess/beginclean-upandnewwork

XMEM

ShadowMUFPLEXDSNZMFM2

RemoteShadow


§ Applicationswithreconnectcapabilitiesre-establishconnectionsandcontinueprocessing

§ Briefpauseinservice,butnotanoutage

§ SiterestartsfailedMUFregionanditautomaticallydetectsthatitisnowtheShadowLP

AR1

CICSPLEXBATCH

CICSPLEXXCF

LPAR

2

CICSTOR

CICSTOR

ShadowMUFPLEX

NewBATCH

FullAccess

XMEM

Allocation/Openonly

DSNZMFM1RemoteShadow

DSNZMFM1

ShadowTechnology– Unplannedoutage(cont’d)


§ PlannedShadowMUF– CFstructurerequired– TwoMUFscanbeupsotherulesforfulldatasharing

arenowenforced– CanusetheMigratecommandordotheprocess

manually– IfeitherMUFinstancefailsduringthisprocess,must

restarttheMUFinstancethatfailedASAP– EOJofeitherMUFinstanceremovestheaspectsoffull

datasharing– TimelinefortwoMUFinstancesbeingupatthesame

timeshouldbeconsideredtobebrief

AspecialformofDataSharingShadowTechnology– Plannedoutage

Primary

Shadow


§ IssueMIGRATEcommandtoconvertRemoteShadowintoafulldatasharingMUF

§ CouplerFacilityusedtosynchronizetwomemberMUFs

§ BothMUFsnowfullparticipants

ShadowTechnology– PlannedoutageLPAR

1

CICSPLEXBATCH1

CICSPLEX

XCF

LPAR

2

CICSTOR

CICSTOR

ShadowMUFPLEXforIPLCoupler

XMEM

FullAccess FullAccess

DSNZMFM1

DSNZMFM2ActiveMUF


§ AllapplicationsnowrunningonLPAR2

§ StopMUFonLPAR1§ Useofcouplerstops§ IPLLPAR1§ OncecompleterestartShadowonLPAR1

§ CouldissueMIGRATEtoreverttooriginalstate

§ CoulduseShadowonLPAR3whileLPAR1IPL’d

ShadowTechnology– Plannedoutage(cont’d)

SVC

LPAR

1

CICSPLEXBATCH1

CICSPLEX

LPAR

2

CICSTOR

CICSTOR

MUFPLX1

ShadowMUFPLEXforIPL

Coupler

BATCH2BATCH3

EOJ

EOJ

EOJ

EOJ

FullAccess

DSNZMFM2ActiveMUF



§ Upgradefrom14.0to15.0– Recommendthecodeonlybedoneatthistime– OneMUFinstancecanbe14.0– OtherMUFinstancecanbe15.0– RecommendnotleavingbothMUFinstancesup

verylong– DBIDFormat3andDBIDFormat2messageswill

beoccurringinbothMUFs


Primary

Shadow



§ Recommendyoubringdownthe14.0MUFinstanceassoonasyoucan

§ ThenrestarttheShadowMUFas14.0forfallback

§ Thisupgradeprocessissupported,butitisnotthepathweexpecttheclientstotake– UpgradepathshouldnotbedonewithtwoMUFsup


Primary

Shadow


ShadowTechnology– OtherConsiderations

§ ProductssuchasCA7andCA11havethebuilt-inlogictorecognizeaMUFfailureandautomaticallyreconnecttotheShadowwithoutlossofinformation

§ CADatacomprovidesasuiteof“online”utilitiessothatitemslikedatareorganizationaresupportedwhilethedataisinuse– Thesefunctionsarenotallowedwhenrunningdatasharingmodefor

twoormoreMUFinstancesatthesametime



ShadowTechnology– OtherConsiderations(cont’d)

§ HowAreClientsUsingShadow?– Largenumberofsiteshavenotimplementedthis– Fortheoneswhohave,probablyover90%usetheunplannedversion

ofShadow(noCFstructure)– Theremaining5-10%usetheplannedoutageoftheShadowMUF

(requiresCFstructure)



Active-Query(Active-ActiveArchitecture)


RemoteReplicationTechnology

§ Active-Standby

§ Active-Query

§ Active-Active

ActiveArchitecture


RemoteReplicationTechnology– ActiveStandby

§ Primaryimagerunsinfullupdatemode– Usertransactionsaredirectedbyarouterto

thecurrent“primary”datamanager– Dynamicswitchingcanoccurtoshiftworkload

iftheprimarydatamanagerfails– Secondary“standby”imagedoesnotprocess

anyuserwork– Allusersissuedatarequestsontheprimary

image– Datachangesarereplicatedinatimelyfashion

fromtheprimarytothestandbyimage

ActiveArchitecture


RemoteReplicationTechnology– ActiveQuery

§ Primaryimagerunsinfullupdatemode– Userupdatetransactionsaredirectedbya

routertothecurrent“primary”image– Dynamicswitchingcanoccurtoshift

workloadiftheprimaryimagefails– Userquerytransactionscanbedirectedto

the“query”imagewhichallowsworktobeprocessed

– Datachangesarereplicatedinatimelyfashionfromtheprimarytothequerydatamanagementimage

ActiveArchitecture


RemoteReplicationTechnology

§ ComponentsUsed

§ Prerequisites

§ MQTSOverview

§ OperationalOverview

§ SampleOutput

ActiveQuery– DatacomV14.02


RemoteReplicationTechnology- Components

§ ChangeDataCapture(CDC)– Builtinfacilitytocapturechangesforselectedtables– ChangesstoredinaDatacomdatabaseasTSNandMNTrows

§ MQTransportService(MQTS)- PartofIPC15.0– NewIPCfacilitytoenableDatacomcomponentstointeract

withIBMMQ

§ NewCDCRemoteReplicationcomponent– NewDatacomdeliverablesthatmovethedatafromtheCDC

acrossMQtoatargetMUF

ActiveQuery– DatacomV14.02/IPCV15.0


RemoteReplicationTechnology- Prerequisites

§ SourceMUFenvironment

§ TargetMUFenvironmentsynchronizedtosourceMUF

§ MQsubsystemsforeachenvironment– MQqueuesdefinedforsendingfromsourcetotargetsystem

§ IPC15.0installed(MQTS)

§ CDCremotereplicationservicesinstalled– RO81655forR14– RO81529forR15



RemoteReplicationTechnology- MQTS

§ OperatesonIBMMQqueues– RequiresMQsetup,partofIPC15.0(compatiblewithDB14.0and15.0)

§ MQTSusesaworkloadIDtoconstructtheMQqueuenames– CAMQTS.queue.workloadID– Wherequeueis:

§ SOD– Source,outgoing,data(connectswithremote’sTID)§ SID– Source,incoming,data(connectswithremote’sTOD)§ TOD– Target,outgoing,data(connectswithremote’sSID)§ TID– Target,incoming,data(connectswithremote’sSOD)§ XQ– Transmissionqueue



RemoteReplicationTechnology– MQTS(cont’d)

§ MQTStoMQChannels

§ MQTSusestheworkloadIDtoconstructtheMQchannelnames– CAMQTS.channel.workloadID– Wherechannelis:

§ HA– SystemAtoBcommunication§ HB– SystemBtoAcommunication

§ Remote’schannelnamesmustmatchlocal’schannelnames



RemoteReplicationTechnology– MQOverviewActiveQuery– DatacomV14.02/IPCV15.0

Example:WRKLD03MQQueueRelationshipsforWorkload


RemoteReplicationTechnology– MQOverviewActiveQuery– DatacomV14.02/IPCV15.0

RemoteReplicationOperationalOverview



§ DBCDSPR- TheSender– Providecontrolstatementstogive:

§ CDCDBIDtoprocess§ TheMQTSWorkloadID§ Otherparameterstocontrolbuffersizes,waitlimits,retrycounts,etc.

– ConnectstothesourceMUF– ConnectstoMQviaMQTSSEND– SendschangeddatatothereceiverviaMQ– Respondstoconsolecommands




§ DBCDRPR– TheReceiver– Providecontrolstatementstogive:

§ TheMQTSWorkloadID§ Otherparameters

– ConnectstothetargetMUF– ConnectstoMQviaMQTS– GeneratesURTsforthetargetMUF– ReceivesMQdataviaMQTSRECEIVE– AppliesupdatestothetargetMUF– Respondstoconsolecommands



SampleOutputSenderActiveQuery– DatacomV14.02/IPCV15.0


SampleOutputSender(cont’d)ActiveQuery– DatacomV14.02/IPCV15.0

Senderthroughputstatistics,responsetoSTATUScommand


SampleOutputReceiverActiveQuery– DatacomV14.02/IPCV15.0

Receivermessagesatstartup


SampleOutputReceiver(cont’d)ActiveQuery– DatacomV14.02/IPCV15.0

Receiverthroughputstatistics,responsetoSTATUScommand


RemoteReplicationTechnology- Summary

§ NewMQTransportServiceprovides– MQwrappersothatsender/receiverdon’thavetohaveMQknowledge

§ CDCusedtocapturechangesatsource

§ Senderusedtopackagesourcechangesandsendtoreceiver– OncesentdeleteschangesfromsourceCDC

§ ReceiverusedtotakepackagedchangesfromMQandapplytotargetMUF– OnceapplieddeletespackagefromMQ



SummaryAFewWordstoReview

ExperiencesVarioussiteshasusedthesefunctionstokeeptheirdatabaseenvironmentavailable24x7foranumberofyears.

KeyTopicsIntoday’sworld,databaseenvironmentsmustbeabletoprovide24x7access.

FindingsCADatacomShadowMUFdelivershigh-availabilitywhilethenewRemoteReplicationfeaturesetsthebaseforcontinuousavailability.

@CAWORLD#CAWORLD ©2016CA.AllRIGHTSRESERVED.42 @CAWORLD#CAWORLD ©2016CA.AllRIGHTSRESERVED.42

MainframeandWorkloadAutomation

FormoreinformationonMainframeandWorkloadAutomation,pleasevisit:http://cainc.to/9GQ2JI


RecommendedSessionsSESSION# TITLE DATE/TIME

MFX92S StrategyandVisionforCADatacomandCAIdeal 11/16/2016at12:45pm

MFX93S What’snewinCADatacom 11/16/2016at1:45pm

MFX94S ReducingTCOwithDatacomCompression(Presspack) 11/16/2016at3:00pm

MFX95SA ModernizingtheCADatacomdata – SQLAccessPartI 11/16/2016at3:45pm

MFX95SB ModernizingtheCADatacomdata – SQLAccessPartII 11/16/2016at4:30pm

MFX96S CADatacom/ADInstallation/UpgradeandMaintenance 11/17/2016at12:45pm

MFX97S CADatacom/ADReportUtilization,andinformationgatherforSupport 11/17/2016at1:45pm

MFX98SUsingSysview tomonitorandmeasureyourCADatacomenvironment– ADandDB

11/17/2016at3:00pm

MFX99S BirdsofaFeather/StumptheTechie! 11/17/2016at3:45pm


Questions?


Thankyou.

Stayconnectedatcommunities.ca.com


©2016CA.Allrightsreserved.Alltrademarksreferencedhereinbelongtotheirrespectivecompanies.

Thecontentprovidedinthis CAWorld2016presentationisintendedforinformationalpurposesonlyanddoesnotformanytypeofwarranty. The informationprovidedbyaCApartnerand/orCAcustomerhasnotbeenreviewedforaccuracybyCA.

ForInformationalPurposesOnlyTermsofthisPresentation