• Nenhum resultado encontrado

Requirements planning and checklist

This sectionsummarizestherequirements,andthestepsthatyou needtofollow,to setuptheCICSloggingenvironment.Someof thestepslistedhave apointerto sectionsthatprovidemoredetailed information.ThesestepscoverbothMVSand CICSsystem programmertasksandsomesecurityadministrator tasks,andclose cooperation betweenallgroupsisneeded:

Planning

Considerthepossiblestorageoptions,andchoosewhich ofthe3available hardware optionsyouwanttouse:

v Non-volatilecoupling facility,wherelogstreamdataisduplexedinthe MVSloggerdataspace.Non-volatilestorageinvolvestheuseofbattery backuporanuninterruptiblepowersupply(UPS):

Whenusinga UPS,youuseahardware consolecommandtoupdate couplingfacilitystatus

Whenusingbatterybackup, batteriesmustbeonlineandcharged.

v Volatilecouplingfacility,wherelogstreamdataisduplexedtoa staging dataset.

v DASD-only,wherelogstreamdataisduplexedintheMVSloggerdata space.

See“CouplingfacilityorDASD-only?”onpage112,to helpyoudecideonone of theseor acombinationofboth.

As partoftheplanningphase:

v DeterminethenumberCICSregionsthatrequireloggersupportandhence systemlogstreams.

v Determinethenumberof userjournalsandautojournalsthatyourregions use.

v Determinethenumberof forwardrecoverylogs requiredfor VSAMdatasets.

v

Determinewhetheranyuserjournalorforwardrecovery logstreamsareto besharedbetweenregions(tocreatemergeddataautomatically).

Note: Thesystem logstreams,DFHLOGandDFHSHUNT,cannotbe shared.

DASD-onlylogstreams canbesharedonlywithin thesameMVS image.

v Decideonthenumberandsizes ofthecouplingfacilitiestobeused.

v Determinethelogstreamsizes:

Forcouplingfacilitylogstreams, see“Couplingfacilitylogstreams” on page113.

ForDASD-onlylogstreams,see “DASD-onlylogstreams” onpage 129.

For informationabouttypesof couplingfacility,seethez/OSMVSSettingUpa Sysplex.NotethattheminimumlevelofcouplingfacilitysupportedbytheMVS system loggerisCFLEVEL=1,withtheappropriateservicelevelof thecoupling facilitycontrolcodethatsupports CFLEVEL=1.

Maintenance

Ensure thatallmaintenanceaffecting theMVS systemlogger,andtheCICSlog manageranditsutilities,isapplied:

v LoggerserviceabilityAPARsrelatingto theMVSsystemloggerareidentified withtheLOGRSERVICEkeyword.

v

APARsrelatingtotheCICSlogmanagerareidentifiedwiththeCICSLOGR keyword.

Run DFHLSCU

If youaremigratingfromCICSVersion3orVersion4,runthislogstreamsizing utilityusingoneormore CICSjournaldatasets asinput:

v UseCICSjournaldatasets takenfromperiodsof heavyproductionuse.

v Ineach runof DFHLSCU,useonlyjournaldatasets thatareto bemigrated tothesameMVSlogstream

See“Thelogstreamsizing utility,DFHLSCU”onpage122for moreinformation.

Createandformatthe LOGRcoupledatasets In consultationwithyourMVS systemprogrammer:

v

UseMVS utilityIXCL1DSUto createandformat theprimaryandalternate LOGRcoupledatasets.

v IdentifytheLOGRcoupledatasets tothesysplexintheCOUPLExxmember inSYS1.PARMLIB

v MaketheLOGR coupledatasetavailabletothesysplex.

See“FormattheLOGR CoupleDataSetandMakeitAvailable totheSysplex”

inthez/OSMVSSettingUpaSysplex manualforinformationabout these steps.

106 CICSTSforz/OS: InstallationGuide

Notes:

