This sectioncoversmigrationfromaCICSsystemwithlocalDL/I,toa CICS TransactionServerfor z/OS,Version2Release3system withDBCTL.
v “Othermethods foraccessingDL/I”
v “CICS-IMSreleasecompatibility”
v “PossiblemigrationpathstoCICSTransactionServerfor z/OS,Version2 Release3withDBCTL”onpage 16
v “Suggestedmigrationprocedureto DBCTL”onpage 17 v “Planningyournew DBCTLsetup”onpage 18
v “SettinguptestandproductionsystemsforCICSDBCTL”onpage19
SeeAppendixA,“Migrationtask summaryfor DBCTL,”onpage165fora checklist of taskstobedoneto migratetoDBCTL,andalist offallbackconsiderations.
SeetheCICSTransactionServerforz/OSMigrationfromCICSTSVersion2.2and theIMSReleasePlanningGuideforinformationonmigratingto CICSTransaction Serverfor z/OS,Version2 Release3 andtoIMS/ESArespectively.
Other methods for accessing DL/I
Remote databasesupportremainsinCICSforfunction-shippedDL/Irequests.Your remotedatabasescanbemanagedeither bylocalDL/I (iftheremoteCICSis CICS/ESA 4.1or below)orbyDBCTL.
Function shippingsupportstheadditionalsystemservicerequests,DEDBrequests, andenhancedscheduling(usuallyknownas“dataavailability”)supportedbya DBCTLenvironment,allof whicharedescribedinChapter7,“Application programming forDBCTL,”onpage93.
Withdrawn support of local DL/I and shared database
CICSTransactionServerdoesnotsupportlocalDL/I orbatchshareddatabase.
Batch jobsthatusetheCICSshareddatabasefacilitycannotaccessdatabases ownedbyDBCTL.If youwantto useCICSshareddatabasejobs withDBCTL,you must migratethemtorunasBMPs,whichcommunicatedirectlywiththeDBCTL address space.
CICS-IMS release compatibility
Thestartingpoint formigrationisa CICSsystem runningwithlocalDL/I.Theaimis to installCICSTransactionServerfor z/OS,Version2Release3 andIMS/ESA Version6 orlater.Table1shows whichCICSandIMSreleasescanbeused together, andwhethertheycanbeusedwithDBCTL,localDL/I,or both.
Table1.CICS-IMSreleasecompatibility
CICS LocalDL/I DBCTL
CICSTransactionServerfor OS/390,Version1Release1
---- IMS/ESA3.1IMS/ESA4.1
IMS/ESA5.1IMS/ESA6.1 IMS/ESA7.1
CICSTransactionServerfor OS/390,Version1Release2
---- IMS/ESA3.1IMS/ESA4.1
IMS/ESA5.1IMS/ESA6.1 IMS/ESA7.1
Table1.CICS-IMSreleasecompatibility (continued)
CICS LocalDL/I DBCTL
CICSTransactionServerfor OS/390,Version1Release3
---- IMS/ESA5.1IMS/ESA6.1
IMS/ESA7.1 CICSTransactionServerfor
z/OSVersion2Release1
---- IMS/ESA5.1IMS/ESA6.1
IMS/ESA7.1 CICSTransactionServerfor
z/OSVersion2Release2
---- IMS/ESA6.1IMS/ESA7.1
CICSTransactionServerfor z/OS,Version2Release3
---- IMS/ESA6.1IMS/ESA7.1
Anyattemptto connectCICS,withstorageprotectionactive,to aDBCTL
subsystemrunningIMS/ESA3.1resultsinCICSterminatingtheconnectionattempt abnormally. MessageDFHDB8118withreturncode4issent totransientdata destination CDBC,indicating thatCICSdetected thatthereleaseof IMS/ESAdoes notsupporttheMVSsubsystemstorage-protectionfacility.CICSonlyallows connection tothis DBCTLsubsystemifstorageprotectionisturned off.
Possible migration paths to CICS Transaction Server for z/OS, Version 2 Release 3 with DBCTL
This sectionoutlinessomepossiblemigrationscenariostoCICSTransactionServer for z/OS,Version2 Release3 withDBCTL, accordingto yourcurrentsetup.
v “CICSwithlocalDL/I”
v “CICSwithlocalDL/Ianddatasharing”
v “CICSwithshareddatabase”
v “CICSwithIMSdatasharingandbatch”onpage17 v “CICSwithfunction shipping”onpage17
v “CICSwithIMS/ESADM/TM”onpage17
CICS with local DL/I
CICSwithlocalDL/I:
1. CICS/ESA 4.1withlocalDL/IwithIMS/ESAVersion4orbelow
2. CICS/ESA 4.1withlocalDL/IwithIMS/ESAVersion3orlaterandDBCTL (optional)
3. CICSTransactionServerforz/OS,Version2 Release3withDBCTL.
CICS with local DL/I and data sharing
1. CICS/ESA 4.1withlocalDL/IwithIMS/ESAVersion4orbelowdatasharingin a single-MVSenvironment
2. CICS/ESA 4.1withlocalDL/IwithIMS/ESAVersion3orlaterandDBCTLwith data sharing(optional)
3. CICSTransactionServerforz/OS,Version2 Release3withDBCTLwithout data sharing.
CICS with shared database
1. CICS/ESA 4.1withlocalDL/IwithIMS/ESAVersion4orbelowCICSshared database
2. CICSTransactionServer forz/OS,Version2 Release3 withDBCTLand BMPs—CICSshareddatabaseprogramsconvertedto BMPs.
CICS with IMS data sharing and batch
1. CICS/ESA 4.1withlocalDL/IwithIMS/ESAVersion4 orbelowanddata sharingwithbatchina single-MVSenvironment
2. CICSTransactionServer forz/OS,Version2 Release3 withDBCTLandBMPs without datasharing—batchprogramsconvertedto BMPsina single-MVS environment.
CICS with function shipping
1. CICS/ESA 4.1withIMS/ESAVersion4orbelow, localDL/I—multipleMRO regions—TORs,AORs,andDORs
2. MultipleCICSTransactionServerfor z/OS,Version2Release3systemsusing DBCTL—DBCTLreplacesDORs.
CICS with IMS/ESA DM/TM
Scenario 1
1. CICS/ESA 4.1withlocalDL/IandIMS/ESADM/TMversion4 orlaterdata sharing(possiblyinamulti-MVSenvironment)
2. CICSTransactionServer forz/OS,Version2 Release3 withIMS/ESATM Version6 orlaterwithDBCTLinasingle-MVSenvironment.
Scenario 2
1. CICS/ESA 4.1withIMS/ESADM/TMVersion3orlaterwithLU6.1ina single-MVSenvironmentormulti-MVS
2. CICSTransactionServer forz/OS,Version2 Release3 withIMS/ESADM/TM Version6 orlaterwithDBCTL(applicationprogramrewritten) ina single-MVS environment.
Suggested migration procedure to DBCTL
If youalreadyuseCICSwithDL/I,asuggestedmigrationpathisasfollows:
v InstallMVS(without changingyour CICSor IMSsystems).
v InstallIMS/ESAVersion4(Version5does notsupportlocalDL/I).
v InstallCICS/ESA 4.1withIMS/ESAVersion4 runninglocallyandputthese systemsintoproductiontogether.(Atthisstage,therearenogreatchangesin theCICS-DL/Ienvironment.)
v Convertto DBCTL.
v InstallCICSTransactionServerfor z/OS,Version2Release3.
You willprobably wantto migratetoDBCTLinstages, perhapsasfollows:
1. Set upa testsystem.If youalreadyhavea testsystemthatisusedfor testing new applications,considerusingit fortestingmigrationtoDBCTL.
2. If youdonotwanttobeginwitha testsystem,beginbysettingupa trial productionsystem,perhapsoneyoualreadyusefor testingexistingproduction applicationproblems.
3. Set upa productionDBCTL.
You then:
v GenerateDBCTL,DLISAS, andDBRC.
Youmust useDBRCwithDBCTL.IfyouarenotfamiliarwithusingDBRC,you shoulduseit initiallyjust tocontrollogfacilities.Todothis,specifySHARECTL whenyouinstallDBRC,butdonotregisterdatabases.
v Decidewhich applicationstomigrate.
v Takefullimagecopies ofdatabasesbeforemigratingthemto useDBCTL.Thisis becauseinformationfor CICS-DL/IdatabasesisonboththeCICSandtheIMS logs.TakinganimagecopywillensurethattheRECONisupdated, and informationforthatdatabasewillbefromtheIMSlogonly.SeetheIMS OperationsGuideforinformationontakingimagecopies,andtheIMSUtilities Reference:Databasemanualmanualfor informationontheutilitiesyoucanuse todoso.
v ConvertCICSshareddatabaseprogramsto BMPs.
v Convertanyprograms thatuseDFHFCTYPE=DLImacrosto issueDL/I commandsorcallsinstead.
v ConvertproductionCICSTransactionServerfor z/OS,Version2Release3 systems.
v TuneCICS-DBCTL.
v Convertbatchjobsto BMPs(theymustissuecheckpoints).
v WhenmigratingyourCICSshareddatabaseprogramsor“native”IMSbatch programsto BMPs,definePSBs inDBCTLsecuritygeneration.
Note: If youruntheapplicationwithCICSLocalDL/I(which IMStreats asa batchjob),IMSallowspathinsertswithout thePROCOPT=Pparameter.
IMSissuesstatuscodeAMif aCICSonlineprogramoraCICSshared databaseprogramissuesanISRTcall withtheDcommandcodewhen theprogramdoesnothave thePROCOPT=Pparameterspecifiedinthe DBPCBthatwasreferencedinthecall.IMSbatchprograms, however,do notneed thePROCOPT=PparametertoissueanISRTcall withtheD commandcode unlesstheprogramusesfieldlevelsensitivity.
If youthenconverttoDBCTL, andruntheapplicationinaBMP region (which IMStreats asonlineprocessing ratherthanbatch),youareno longerpermittedto usepathinsertswithout thePROCOPT=Pparameter.
Forinformationondoingthis,seeChapter8, “SecuritycheckingwithDBCTL,”on page115.
v ConsiderDEDBsfornew applications.
Planning your new DBCTL setup
v IfyouarerunningmultipleCICSregions,each withitsown copyof localDL/I, youarerecommendedto migrateallyourlocalDL/I systemstousea single DBCTL.Ifyou arerunningthesameapplicationsthatschedulethesamePSBs oneachofyour CICSsystems,butaccessdifferentinstances ofthesame databases,migratingtoasingleDBCTLmeansthatyouwillneedaseparate DBDandseparate PSBsfor eachinstanceofadatabase.However, your
applicationscouldcontinueto schedulethesamePSBsbecausethereisaCICS globaluserexitavailableto DL/Iuserswhichmayhelpwithmigrationtoasingle DBCTLinthiscase.ItiscalledXDLIPRE,andit enablesyouto changethePSB nameand/or theSYSIDthattheapplicationprogramhasscheduled atexecution time.AppendixE,“Usingglobaluserexit XDLIPREtochangePSBto be
scheduled,”onpage179containsanexampleofXDLIPREthatyou cancopy
andmodify.Notethatthis exampleisprovidedfor guidanceonly.SeetheCICS CustomizationGuideforprogramminginformationonusingtheseexits.
v Youhave aremoteDL/I environment,inwhichyouarerunningmultipleCICS AORsthatfunctionship DL/Irequeststo aDL/I resourceowningCICSregionin thesameMVSimage.In thiscase,replacetheDL/Iresource-owningregionwith DBCTL.However,if youarefunctionshippingDL/Irequests toaDL/I resource owningCICSregionina differentMVSimageyoucannotreplacetheDL/I resourceowningregionwithaDBCTLsubsystem.ThisisbecauseCICSand DBCTLcanonly communicatewitheach otherwhentheyareinthesameMVS image.However,theDL/Iresource owningCICSregionmust useDBCTLinstead oflocalDL/I,asshown inFigure5.In thiscase,youkeeptheDOR, butit
communicateswithDBCTL;thatis,DBCTLreplaceslocalDL/I,butnottheDOR.
v CICSTransactionServerforz/OS, Version2Release3systemsrunningina separateMVSimagefromDBCTLmustfunctionship theirDL/Irequests toa CICSTransactionServerforz/OS, Version2Release3system locatedinthe sameMVS imageasDBCTL.
v Ifyouwantbatchprograms torunconcurrentlywithCICS,andyoudonot alreadyuseIMSdatasharingorDBRC:
– InstallDBRCintheexistingCICSsystemandbecome familiarwithit before migratingto DBCTL;or
– InstallDBCTLanduseDBRC tocontrollogsonly.Runthebatchprogramsas BMPs.Whenyouarefamiliarwiththis environment,extendyourusageof DBRCto controldatabaseintegrity.
v Youhave anIMSdatasharingenvironment,inwhichyouarerunningmultiple CICSsystemsthataredatasharingwithoneanotherandwithbatch,andallthe datasharingistakingplacewithin asingle-MVSenvironment.Inthis case,you couldconsidermigratingcompletelyto asingleDBCTLwithinanMVS image insteadof usingdatasharing. Ifyoudothis,migratealltheDL/Ibatchjobs involvedtoBMPs,which willsimplifylogmanagement.
YoucanuseIMSdatasharingacrossmultipleDBCTLsinasingle-ormulti-MVS environment.
v IfyourcurrentCICSissharingdatabaseswithIMS/VSDB/DCor IMS/ESA DM/TMusingIMSdatasharing, itmaybeappropriatetomigratetousingthe IMS/VSDB/DCorIMS/ESADM/TMregionastheDBCTLregion.
Setting up test and production systems for CICS DBCTL
Notethefollowingpointswhensettingupyourtest and/orproductionsystems.
Number of DBCTL subsystems to use
You willneed todeterminethenumberof DBCTLsyourequireina single-MVS environment;forexample,oneDBCTLsubsystemforthewholeMVS image,orone DBCTLsubsystemfor eachCICSsysteminsingle-MVSenvironment.Balance®the
MVS A MVS B
AORs DOR DBCTL
Figure5.FunctionshippingtoaDORinadifferentMVSimagewithDBCTL
numberof DBCTLswithina singleMVSimageagainsttheamountofCSAneeded.
Also, beawareof theneed todifferentiateDBCTLsystemsonthesameMVS imageto avoidcausinganyconfusionbetweensubsystems.
You arerecommendedtohave onlyoneproductionDBCTLinasingle-MVS environment.Normally,thisshouldbelargeenoughto serveallCICSTransaction Server forz/OS,Version2 Release3 systemswithinoneMVSimage.For multiple CICSsystemswithlocalandremoteDL/I,runninginseveralMVS imagesusing IMSdatasharing,countthenumberof DL/Ithreadsneeded.If thesum ofthese threads, plusthenumberof expectedactiveBMPsislessthan255,youshould need onlyoneDBCTLwithoutdatasharing.
You needonelogforeach DBCTL,sobearinmind thatloggingcanbecomemore complexthemoreDBCTLsyouhave.Balancetheneedfor multipleDBCTLs against thelogging proceduresyouwillneed. However,logthroughputtimeshould beimprovedcomparedwithlocalDL/I,becauseDBCTLusesthewriteaheaddata set(WADS), whichcanreducetheelapsedtimeneededfor alogwrite.
Chapter 4. Installing DBCTL, and defining CICS and IMS system resources
This chapterdescribeshowtoinstall DBCTLanddefineCICSandIMSsystem resourcesunderthefollowingsections:
v “ChecklistforinstallingandgeneratingDBCTL”
v “DefiningCICSsystem resourcesforDBCTL”onpage22foraDBCTL
environment,anddescribingtheeffectsonsystemdefinitionsinanexistingDL/I environment
v “GeneratingDBCTL”onpage28,includingsomeexamplesof JCLyoucancopy toprovidea basicDBCTLsubsystem
v “StartingDBCTL, DLISAS,andDBRC”onpage37
v “DefiningtheIMSDRAstartupparametertable”onpage38,includingsome exampleJCL
v “CustomizingDBCTL”onpage42,bymeansofauser-replaceable programand twoglobaluserexits.
Checklist for installing and generating DBCTL
In thischecklist,itisassumedthatyouhavealreadyinstalledCICSTransaction Serverfor z/OS,Version2 Release3 andIMS/ESA6.1or higher,andhavereadthe programdirectoryfor eachproductto checkforanyPTFsorAPARsthatyoumay need, asadvisedintheCICSTransactionServerfor z/OSInstallationGuide.This checklist isanexampletohelpyou developyourown proceduresfor installing DBCTL, dependingontheDBCTLfacilities youwantto use.Whendevelopingyour own checklist,referto theIMSInstallationGuideandtheIMSSystemDefinition Referencemanual manualorIMS/ESAInstallationVolume2:SystemDefinitionand Tailoringfor furtherguidanceonIMSinstallationandsystemdefinition.
CICSsuppliesaDBCTLinstallationverificationprocedure,DFHIVPDB.For more informationabout thisIVP,see theCICSTransactionServerfor z/OSInstallation Guide.
Using DBCTLinsteadof localDL/Isimplifiesinstallation,becauseyoudonothave to performa partialsystem generationofCICStouseDL/I resources.Also,youdo nothave todoapartialsystemgenerationifyouuse remoteDL/I support.
1. PrepareaPDIRthatdoesnot specifyPSBs foranapplicationthatistobe migratedtoDBCTLfortesting. (See“PSBdirectories(PDIRs)”onpage25.) 2. PerformDBCTLstartup.(See“StartingDBCTL, DLISAS,andDBRC”onpage
37.)
3. Updatesystemprocedure libraries;for example,SYS1.PROCLIB, withthe startupproceduresfor DBCTL,DLISAS,DBRC,andtheIRLM(if youareusing it).(ThesestartupproceduresareintheIMS.PROCLIB library.)
4. CheckthatDBCTLhasbeenfullyinstalled,integratedwithMVS,andthatall requiredonlinedata setshavebeen allocatedandinitialized,whereapplicable.
(Forfurtherguidanceondoingthis, seetheIMSInstallationGuide.)
5. PerformanACBgenerationto createmembers oftheIMS.ACBLIB,ifyou have notdone thisalready.
AnACBgenerationshouldhavebeenperformed whenCICSwithlocalDL/I wasmigratedto IMS/ESA3.1orlater.DBCTLcanuseACBsgenerated fora localDL/I (IMS/ESA3.1)environment,butyoushouldnotsimplyinclude
existingACBLIBsintheDBCTLandDLISASJCL.Useapairofnew,separate, ACBLIBs,whichwillenableyou tousetheIMSonlinechange facility.Youcan copythem from,say,CICS.LOCAL.ACBLIBintoa DBCTL.ONLINE.ACBLIBA andDBCTL.ONLINE.ACBLIBBbut,ifyoudothis, beawarethatyoumight copysomeinvalid(thatis,pre-IMS/ESA3.1)ACBs.Toavoidthis, startwith emptyACBLIBAandACBLIBBlibraries,andregenerateACBs asrequired.
6. Ifyouintendtousedynamicallocation, createDFSMDAmembers.(See“IMS dynamicallocation macro(DFSMDA)”onpage36.)
7. StartDBCTL. DBCTLwillissueastartcommandforDLISASandDBRC.This requirestheDLISASandDBRCJCLprocedurestobeinSYS1.PROCLIB.
(See“StartingDBCTL,DLISAS,andDBRC” onpage 37.)
8. TestDBCTL,for examplebyusingtheDBCTLoperatorcommand/DISPLAYto verifythatDBCTLrecognizesthePSBsandDBDsyou definedintheDBCTL generation.(See“Findingoutcurrentstatusof DBCTLactivities” onpage 63.) 9. Checkyourlogarchivingsetupworksbeforedoinganymoretesting.(See
“LogcontrolwithDBRC” onpage34.)Ifit doesnot,theIMSlogsmay eventuallyfillandstallthesystem.
10. Assemblea DRAthatwillenableCICStoconnect toDBCTL.(See“Defining theIMSDRAstartupparametertable”onpage38.)
11. StartCICSandtesttheconnectionto DBCTL,usingtheCDBC transaction.
(See“CDBC transactionforconnect anddisconnect”onpage48.) 12. GenerateaninitializationPLT,sothatCICScanconnect toDBCTL
automaticallyat startuptime. (See“ConnectingDBCTLto CICSautomatically”
onpage 46.)
13. Testtheapplication(s)youdefinedto DBCTL.
14. Setupandtestrecoveryandrestart ofCICSandDBCTL,anddatabase recovery.(SeeChapter6, “RecoveryandrestartoperationsforDBCTL,” on page73.)
Defining CICS system resources for DBCTL
This sectiontellsyouhowto definesystem resourcesforDBCTL.
v “Systeminitializationparameters”
v “PSBdirectories(PDIRs)”onpage25 v “DDstatements” onpage 25
v “CICS-suppliedgroupswithinCICSsystemdefinition”onpage27 v “Logmanagement”onpage27
v “Monitoringcontroltable(MCT)”onpage27 v “Programlist table(PLT)”onpage27 v “Transientdataqueues”onpage 28
System initialization parameters
TheCICSsysteminitialization parameterscontain informationneededto initialize andcontrolsystem functionsandtheinitialization process.Italso containsmodule suffixes toenableyouto choosebetweendifferentversionsof CICSmodulesand tables.You cangenerateseveralSITsandselecttheonethatbestmeetsyour currentrequirementsat initializationtime. Ifyouhavemorethan oneCICSsystem, each canuseadifferentSIT.
Specifying DL/I support in system initialization parameters
In CICSTransactionServerforz/OS, Version2Release3,there isnoDLIsystem initialization parameter.Support forDBCTLisalwayspresent.Support forremote DL/I isincludedif thePDIR=YES|xxkeywordisspecified.
Note: ThedefaultisPDIR=NO, meaningthatbydefaultsupportfor remoteDL/I is notincluded.
SeeCICSSystemDefinitionGuideformoredetails abouttheseparameters.
SeeCICSSystemDefinitionGuideformoredetails abouttheseparameters.