48
IBM Software Columbus and Detroit IMS User Group © 2013 IBM Corporation IMS Recovery Solution Pack for z/OS How it works and How to use it Raquel Carvallo IMS Tools – Technical Sales and Support [email protected]

Recovery Solution Pack - IMS RUG March 2013 Columbus

  • Upload
    ibm-ims

  • View
    187

  • Download
    2

Embed Size (px)

Citation preview

Page 1: Recovery Solution Pack - IMS RUG March 2013 Columbus

IBM Software

Columbus and Detroit IMS User Group

© 2013 IBM Corporation

IMS Recovery Solution Pack for z/OS

How it works and How to use it

Raquel CarvalloIMS Tools – Technical Sales and [email protected]

Page 2: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation2

Agenda

IMS Recovery Solution Pack for z/OS Description IMS Database Recovery Facility for z/OS IMS Database Recovery Facility Extended Functions for z/OS IMS High Performance Change Accumulation Utility for z/OS

IMS High Performance Image Copy for z/OS IMS Index Builder for z/OS

Page 3: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation3

IMS Recovery Solution Pack

IMS Tools Knowledge Base Optional report repository for other tools Required by IMS Database Recovery Facility Extended Functions ISPF interface to access output

IMS Database Recovery Facility Extended Functions Provides functions to help maintain recoverability of databases Generates DRF recovery JCL from Recovery Point ID (RPID)

dataset Mostly batch jobs ISPF edit macro in RPID dataset

IMS Database Recovery Facility Batch job actually performs recovery

Page 4: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation4

IBM IMS Database Recovery Facility for z/OS

Page 5: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation5

IMS Database Recovery Facility for z/OS

IMS Database Recovery Facility (DRF) allows you to simultaneously recover multiple database data sets and Fast Path areas in an IMS DBCTL or DB/TM environment Operational Requirements:

Runs as an authorized program in supervisor state IMS DRF recovery assets must be registered with

DBRC ie; DBDS, LOGS, CA & IC data sets

Refer to the User Guide for these requirements

Page 6: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation6

IMS Database Recovery Facility for z/OS

Integrated with other IMS Tools products→ IMS High Performance Image Copy

→ Create new IC of recovered DB→ Create incremental IC of prior IC and logs/CA

→ DB not touched→ IMS High Performance Pointer Checker/IMS HP FP Utilities

→ Hash check recovered DB→ IMS Index Builder / DFSPREC0

→ Rebuild indices instead of recovering→ IMS Library Integrity Utility

→ Ensure correct DBD is used in recovery→ One step processing for all utilities instead of one step for each → Block of data is read once and shared among all utilities

Page 7: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation7

Database Copy Generation→Create copies of DB data sets without accessing production copies→ Input is prior IC + logs / CA→Copies can be created to any point in time

Incremental Image Copy

→Create a new image copy using a prior IC + logs / CA → Production DB is not accessed

→ IC is either batch or concurrent, depending on state of DB→ IC can be created to any point in time→Requires IMS High Performance Image Copy

Allocate/Open Option on START VERIFY→Logical and physical validation of data set availability prior to

running the actual recovery job

IMS Database Recovery Facility for z/OS

Page 8: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation8

Database Recovery Facility Architecture

Components BPE (base primitive environment)

Common system service base upon which provides services such as tracing, message formatting, parsing, storage management, sub-dispatching, and serialization

IMS DRF master address space (MAS) The address space in which the controlling components of

DRF reside and the log and change accumulation data sets are read

IMS DRF recovery sort subordinate subspace (RSS) These address spaces sort log and change

accumulation data and restores image copy data Invoked by MAS

Page 9: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation9

Database Recovery Facility Architecture

IMS DRF master address space (MAS)Integrated Auxiliary Utilities (IAU) or Utility Address Space (UASs)