1. For thistaskyou needknowthenumberof logstreamsand,forcoupling facilitylogstreams,thenumberofstructures.EachCICSregionneedstwo system logstreamsand,optionally:

v Alogstreamforthelogoflogs

v Oneormorelogstreams forforwardrecoverylogs v

Oneormorelogstreams forautojournals v Oneormorelogstreams foruserjournals

2. If youaremigratingfromareleaseof OS/390,beforerelease3,(to meet thez/OSminimumrequirementlevelforCICSTS),youwillneedto reformatyourLOGR datasets,becauseloggingenhancementsintroduced inOS/390Release3requiredLOGRcoupledatasetof thesysplexto be formatted usingOS/390Release3orlater.

Theremovalof the168data setlimit(describedin“Generallogs”onpage 137)also requirestheLOGRdatasettobeformattedwith

DSEXTENT(nnnnn).ThisdoesnotapplytoLOGR coupledatasets formatted forDASD-onlylogging.

Definecoupling facilitystructures

If youareusingthecouplingfacilityfor someor allof yourlogstreams,update yourCFRM policyandyourLOGRcoupledata setwiththerequiredstructure definitions.

See“Definingcouplingfacilitystructures”onpage 114fordetails,includinga sample job.

Establishtherequiredsecurity authorizations

Ensure thatalltheuserids thatareinvolvedwithrunningthesystem logger,or defining oraccessingloggerresources,areauthorized,andthattherequired profiles aredefinedintheLOGSTRMgeneralresourceclass:

v IftheMVSsystem loggeraddress space(IXGLOGR) isnotgivenSAF privilegedortrustedstatus,ensureyougivetherequiredauthorizationtothe useridthatruns IXGLOGR.Forexample,if theuseridthatrunsIXGLOGR (definedintheRACFstartedprocedurestable(ICHRIN03),or definedinthe RACFSTARTEDclassprofile)isSYSTASK:

SYSTASKrequiresALTERaccessto IXLSTRstructureprofiles inthe FACILITYgeneralresourceclassfor accessto logstreamcouplingfacility structures.

SYSTASKrequiresALTERaccessto thedatasetprofiles

(hlq.data_set_name)intheDATASETgeneralresourceclass,for each DASDlogstreamandstagingdataset.

v TousetheMVSsystemloggerIXCMIAPUutilityto define,updateanddelete entriesintheLOGR coupledataset,youneedappropriateauthorizationsto therelevantRACFprofilesintheLOGSTRMandFACILITYgeneralresource classes.See“Authorizationsfor usersof IXCMIAPU”onpage34for

informationandexamplesofhow todothis.

v ToenableCICSto createlogstreamsdynamically, andtowritetolog streams,ensurethattheCICSregionuseridhastherequiredauthorizations.

See“Authorizationsfor CICSregions”onpage34forinformationand examplesofhow todothis.

For moreinformationaboutauthorizationsfor thesystemlogger,seethez/OS MVS SettingUpa Sysplexmanual

Checksysplexdefinition inPARMLIB

TousetheMVS systemlogger,eachMVS imagemust bea memberofa sysplex.Ensure yoursysplexdefinition,inPARMLIBmemberIEASYSxx, specifies eitherPLEXCFG(MONOPLEX),fora single-membersysplex,or PLEXCFG(MULTISYSTEM), foramulti-member sysplex.Alsoensurethatyou defineaCOUPLExxmemberinPARMLIB.

Note: Thevaluespecified ontheSYSPLEXparameterinCOUPLExxforms partofDASD-onlyandstagingdatasetnames.

Activate theLOGRsubsystem

Ensure theLOGRsubsystemisactiveto enabletheCICSlogmanagerbatch utility, DFHJUP,toformat andprintlogdata.TheLOGR susbsystemisdefined bythefollowingentryinIEFSSNxxPARMLIBmember:

SUBSYS SUBNAME(LOGR) INITRTN(IXGSSINT) Planstagingdatasetrequirements

