Manuals / IBM / Computer Equipment / Server

IBM SC34-7012-01 manual v Back out recoverable resources

Models: SC34-7012-01

1 268

Page 23

The CICS recovery manager then uses the information retrieved from the system log to:

vBack out recoverable resources.

vRecover changes to terminal resource definitions. (All resource definitions installed at the time of the CICS failure are initially restored from the CICS global catalog.)

A special case of CICS processing following a system failure is covered in Chapter 6, “CICS emergency restart,” on page 61.

Chapter 1. Recovery and restart facilities 11

Page 23

Image 23

IBM SC34-7012-01 manual v Back out recoverable resources

Contents

SC34-7012-01 Recovery and Restart GuideCICS Transaction Server for z/OS Version 4 ReleasePage SC34-7012-01 Recovery and Restart GuideCICS Transaction Server for z/OS Version 4 ReleaseCopyright IBM Corporation 1982 Chapter 2. Resource recovery in CICS ContentsPart 1. CICS recovery and restart concepts Part 2. Recovery and restart processesChapter 8. Unit of work recovery and Part 3. Implementing recovery andChapter 9. Communication error recoveryChapter 18. Backup-while-open BWO Chapter 13. Programming for recoveryChapter 16. Moving recoverable data Chapter 17. Forward recoveryNotices Chapter 19. Disaster recoveryAccessibility Part 4. AppendixesWho should read this book How to use this bookPreface What this book is aboutviii CICS TS for z/OS 4.1 Recovery and Restart Guide Changes in CICS Transaction Server for z/OS, Version 4 Release x CICS TS for z/OS 4.1 Recovery and Restart Guide Part 1. CICS recovery and restart concepts 2 CICS TS for z/OS 4.1 Recovery and Restart Guide Logging changes Chapter 1. Recovery and restart facilitiesMaintaining the integrity of data 4 CICS TS for z/OS 4.1 Recovery and Restart Guide Minimizing the effect of failuresThe role of CICS CICS backward recovery backout Recoverable resourcesEmergency restart backout Dynamic transaction backoutForward recovery of CICS data sets CICS forward recoveryForward recovery for non-VSAM resources Failures that require CICS recovery processingCICS recovery processing following a communication failure XCF/MRO partner failures 10 CICS TS for z/OS 4.1 Recovery and Restart Guide CICS recovery processing following a transaction failureCICS recovery processing following a system failure v Back out recoverable resources 12 CICS TS for z/OS 4.1 Recovery and Restart Guide Shunted units of work Chapter 2. Resource recovery in CICSUnits of work Active and retained states for locks LocksEXEC CICS CREATE TERMINAL Synchronization pointsEXEC CICS CREATE TERMINAL EXEC CICS CREATE CONNECTION COMPLETE EXEC CICS DISCARD CONNECTION EXEC CICS DISCARD TERMINALEXEC CICS DISCARD TERMINAL Examples of synchronization pointsEXEC CICS CREATE CONNECTION COMPLETE EXEC CICS DISCARD CONNECTION CICS recovery manager Figure 3. CICS recovery manager and resources it works with FC/RLSRecovery v Coordinating recoverable conversations to remote nodesCoordinating updates to local resources Managing indoubt units of work Coordinating updates in distributed units of workInformation recorded on the system log Resynchronization after system or connection failureCICS system log User journals and automatic journaling Forward recovery logsSystem activity keypoints Input or output messages from terminals accessed through VTAM 24 CICS TS for z/OS 4.1 Recovery and Restart Guide First quiesce stage Chapter 3. Shutdown and restart recoveryNormal shutdown processing Third quiesce stage Second quiesce stageShunted units of work at shutdown Warm keypointsPERFORM IMMEDIATE not recommended Flushing journal buffersImmediate shutdown processing PERFORM SHUTDOWN IMMEDIATE Shutdown requested by the operating system 30 CICS TS for z/OS 4.1 Recovery and Restart Guide Uncontrolled terminationThe shutdown assist transaction Global catalog Cataloging CICS resourcesLocal catalog Shutdown initiated by CICS log manager Effect of problems with the system logDFHRM0405 How the state of the CICS region is reconstructedDFHRM0402 DFHRM0403 and DFHRM0404About this task Overriding the type of start indicatorWarm restart Emergency restartAn initial start of CICS Recovery of data during an emergency restartCold start Dynamic RLS restart MNPS, multinode persistent sessions Recovery with VTAM persistent sessionsRunning with persistent sessions support SNPS, single-node persistent sessionsSituations in which sessions are not reestablished SET VTAM FORCECLOSE SET VTAM IMMCLOSE SET VTAM CLOSED Running without persistent sessions supportSituations in which VTAM does not retain sessions regions that do have persistent sessions support 42 CICS TS for z/OS 4.1 Recovery and Restart Guide Part 2. Recovery and restart processes 44 CICS TS for z/OS 4.1 Recovery and Restart Guide About this task Chapter 4. CICS cold startStarting CICS with the START=COLD parameter VSAM FilesData tables Temporary storageTransient data Temporary storage data sharing serverLIBRARY resources Resource definitions dynamically installedTransactions Journal names and journal modelsTerminal control resources Committing and cataloging resources installed from the CSDSingle resource install Monitoring and statisticsStarting CICS with the START=INITIAL parameter Installable set installDistributed transaction resources Dump tableinformation saved in the system log from a previous run. The primary and secondary system log streams are purged and CICS begins writing a new system log 52 CICS TS for z/OS 4.1 Recovery and Restart Guide Rebuilding the CICS state after a normal shutdown Chapter 5. CICS warm restartFiles Reconnecting to SMSVSAM for RLS accessData set name blocks Recreating non-RLS retained locksTemporary storage TDINTRA=NOEMPTY the defaultTDINTRA=EMPTY Trigger levels for TERMINAL and SYSTEM onlyPrograms No autoinstall for programsTransactions LIBRARY resourcesMonitoring and statistics Autoinstall for programsStart requests Terminal control resources CSD-defined resource definitionsTCAM and sequential BSAM devices Journal names and journal modelsDistributed transaction resources URIMAP definitions and virtual hostsv Different TCT from last run. CICS installs the TCT only, and does not apply the warm keypoint information, effectively making this a cold start for these devices 60 CICS TS for z/OS 4.1 Recovery and Restart Guide Driving backout processing for in-flight units of work Recovering after a CICS failureRecovering information from the system log Chapter 6. CICS emergency restart62 CICS TS for z/OS 4.1 Recovery and Restart Guide Effect of delayed recovery on PLTPI processingOther backout processing Rebuilding the CICS state after an abnormal terminationTemporary storage Reconnecting to SMSVSAM for RLS accessRLS restart processing and orphan locks Recreating non-RLS retained locksCSD-defined resource definitions 64 CICS TS for z/OS 4.1 Recovery and Restart GuideStart requests Terminal control resourcesTCAM and sequential BSAM devices is successful, but CICS abnormally terminates before the catalog can be updated, CICS recovers the information from the forward recovery records on the system logDistributed transaction resources 66 CICS TS for z/OS 4.1 Recovery and Restart Guide Restrictions Chapter 7. Automatic restart managementCICS ARM processing Before you begin Registering with ARMWaiting for predecessor subsystems De-registering from ARMChapter 7. Automatic restart management Failing to registerARM couple data sets CICS restart JCL and parametersCICS START options Connecting to VTAMWorkload policies Server ARM processing The COVR transactionMessages associated with automatic restart Automatic restart of CICS data-sharing serversServer initialization parameters for ARM support Server commands for ARM supportCANCEL RESTART=NOYES Waiting on events during initializationCommit-failed Chapter 8. Unit of work recovery and abend processingUnit of work recovery In-flight-failedIndoubt-failed Transaction backoutBackout-failed CICS data tables FilesBDAM files and VSAM ESDS files START requests START with recoverable data no PROTECTIntrapartition transient data Auxiliary temporary storageRestart of started transactions START with recoverable data PROTECTSTART with nonrecoverable data no PROTECT START with nonrecoverable data PROTECTEXEC CICS CANCEL requests Basic mapping support BMS messagesAuxiliary temporary storage Backout-failed recoveryDisposition of data sets after backout failures I/O errorTransient data Retrying backout-failed units of workSMSVSAM server failure Open errorLogical delete not performed Coupling facility cache structure failure DFSMSdss non-BWO backup in progressDuplicate key error SMSVSAM server recycle during backoutNone of the above Commit-failed recoveryLock structure full error Files Indoubt failure recoveryAuxiliary temporary storage Investigating an indoubt failureIntrapartition transient data The WAITSTATE of Shunted shows that this UOW has been suspended We can now see that Cache failure support Recovery from failures associated with the coupling facilityAbout this task Lost locks recoveryRebuilding the lock structure Notifying CICS of SMSVSAM restart90 CICS TS for z/OS 4.1 Recovery and Restart Guide Performing lost locks recovery for failed units of workConnection failure to a coupling facility lock structure MVS system recovery and sysplex recoveryConnection failure to a coupling facility cache structure Exit code Transaction abend processingTransaction restart Abnormal termination of a taskProcessing operating system abends and program checks Actions taken at transaction failurev If a match is not found, CICS is terminated 96 CICS TS for z/OS 4.1 Recovery and Restart Guide Terminal error program DFHTEP Chapter 9. Communication error processingTerminal error processing Node error program DFHZNEPIntersystem communication failures Part 3. Implementing recovery and restart 100 CICS TS for z/OS 4.1 Recovery and Restart Guide Application design considerations Chapter 10. Planning aspects of recoveryQuestions relating to recovery requirements Validate the recovery requirements statement About this task Designing the end user’s restart procedureEnd user’s standby procedures Communications between application and userSecurity System definitions for recovery-related functionsSystem recovery table SRT Resource definitions for recoveryProgram list table PLT Documentation and test plansTransient data queues Temporary storage tablev Forecast the exceptional conditions that can be expected System logging recovery purposes onlyForward recovery logging Chapter 11. Defining system and general log streamsGeneral log streams Defining log streams to MVSDefining system log streams System log streamsWith a JOURNALMODEL definition Specifying a JOURNALMODEL resource definitionWithout a JOURNALMODEL definition Model log streams for CICS system logs Recovery considerations2-Way Sysplex About this task Activity keypointingVarying the model log stream name About this task Keeping system log data to a minimumAbout this task Log-tail deletionMoving units of work to the secondary log About this task Writing user-recovery dataAvoiding retention periods on the system log Retrieving user records from the system logAbout this task Defining forward recovery log streamsAbout this task Procedure Long-running transactionsWhat to do next Model log streams for CICS general logsAbout this task Merging data on shared general log streamsDefining the log of logs About this task Log of logs failureReading log streams offline About this taskAbout this task Adjusting local timeEffect of daylight saving time changes Time stamping log and journal recordsOffline utility program, DFHJUP 122 CICS TS for z/OS 4.1 Recovery and Restart Guide RESTARTNOYES Chapter 12. Defining recoverability for CICS-managed resourcesRecovery for transactions Defining transaction recovery attributesACTIONBACKOUTCOMMIT Indoubt options for distributed transactionsSPURGENOYES TPURGENOYESSharing data sets with batch jobs Recovery for filesFile-owning regions and RLS access VSAM filesBackward recovery Basic direct access method BDAMDefining files as recoverable resources Forward recoveryBACKUPTYPEDYNAMIC VSAM files accessed in non-RLS modeRECOVERYALL RECOVERYBACKOUTONLYNONE VSAM files accessed in RLS modeInquiring on recovery attributes LOGNONEUNDOALLOverriding open failures at the XFCNREC global user exit File recovery attribute consistency checking non-RLSBDAM files The CSD data setAbout this task CICS responses to file open requestsBackward recovery Implementing forward recovery with user-written utilitiesImplementing forward recovery with CICS VSAM Recovery MVS/ESA Recovery for intrapartition transient dataPhysical recovery Logical recoveryNo recovery Forward recoveryInput extrapartition data sets Recovery for extrapartition transient dataBackward recovery Using post-initialization PLTPI programsRecovery for temporary storage Output extrapartition data setsGROUPTSRECOV PREFIXDF LOCATIONAUXILIARY RECOVERYYES Recovery for Web servicesConfiguring CICS to support persistent messages Forward recoveryProcedure Defining local queues in a service providerProcedure Results What to do nextPersistent message processing Error processingFor example, your recovery transaction could 140 CICS TS for z/OS 4.1 Recovery and Restart Guide About this task Procedure Chapter 13. Programming for recoveryDesigning applications for recovery Splitting the application into transactions142 CICS TS for z/OS 4.1 Recovery and Restart Guide Example What to do next Relationships between processing unitsProcedure SAA-compatible applicationsProgram design Dividing transactions into units of workPseudoconversational processing Processing dialogs with usersConversational processing Main storage areas CICS recoverable resourcesMechanisms for passing data between transactions User files and DL/I and DB2 databases Designing to avoid transaction deadlocksTemporary storage auxiliary Transient data queuesProcedure Implications of interval control START requestsTerminal paging through BMS Using transient data queuesImplications of automatic task initiation TD trigger level Implications of presenting large amounts of data to the userAbout this task Managing transaction and system failuresTransaction failures About this taskDynamic transaction backout HANDLE ABEND commandsEXEC CICS SYNCPOINT ROLLBACK command Transaction restart after DTB Use of the program error program DFHPEPSystem failures Handling abends and program level abend exitsInformation provided Processing the IOERR conditionCommand Locking enqueuing on resources in application programs START TRANSID commandsPL/I programs and error handling About this task Nonrecoverable filesImplicit locking for files Recoverable files v READ for UPDATE v WRITE v DELETE v WRITEQ TD v READQ TD v DELETEQ TD Implicit enqueuing on logically recoverable TD destinationsImplicit enqueuing on recoverable temporary storage queues Sequential methods HSAM, HISAM, SHISAM Implicit enqueuing on DL/I databases with DBCTLExplicit enqueuing by the application programmer Direct methods HDAM, HIDAMdeadlock Possibility of transaction deadlockAbout this task Where you can add your own codeUser exits for transaction backout Procedure XRCINIT exitXRCINPT exit XFCBFAIL global user exitCoding transaction backout exits XFCLDEL global user exitXFCBOVER global user exit XFCBOUT global user exitAbout this task Chapter 14. Using a program error program PEPThe CICS-supplied PEP ProcedureYour own PEP About this task Omitting the PEPChapter 14. Using a program error program PEP 166 CICS TS for z/OS 4.1 Recovery and Restart Guide About this task Chapter 15. Resolving retained locks on recoverable resourcesQuiescing RLS data sets About this taskIllustration of the quiesce flow across two CICS regions The RLS quiesce and unquiesce functionsChapter 15. Resolving retained locks on recoverable resources Other quiesce interface functions Non-BWO data set backup startForward recovery complete Non-BWO data set backup endBWO backup start BWO backup endQuiesce coupling facility cache available Switching from RLS to non-RLS access modeLost locks recovery complete Exception for read-only operationsWhat can prevent a switch to non-RLS access mode? About this task Resolving retained locks before opening data sets in non-RLS modeInvestigating which retained locks are held and why ProcedureAbout this task INQUIRE DSNAMEINQUIRE UOWDSNFAIL 176 CICS TS for z/OS 4.1 Recovery and Restart Guide SHCDS LIST subcommandsResolving retained locks and preserving data integrity About this task ProcedureAbout this task Choosing data availability over data integrityDFH0BAT2 CEMT command examplesThe batch-enabling sample programs DFH0BAT1NORMAL SET DSNAME’RLS.ACCOUNTS.ESDS.DBASE1’ RETRYSTATUS RESULTS - OVERTYPE TO MODIFY DsnRLS.ACCOUNTS.ESDS.DBASE1Overriding retained locks The PERMITNONRLSUPDATE subcommandThe DENYNONRLSUPDATE subcommand A special case lost locksPost-batch processing Coupling facility data table retained locks About this task Chapter 16. Moving recoverable data sets that have retained locksProcedure for moving a data set with retained locks Using the REPRO methodSHCDS FRBIND SHCDS FRRESETRRSHCDS FRSETRR SHCDS FRUNBINDAbout this task Using the EXPORT and IMPORT functionsChapter 16. Moving recoverable data sets that have retained locks About this task Rebuilding alternate indexesAbout this task Chapter 17. Forward recovery proceduresForward recovery of data sets accessed in RLS mode 5. Restore the backup Recovery of data set with volume still available3. Issue FRSETRR 4. Issue FRUNBIND9. Alter the new data set name Recovery of data set with loss of volume10. Issue the FRBIND subcommand 11. Issue the FRRESETRR subcommandVolume recovery procedure using CFVOL QUIESCE 1. VARY SMS,CFVOLvolser,QUIESCE Example of recovery using data set backup 5. We terminated the SMSVSAM servers using the MVS command INQUIRE UOWDSNFAIL DSNRLSADSW.VF01D.BANKACCT 194 CICS TS for z/OS 4.1 Recovery and Restart GuideThese commands are issued to each CICS AOR that requires access 196 CICS TS for z/OS 4.1 Recovery and Restart Guide Example of recovery using volume backupCatalog recovery 4. Run the forward recovery utility Forward recovery of data sets accessed in non-RLS modeProcedure for failed RLS mode forward recovery operation 3. Restore the backup1. Tidy up any outstanding CICS recovery work, as follows 1 Force shunted indoubt units of work using SET DSNAME Procedure for failed non-RLS mode forward recovery operation 202 CICS TS for z/OS 4.1 Recovery and Restart Guide BWO and concurrent copy Chapter 18. Backup-while-open BWOBWO and backups Previous product BWO requirementsComponent name Full DFSMS/MVS nameVSAM control interval or control area split Hardware requirementsWhich data sets are eligible for BWO TYPECICS Specifying BWO using access method servicesHow you request BWO ResultsAbout this task Specifying BWO on CICS file resource definitionsProcedure Systems administrationRemoving BWO attributes Batch jobsBWO processing Back-level data sets First file opened in non-RLS mode against a clusterFile opening Subsequent files opened when use count is zero Subsequent files opened when use count is not zeroRestriction for VSAM upgrade set File closing non-RLS modeImmediate or uncontrolled shutdown Data set backup and restoreShutdown and restart Controlled shutdownInvalid state changes for BWO attributes VSAM access method servicesNon-SMS managed storage Forward recovery loggingData set restore Data setsForward recovery Recovery point non-RLS modeAbout this task Recovering VSAM spheres with AIXsAn assembler program that calls DFSMS callable services DATEPACK DATETIMEDTTENTHS RECOVPTPLOAD 220 CICS TS for z/OS 4.1 Recovery and Restart GuidePRGCONT BWOFLAGS12,ZEROESEND PROG 222 CICS TS for z/OS 4.1 Recovery and Restart Guide Why have a disaster recovery plan? Chapter 19. Disaster recoveryDisaster recovery testing Tier 1 - physical removal Six tiers of solutions for off-site recoveryTier 0 no off-site data The drawbacks are Tier Tier 2 - physical removal with hot siteTier 3 - electronic vaulting Tier 0-3 solutions Tier 0 Tier 4 - active secondary site230 CICS TS for z/OS 4.1 Recovery and Restart Guide Figure 22. Disaster recovery tier 4 active secondary siteTier 6 - minimal to zero data loss Tier 5 - two-site, two-phase commitFigure 24 summarizes the tier 6 solution Tier 4 Tier 4-6 solutionsPeer-to-peer remote copy PPRC and extended remote copy XRC Disaster recovery and high availabilityUse PPRC for high value transactions Use XRC for high volume transactionsPPRC or XRC? 236 CICS TS for z/OS 4.1 Recovery and Restart Guide Remote Recovery Data FacilityOther benefits of PPRC and XRC Forward recoveryRRDF Choosing between RRDF and 3990-6 solutionsDisaster recovery personnel considerations About this task238 CICS TS for z/OS 4.1 Recovery and Restart Guide Disaster recovery facilitiesMVS system logger recovery support Returning to your primary siteCICS VR shadowing CICS VSAM Recovery QSAM copyRemote Recovery Data Facility support Remote site recovery for RLS-mode data setsFinal summary Copyright IBM Corp. 1982 Part 4. Appendixes242 CICS TS for z/OS 4.1 Recovery and Restart Guide Notices 244 CICS TS for z/OS 4.1 Recovery and Restart Guide TrademarksCICS books for CICS Transaction Server for z/OS Access to CICSAdministration BibliographyGeneral Administration and ManagementCICSPlex SM books for CICS Transaction Server for z/OS Other CICS publicationsAccessibility 248 CICS TS for z/OS 4.1 Recovery and Restart Guide Index A files continued DL/I continuedlocking continued Page CICS Transaction Server for z/OS Version 4 Release Readers’ Comments - Wed Like to Hear from YouRecovery and Restart Guide Publication No. SC34-7012-01 IBM United Kingdom Limited Readers’ Comments - Wed Like to Hear from YouSC34-7012-01 SC34-7012-01Page SC34-7012-01