IMS High Performance Image Copy to create image copiesIMS Index Builder to rebuild index data setsIMS High Performance Pointer Checker and the IMS High Performance Fast Path Utilities to validate database consistencyIMS HALDB DFSPREC0 to rebuild a HALDB Primary Index data set and Index List data setIMS Library Integrity Utility to verify that the DBD used for the recovery is the same as the one that was used to create the

database (optional)

Page 10: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation10

The IBM IMS Tools Recovery Solution

Start Options

JCLJCL

Recon

Master Address Space

Recovery Sort SubspacesControl Function

DBRC

Log and CA read

Log

IC

DBDS

AreaData Set Restore

SortSub AS

Data Set Restore

Sort

Report

IB/DFSPREC0 Utility Address Space

IB or DFSPREC0

HPPC, DEDB PC HPIC

IC

Build primary and secondary index data sets during

the recovery process

Rebuild post recovery phase

Hash check pointer validation run

as part of recovery processing

Block by block pointer check, not

post processed

Produce image copies as part of recovery processing

Image copies are registered with DBRC

Block by block image copies

Page 11: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation11

IMS DRF Recovery Flow Read log data sets first

Read change accumulation datasets concurrently with log data sets

Sort recovery required contents of log records

Update image copy data with log and change accumulation data in a single pass Standard IC changes applied as data is read IC2 data is restored, only updated records are read

Index Builder or DFSPREC0 processing is invoked only after database recovery is complete because the entire database is required in order to rebuild the indexes or ILDSs. This processing cannot occur while the individual database data sets are being recovered.

Page 12: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation12

IMS Database Recovery Facility

Initiating Database Recovery Facility as a batch job

Create and submit JCL

JCL will point to Master Address Space (MAS)

MAS will invoke RSS and IAUs

Specify DRF control statements //SYSIN DD statement

If you use //SYSIN DD * control statements must follow

You may also specify //SYSIN DD DSN=data.set.name to indicate control statements are to be read from a sequential file or PDS member

Page 13: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation13

IMS Database Recovery Facility

JCL requirements

EXEC PGM=FRXSDR00,PARM=DRF The program that starts the Main address space PARM=DRF Identifies this program to the BPE

system service base used by IMS Database Recovery Facility

DRF is the only positional parm and must be listed first

Page 14: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation14

IMS Database Recovery Facility Parms

BPECFG=nnnnnnnn Points to BPE configuration member

DRFMBR=nn Points to suffix of FRXDRF member containing

environmental defaults DRFPROC=nnnnnnnn

Points to the Recovery Sort Subspace (RSS)