Stagingdatasets areused forbothDASD-onlyandcouplingfacilitylog streams, andifspecifiedaredynamicallyallocatedbytheMVS systemlogger:

v ForDASD-onlylogstreams, stagingdatasetsaretheprimary(interim) storage.

v Forcouplingfacilitylogstreams,stagingdatasets areallocatedbythe systemloggertosafeguardlogdataintheeventofthelogdatabeingina volatileconfiguration;thatis:

Thereisalossof thecouplingfacilitybatterybackup

Astructurefailurethatresultsintheonly copyof logdatabeinginMVS localstoragebuffers.

Considerthefollowingparameters:

v STG_DUPLEX(YES)andDUPLEXMODE(COND)to causethesystemlogger tousestaging datasetsif thecouplingfacilityisnotfailureindependent(see

“Stagingdatasetsfor couplingfacilitylogstreams”onpage128formore information)

v

STG_MGMTCLAStospecifytheSystemManaged Storage(SMS)

managementclassto beused forstagingdata setallocation(validonly when STG_DUPLEX(YES)orDASDONLY(YES)isspecified)

v STG_STORCLASto specifytheSMS storageclass tobeusedfor staging datasetallocation(validonlywhenSTG_DUPLEX(YES)or

DASDONLY(YES)isspecified)

v STG_SIZEto specifythesizeofstagingdatasets

v SHAREOPTIONS(3,3)forlogstreamdatasetsandstagingdata sets(see

“VSAMShareOptionsforSystemLogger”inz/OSMVS SettingUp a Sysplex)

PlanDASDspace andSMS environmentforloggersecondarystorage Systemloggersecondarystoragecomprisesalllogstream(offload)datasets.

See“Managingsecondarystorage”onpage 136for informationaboutsize parametersandotherattributesrelatingtosecondarystorage

Definelog streamsandlogstreammodels

Define thespecificlogstreams, andlogstreammodelsfor dynamiccreationof logstreams, intheLOGR policy.

In particular,considerthefollowingwhendefiningyour logstreams:

108 CICSTSforz/OS: InstallationGuide

v SetHIGHOFFLOADnohigherthan80%toallowtheoffloadfunctiontobe activatedbeforestructuresreachthe90%levelandprovideabufferto enableCICSto continuewriting recordswithoutfillingthelogstreambefore offloadcompletes.

v SetLOWOFFLOADforDFHLOG andDFHSHUNTintherange40–60%.

Foruserjournals andthelogof logs,specifyLOWOFFLOADas0.

v SpecifyHLQforthehighlevelqualifierfor offloaddatasets—itisnotpartof theCICSlogstreamname.ThedefaultisIXGLOGR.

v

SpecifySTG_DUPLEX(YES)andDUPLEXMODE(COND)forlogstreamsin thecouplingfacilitytoensurethatstagingdatasets areused automaticallyif thecouplingfacilityisvolatileor failuredependent.

v SetSTG_SIZE tocontrolthesize,in4Kblocks,ofstaging datasets

allocatedbythesystem logger.Forcouplingfacilitylogstreams, thestaging datasetmusthold atleastasmuchdataasthelogstreaminthestructure, sothatoffloadsarenottriggeredbythestagingdatasets.SeeThelog streamsizingutility,DFHLSCUonpages122and133(forDASD-only).

v SpecifyLS_DATACLASandLS_SIZE,for theSMSdataclassandthe numberof4Kallocationblocks respectivelyforlogstreamoffload datasets (see“Managinglogdatasets”onpage136)

v

SpecifyMODEL(YES)toindicatethatalogstreamdefinitionisamodelonly andnotanactuallogstream.SeeSDFHINSTmembersDFHILG2 (coupling facility)andDFHILG5(DASD-only)for samplesofmodellogstreams.

Note: UseAUTODELETE(YES)withasuitableretentionperiod(RETPD)for generallogsbutnotforCICSsystemlogs (DFHLOGandDFHSHUNT).

See“Definingcouplingfacilitylogstreams”onpage118forsomesample IXCMIAPU jobs,andseez/OS MVSSettingUpaSysplexfor general informationabout updatingLOGR policies.

DefineJOURNALMODELresourcedefinitions

Define JOURNALMODELresourcedefinitions intheCICSCSDto enableCICS to mapCICSjournalnamesto MVSsystem loggerlogstreamnames.Seethe CICSResourceDefinition Guidefor informationaboutJOURNALMODEL resource definitions.

Remove JCTdefinitions

WhenmigratingaCICSregionfromaCICS/ESA4.1region(orearlier),remove allreferencestojournalcontroltables(JCTs), andanyDDstatementsfor CICS journaldatasets,fromstartupJCL.

SeetheCICSTransactionServerforz/OSMigrationfromCICSTSVersion2.2 for CICSTSVersion1 Releases1and2 forinformationaboutobsolete

parametersandfunctionrelatingto theoldCICSjournalcontrolfunction and othermigrationinformation

ReviewAKPFREQ systeminitialization parameter

WhenmigratingaCICSregionfromaCICS/ESA4.1region(orearlier),review thevaluespecifiedforAKPFREQ.

This parameternowrepresentsthenumberof writeoperations(logrecords)by CICSlogmanagerto thelogstreambufferbeforeanactivitykeypointistaken, whereasundertheoldjournalcontrolprogramit specifiesthenumberof consecutiveblocks writtentothesystemlogdata set.

Theparameterhasa significantimpactonthesizeof systemloggerprimary (interim)storage,affecting thelogtailmanagement thattakesplaceduring activitykeypoint(AKP)processing.Thesystemlogger:

v Deletesrecordsthatarenolongerof interesttoCICS

v MovesrecordstoDFHSHUNTfor thosetasksthatwrotelogrecordswithin thelastACP.

UpdateJCLofbatchjobs

WhenmigratingaCICSregionfromaCICS/ESA4.1region(or earlier),update DFHJUPbatchjobJCL.Toprocesslogstreams, thesejobs requirethe

SUSBSYSkeywordonDDstatementforthelogstreambeingprocessed.

Evaluateresultsafterimplementation

Afteryouhave implementedthestepsnecessarytouse theMVS systemlogger for CICSlogstreamsandjournals,evaluatetheresultsona continualbasis.

Thefollowingareaidsthatyoucan use:

v CICSintervalstatistics.Youcancollect theseat specifiedintervalsand end-of-dayto obtainCICSlogmanagerstatistics.Youcanalsocollect statisticsusingtheDFH0STATsampleprogram.

v SMFType 88records.Theseareproduced bytheMVS systemlogger,and canbeprintedusingIXGRPT1,which issuppliedinSYS1.SAMPLIB.You canalsoprinttheserecordsusingIXGRPT1JandIXGRPT1L.

Thefollowingsectionsprovidemoredetailed informationtohelp youwiththeabove steps:

v “CouplingfacilityorDASD-only?”onpage112

v “Couplingfacilitylogstreams” onpage 113,whichcontains:

“Definingcouplingfacilitystructures”onpage114

“Planningconsiderationsfor thenumberof logstructures”onpage117 – “Logstructurenamingconventions”onpage 118

“Definingcouplingfacilitylogstreams”onpage118

“Sizingconsiderations forcouplingfacilitylogstreams”onpage 120 – “Couplingfacilityrequirements inanRLSenvironment”onpage127 – “Stagingdata setsforcouplingfacilitylogstreams”onpage 128.

v “DASD-onlylogstreams”onpage129,whichcontains:

“DefiningDASD-onlylogstreams”onpage 130

“Sizingconsiderations forDASD-onlylogstreams”onpage131

“ConvertingaDASD-onlylogstreamtouse acouplingfacility”onpage134.

v “Managingsecondarystorage”onpage136.