Example: PARM=('DRF,BPECFG=FRXBPECF,DRFMBR=ZZ,

DRFPROC=FRXJCLSB'

Page 15: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation15

IMS Database Recovery Facility JCL

//FRXMAST PROC RGN=500M,FRXPROC='TIMSVS.PROCLIB'

//STEP1 EXEC PGM=FRXSDR00, The program that starts the IMS DRF

master address space

// PARM=('DRF,BPECFG=FRXBPECF, DRF identifies itself to BPE

// DRFMBR=ZZ, Suffix of FRXDRFXX PROCLIB member that contains

environmental control statements

// 'GSGNAME=,'),DRFPROC=FRXJCLSB', Use this parameter to specify the name

of the procedure used to initiate the DRF Recovery Sort Subspace (RSS)

// REGION=&RGN,TIME=1440

//STEPLIB DD DSN=&SFRXLOAD,DISP=SHR

//IMS DD DSN=&DBDLIB,DISP=SHR

// DD DSN=&PSBLIB,DISP=SHR

//PROCLIB DD DSN=&FRXPROC,DISP=SHR

//DFSRESLB DD DSN=&IMSRES,DISP=SHR

Page 16: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation16

your.PROCLIB(FRXMAS)

//*****************************************************************

//* SOLUTION: IMS RECOVERY SOLUTION PACK FOR Z/OS *

//* TOOL: IMS DATABASE RECOVERY FACILITY *

//* DESC: SAMPLE JCL PROCEDURE FOR EXECUTING THE *

//* DRF MASTER ADDRESS SPACE *

//* SOURCE: SFRXSAMP(FRXMAS) *

//*****************************************************************

//FRXMAST PROC RGN=500M,FRXPROC='TIMS.PROCLIB'

//STEP1 EXEC PGM=FRXSDR00,

// PARM=('DRF,BPECFG=FRXBPECF,DRFMBR=ZZ,DRFPROC=FRXJCLSB',

// 'GSGNAME=,'),

// REGION=&RGN,TIME=1440

//STEPLIB DD DSN=&SFRXLOAD,DISP=SHR

// DD DSN=&COMPLIB,DISP=SHR

// DD DSN=&IMSRES,DISP=SHR

//IMS DD DSN=&DBDLIB,DISP=SHR

// DD DSN=&PSBLIB,DISP=SHR

//PROCLIB DD DSN=&FRXPROC,DISP=SHR

//IMSDALIB DD DSN=&IMSDALIB,DISP=SHR

//DFSRESLB DD DSN=&COMPLIB,DISP=SHR

// DD DSN=&IMSRES,DISP=SHR

//DFSVSAMP DD DSN=TIMS.PROCLIB,DISP=SHR

Page 17: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation17

your.PROCLIB(FRXJCLIP)

//*****************************************************************

//* SOLUTION: IMS RECOVERY SOLUTION PACK FOR Z/OS *

//* TOOL: IMS DATABASE RECOVERY FACILITY *

//* DESC: UTILITY ADDRESS SPACE JCL FOR IMS INDEX BUILDER AND *

//* THE DFSPREC0 UTILITY. SPECIFIED USING DRFIAX= PARM *

//* IT MUST MATCH THE NAME SPECIFIED ON THE *

//* "DRFIAX(name)" PARM IN THE DRF JOB. *

//* SOURCE: SFRXSAMP(FRXJCLIP) *

//* *

//*****************************************************************

//FRXJCLIP PROC RGN=500M,

// BPECFG='FRXBPECF,

// SFRXLOAD='SPPT.IBMTOOLS.LOADLIB'

//STEP1 EXEC PGM=FRXSDR10,PARM='DRF,BPECFG=&BPECFG',

// REGION=&RGN,TIME=1440

//STEPLIB DD DSN=&SFRXLOAD,DISP=SHR

Page 18: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation18

your.PROCLIB(FRXJCLSB)

//*****************************************************************

//* SOLUTION: IMS RECOVERY SOLUTION PACK FOR Z/OS *

//* TOOL: IMS DATABASE RECOVERY FACILITY *

//* DESC: SUBORDINATE SORT ADDRESS SPACE PROC. *

//* THE NAME OF THIS PROC MUST MATCH THE *

//* "DRFPROC(name)" PARM IN THE FRXMAS PROC. *

//* SOURCE: SFRXSAMP(FRXJCLSB) *

//* *

//*****************************************************************

//FRXJCLSB PROC RGN=500M,

// SFRXLOAD='SPPT.IBMTOOLS.LOADLIB',

// BPECFG=FRXBPECF

//STEP1 EXEC PGM=FRXSDR00,

// PARM='DRF,BPECFG=&BPECFG',

// REGION=&RGN,TIME=1440

//STEPLIB DD DSN=&SFRXLOAD,DISP=SHR

Page 19: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation19

your.PROCLIB(FRXBPECF)

#******************************************************************

# SOLUTION: IMS RECOVERY SOLUTION PACK FOR Z/OS *

# TOOL: IMS DATABASE RECOVERY FACILITY *

# DESC: SAMPLE CONFIGURATION FILE FOR BPE *

# SOURCE: SFRXSAMP(FRXBPECF) *

# *

#******************************************************************

LANG=ENU /* LANGUAGE FOR MESSAGES */

/* (ENU = U.S. ENGLISH) */

#

# DEFINITIONS FOR BPE SYSTEM TRACES

#

TRCLEV=(STG,HIGH,BPE) /* STORAGE TRACE */

TRCLEV=(CBS,HIGH,BPE) /* CONTROL BLK SRVCS TRACE */

TRCLEV=(DISP,HIGH,BPE) /* DISPATCHER TRACE */

TRCLEV=(AWE,HIGH,BPE) /* AWE SERVER TRACE */

TRCLEV=(LATC,HIGH,BPE) /* LATCH TRACE */

TRCLEV=(SSRV,HIGH,BPE) /* SYSTEM SERVICES TRACE */

TRCLEV=(DRF,HIGH,DRF) /* DRF STRUCTURED TRACE */

Page 20: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation20

your.PROCLIB(FRXDRFZZ)

OPTIONS

READNUM(5,30)

SORTPARM(NUM(5),HIPRMAX(OPTIMAL),MAINSIZE(30),-

ASPREF(AS),AVGRLEN(256),FILSZ(210000))

SPSIZE(1024)

UTILGBL (IBPREF(IB),PRPREF(PR),PCJOBNM(PC))

Page 21: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation21

SYSIN will contain two types of control statements

Environmental

Default parameters contained in FRXDRFxx member Statements set in FRXDRFxx override system defaults Parameters in both FRXDRFxx and SYSIN

SYSIN overrides value from FRXDRFxx

Batch Recovery Control Statements

Controls the recovery performed by DRF Must begin with ADD, REMOVE or START

DRF SYSIN Control Cards

Page 22: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation22

DB Recovery Options

Recover to Production Recover to Copy Recover to both Production and Copy Recover to Image Copy

Incremental Image Copy Batch Incremental Image Copy

Automatic Delete/Define of Database Data Sets Allocate/Open Data Sets with START VERIFY Issue /DBR DB and /STA DB in Batch Mode

Database Recovery Facility

Page 23: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation23

IMS Database Recovery Facility

//FULL EXEC FRXMASTR

//SYSIN DD *

READNUM(3,10)

SORTPARM(NUM(10),HIPRMAX(OPTIMAL),MAINSIZE(100), -

ASPREF(IMTA), -

AVGRLEN(1024))

SPSIZE(1024)

OUTPUT(DUP)

REPORT(RPTTYPE=SEP,DRFUNIT=SYSDA,DRFHLQ=SYSD)

DBDSN101(%S(DUP))

DBDSL101(DISP(NEW),STGC(DASD))

ADD DB(IVPDB1,IVPDB1I) DBATRB(DBDSL(101),DBDSN(101))

START ERROR(STOP)

/*

GREEN = Environmental Control Statements

RED = Recovery Control Statements

Page 24: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation24

IMS Database Recovery Facility

READNUM(3,10) Maximum number of log read tasks that are started in parallel for

tape only and the total number of concurrent read tasks

SORTPARM(NUM(10),HIPRMAX(OPTIMAL),MAINSIZE(100), -

ASPREF(IMTA), First 4 chars of Recovery sort subspaces (RSS)

AVGRLEN(1024)) Average record length of records to be sorted

SPSIZE(1024) MB size of dataspaces default is 1024

OUTPUT(DUP)

REPORT(RPTTYPE=SEP,DRFUNIT=SYSDA,DRFHLQ=SYSD)

DBDSN101(%S(DUP))

DBDSL101(DISP(NEW),STGC(DASD))

Remember these are environmental statements

Page 25: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation25

OUTPUT Processing Control Statements

OUTPUT(PRO) Recover to production database Requires the database to be offline prior to initiating recovery

OUTPUT(DUP) Recover to copy of database Database does not have to be off-line during recovery Input to recovery is image copy, change accumulation & logs Output is a set of data sets with different names from production Output data sets are not registered with DBRC

OUTPUT(BOTH) Performs both PRO and DUP Creates two copies of database

Database Recovery Facility Output Options

Page 26: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation26

Database Recovery Facility Output Options

OUTPUT Processing Control Statement (cont)

OUTPUT(ICR) Recover to image copy of database Database does not have to be offline during recovery

IC registered as batch if offline; olic if online Input to recovery is IC, change accum and log data sets Output is a set of image copy data sets

OUTPUT(ICRCA) This option is like ICR, but it specifies that only a BATCH image copy is to be generated using only a prior image copy and a change accumulation as input

Log input is ignored

Page 27: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation27

IMS DRF Control Statements

//FULL EXEC FRXMASTR

//SYSIN DD *

READNUM(3,10)

SORTPARM(NUM(10),HIPRMAX(OPTIMAL),MAINSIZE(100), -

ASPREF(IMTA), -

AVGRLEN(1024))

SPSIZE(1024)

OUTPUT(DUP)

REPORT(RPTTYPE=SEP,DRFUNIT=SYSDA,DRFHLQ=SYSD)

DBDSN101(%S(DUP))

DBDSL101(DISP(NEW),STGC(DASD))

ADD DB(IVPDB1,IVPDB1I) DBATRB(DBDSL(101),DBDSN(101))

START ERROR(STOP)

/*

RED = Recovery Control Statements

Page 28: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation28

Recovery Control Statements

ADD DB ( dbname )

DBDS ( dbname ddname )

AREA ( dbname areaname )

DBDSGRP ( groupname )

CAGRP ( groupname )

RECOVGRP

There is no practical limit to the number of ADD commands that you can

specify except for that which is limited by your environment

Only one Recovery List created regardless of number of ADD statements

IMS DRF Control Statements

Page 29: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation29

START command initiates recovery processing

Some Keywords Available on Start command

VERIFY – LIST, ALLOC and OPEN

ERROR – CONT or STOP

RCVTIME – timestamp* & TSR, PITR or PITCA

• Perform a timestamp recovery - RCVTIME(timestamp,TSR)

• Perform a point in time recovery - RCVTIME(timestamp,PITR)

• Perform a point in time recovery using a point in time change accumulation data set -RCVTIME(timestamp,PITCA)

RCVTYPE – LASTIC, LASTPITCA

*Refer to manual for timestamp considerations

IMS DRF Control Statements

Page 30: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation30

Recovery Control Statements

ADD DB ( dbname ) DBATRB(DBDSL(mmm),DBDSN(nnn) )

The DATRB parameter allows you to specify the the DBDSLmmm and

DBDSNnnn data set characteristics to be used for allocating new database

datasets. The parameters that follow DBATRB; DBDSL and DBDSN identify

the DBDSLmmm and DBDSNnnn parameters in the environmental control

statement parameters to use for the ADD command for recover to copy.

NOTE:

If OUTPUT(PRO) is specified the DBATRB(DBDSN(nnn)) parameter is ignored the name of the existing

production database data set cannot be changed

IMS DRF Control Statements

Page 31: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation31

DRF Recover to Copy Example

The following set of control cards creates a duplicate data base from the 'mydb' data base

DBDSL001(DISP(NEW), - create a new set of data sets STGC(mystgcls), - use the SMS storage class PRIA(200), - primary space allocation override SECA(30)) - secondary space allocation

overrideDBDSN001('MYCOPY') - new high level qualifierOUTPUT(DUP) - this is a recovery to copy onlyADD DB(mydb) DBATRB(DBDSL(001) DBDSN(001))START ERROR(CONT) RCVTIME('200801190300')

Page 32: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation32

DRF Integrated Auxiliary Utility

HP Pointer Checker Keywords

ADD DB(mydbname) PC( {T2CHK(t2len,t2num),

DIAG(NO|YES),

DUMPFORM(UNFORMAT|FORMAT),

PRINTDATA(NO|YES)

INTERVAL(DATASET|BITMAP|(BLOCK,nn)),

RUNTM(YES|NO),

INTST(YES|NO),

BITMAP(YES|NO),

FSEMAP(YES|NO),

MAXFSD(YES|NO),

INTFS(YES|NO,

OVERFLOW(ddnameFromDBD),

PRIMEDB(dbdname)

FABASNAP(YES|NO)} )

Page 33: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation33

Index Builder and DFSPREC0 Keywords

ADD DB(mydbname) IB(BLD_PRIMARY|BLD_SECONDARY, HALDB(BOTH,INDEX,ILE), {INPUT=({IBSCAN,DBRC=Y|N}), NDXIOBUF=({DATA=n,INDEX=n}), SORTE35=NO|YES, SORTFSZ=nnnnnnnnn, SORTID=(sort-id,{sort-parm}), SORTOPT=(sortopt,<<--), SORTOUT=COPY|NOCOPY, SORTSTAT=NO,YES} )

DRF Integrated Auxiliary Utility

Page 34: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation34

Image Copy Keywords

ADD DB(mydbname) IC ( {COMP(N|Y),

COMPTRN(routine),

DBBUF(nnnn),

DSN(name-expression),DSN2(name-expression),

EXPDT(yyyyddd|yyddd),

ICBUFF(nnnn),ICCAT(Y|N),

ICHLQ(hlq1[,hlq2]),ICHLQ2(hlq2),

SPACE({{CYL,TRK,blk},primary,secondary,RLSE…….

STORCLAS(stor-class-name),

UNIT(unitname[,unitcount]),

VOLCNT(nnn),

VOLSER(volser[,volser2]),VOLSER2(volser[,volser2]),

WAITTIME(nnnn),

WAITMSG(N|Y)} )

DRF Integrated Auxiliary Utility

Page 35: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation35

Database Recovery Facility /DBR or /STA in Batch Mode

Issue /DBR DB in Batch Mode

Uses the IMS Tools Online System Interface (TOSI) /DBR DB options

– Can take databases off-line locally to an IMS prior to recovery ADD DB(MYDB) DBR or STA(LOCAL(imsid))

– Can take databases off-line globally on all IMS in the IMSPLEX prior to recovery ADD DB(MYDB) DBR or STA(GLOBAL)

– Does not take databases off-line prior to recovery This is the default ADD DB(MYDB) DBR or STA(NONE)

Page 36: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation36

Database Recovery Facility - Summary

Creation of image copy data sets during the recovery process Creation of index data sets during the recovery process, including

primary, secondary, and HALDB index list data sets Creation of off-line, cloned copies of the database Validation of data during the recovery process Automatic deletion and creation of database data sets during the

recovery process The ability to generate new image copy data sets by applying

database updates from a log data set or change accumulation data set to existing image copy data

Options for verifying data sets, including allocate and open to verify availability and usability of recovery input data sets.

The need to issue the IMS /DBR DB and /DBR AREA commands and the IMS /STA DB and /STA AREA commands is eliminated.

Page 37: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation37

IBM IMS Database Recovery Facility Extended Functions for

z/OS

Page 38: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation38

IMS Database Recovery Facility Extended Functions

Ensures that an IMS database environment is recoverable - Provides six unique features which:

Create clean valid recovery points (RPCR)- Creates recovery points for one or more databases by issuing synchronized /DBR

or /DBD commands across all systems Locate existing recovery points (RPID)

- Analyzes database allocation records in the RECON data sets to identify recovery time spans to which one or more databases can be recovered using timestamp or full recovery

Identify problems which may affect recoveries (“Health Check”)- Inspects the RECON data sets and z/OS catalogs and identifies a number of

problems that can impact IMS database recovery Verify needed recovery assets

- Examines the RECON data sets and identifies the recovery assets (data sets) that are required to recover one or more databases

Condition RECON data sets for disaster recovery- Prepares the RECON data sets for database recovery at your disaster recovery

(DR) site to match recovery ‘point in time’ Issue IMS commands via batch (Type 1 commands in batch)

Page 39: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation39

DRF/XF – Extended Functions

Recovery Point Creation (RPCR) – Provides the ability to create recovery points for one or more

databases

• By specifying multiple databases, you can create recovery points at the application level

• Allocation records in the RECON data sets are updated to reflect a valid, clean recovery point– These recovery points can be used to perform timestamp recoveries, full

recoveries, or create batch image copies to a specified point in time– The user will have the option of having databases /DBR’d or /DBD’d

– Databases will be restarted only on those systems which they were started before the process

– Optionally provide a synchronized log switch across all IMS systems in the environment

– Includes interfaces to pause CICS/ODBA threads and BMPs (at checkpoint) to allow /DBR to complete

Page 40: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation40

DRF/XF – Extended Functions

Recovery Point Identification (RPID)

– Interrogate information in the RECON to identify recovery points and/or recovery time spans to which one or more databases can be recovered

– Identifies recovery time spans individually and common to all databases specified

– Presents recovery points in ISPF-formatted screen

• User selects desired recovery point from ISPF panel • JCL is generated to execute DRF recovery of the

database to the chosen recovery point

Page 41: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation41

DRF/XF Health Checker Interrogate IMS database information looking for potential problems

relating to the recoverability of the environment

– Utilizes information from the RECON data sets and the catalog

Page 42: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation42

DRF/XF – Verify

Identification and Verification of Recovery Assets – Interrogate information in the RECON to identify the assets (logs,

change accums, image copies, etc…) which are required to recover one or more databases

– Once identified, processing options allow for:

• Listing of recovery assets (default, always done)• Verification that the recovery asset is cataloged• Allocation and opening of the file to ensure data set

is usable

Page 43: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation43

DRF/XF – Recon Cleanup

Required for disaster recovery environment

– At the disaster recovery site, the RECON data sets must be conditioned to match the recovery environment

– The following RECON records are affected:

– Data set allocation

– Log data sets

– PRILOG record

– Image copies (beyond the recovery timestamp)

– Change accumulation

– Database reorganization

– System (IMSid)

– Detailed report is generated (not shown)

Page 44: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation44

DRF/XF – IMS Command Interface

Utilizes the IMS Tools Online System Interface to provide a batch IMS

Command interface

– Allows any type-1 IMS command supported through an AO application

– Output from commands displayed in the report file

– Provides three levels of security:

– Same as IMS

– Application class

– None

Page 45: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation45

DRF/XF – Extended Functions

IMS Command Interface Input

Output

Page 46: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation46

IMS High Performance Change Accumulation (HPCA)

Runs multiple change accumulation groups in parallel and streams output across all addresses simultaneously

Functions:► Provides both ISPF interfaces that allow for customization, setup and

execution and Batch interfaces for operations

► DBRC is optional

► Processes input data (from RLDS's) and output data (new CA's) in parallel

Your Value:

Increased database availability

and IMS database data integrity  

Control SpaceControl Space

Main TCB

LogReader

TCB

IMSLog

IMSLog

LogReader

TCB

SORT SpacesSORT Spaces

Main HPCA TCB

SORTProduct

TCB

E15 E35

NewCA

OldCA

Page 47: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation

HPCA - Architecture1. HPCA driver retrieves the control and JCLinformation created during HPCA setup tasks.

2. HPCA driver establishes the environmentfor a single copy of the IMS Cautility. Each Sort process is either a separate TCB when in single address space mode, or a separate address space when in multiple address space mode. Each Sort process invokes an instance of the IMS change accumulation utility.

3. The HPCA Utility driver creates (for this example) two parallel log read tasks that will read n number of logs. Each log read just once.

4. All log records are selected according to the appropriate CAGRP and sent to the Sort task.

5. The Sort Controller invokes an instance of the IMS CA utility.

6. IMS CA utility invokes the Sort process.

7. Sort process selects DB-change type records.8. Records from the Sort process and old change accumulation data sets are merged.

9. The Merge process ultimately produces a new change accumulation data set.

10. The IMS CA report is returned to IMS HP ChangeAccumulation Utility.

Page 48: Recovery Solution Pack - IMS RUG March 2013 Columbus

© 2013 IBM Corporation48

Raquel Carvallo

[email protected]

Questions