Updates to IMS Recovery Solution Pack: IMS Database Recovery Facility V1.1 User's Guide

Product documentation


Abstract

Updates that apply to IMS Recovery Solution Pack: IMS Database Recovery Facility V1.1 User's Guide (SC19-2903-03).

Content

The most recent updates appear at the top of the list.


Update 4
Date of change: October 15, 2013
Change description:
The following new and changed information supports APAR PM94192.
New information is provided in Using IMS Database Recovery Facility to recover HALDB databases that use online reorganization.
Multiple topics in the IMS Recovery Solution Pack: IMS Database Recovery Facility V1.1 User's Guide are updated. Changed information is indicated by beginning of change (Start of change) and end of change (End of change) characters.

Topic: Using IMS Database Recovery Facility -> Using the IMS Database Recovery Facility basic product -> Add command reference (PDF page 102).

    Start of change USEAREA   End of change
    Start of change Indicates that you restored the image copy for the database and IMS Database Recovery Facility needs only to apply log updates.

    IMS Database Recovery Facility does not differentiate between the USEDBDS and USEAREA parameters. These parameters exist to be compatible with the DBRC GENJCL.RECOV command. Both parameters have the same effect because IMS Database Recovery Facility does not check whether the database is a full function database or a Fast Path area.

    IMS Database Recovery Facility does not verify whether a nonstandard image copy exists in the RECON.

    Restrictions:

    • USEDBDS and USEAREA work only with batch-type, nonstandard image copies. Concurrent, nonstandard image copies are not supported. If you must use concurrent, nonstandard image copies, see USEUICLAST and USEUICTIME.
    • You must restore nonstandard image copies before recovery.
    For information about how to recover with the  USEDBDS and  USEAREA parameters, see  Recovering with a nonstandard image copyEnd of change
    Start of change   USEDBDS   End of change
    Start of change Indicates that you restored the image copy for the database and IMS Database Recovery Facility needs only to apply log updates.

    IMS Database Recovery Facility does not differentiate between the USEDBDS and USEAREA parameters. These parameters exist to be compatible with the DBRC GENJCL.RECOV command. Both parameters have the same effect because IMS Database Recovery Facility does not check whether the database is a full function database or a Fast Path area.

    IMS Database Recovery Facility does not verify whether a nonstandard image copy exists in the RECON.

    Restrictions:

    • USEDBDS and USEAREA work only with batch-type, nonstandard image copies. Concurrent, nonstandard image copies are not supported. If you must use concurrent, nonstandard image copies, see USEUICLAST and USEUICTIME.
    • You must restore nonstandard image copies before recovery.
    For information about how to recover with the  USEDBDS and  USEAREA parameters, see  Recovering with a nonstandard image copyEnd of change
    Start of change   USEUICLAST   End of change
    Start of change Indicates that you restored the image copy for the database and IMS Database Recovery Facility needs only to apply log updates.

    IMS Database Recovery Facility applies logs to the database or area from the latest user image copy that is recorded in the RECON. You must restore the database or area to the last user image copy time stamp before you recover.

    IMS Database Recovery Facility verifies that a user image copy was recorded in the RECON.

    Restrictions:

    • The nonstandard image copy must be registered as a user image copy in the RECON. You can register the image copy by using the DBRC NOTIFY.UIC command. The user image copy can be batch or concurrent.
    • You must restore nonstandard image copies before recovery.

    For information about how to recover with the  USEUICLAST parameter, see  Recovering with a nonstandard image copy. End of change

    Start of change   USEUICTIME ( time stamp of user image copy End of change
    Start of change Indicates that you restored the image copy for the database and IMS Database Recovery Facility needs only to apply log updates.

    IMS Database Recovery Facility applies logs to the database data set or area data set from the time stamp of the user image copy that is recorded in the RECON. You must restore the database data set or area data set to the time stamp of the user image copy before you recover.

    The time stamp that is specified for the USEUICTIME parameter must be a valid user image copy time stamp in the RECON for the database data set. If the user image copy time stamps differ for each database data set, you must specify a separate ADD statement for each data set and specify the applicable user image copy time stamp.

    IMS Database Recovery Facility verifies that a user image copy is recorded for that time stamp in the RECONs for each database data set.

    For information about how to recover with the USEUICTIME parameter, see Recovering with a nonstandard image copy. End of change


Topic: Using IMS Database Recovery Facility -> Using the IMS Database Recovery Facility basic product -> START command reference (PDF page 108).

    VERIFY( LIST ,ALLOC,OPEN)
    This parameter specifies the VERIFY level that you want IMS Database Recovery Facility to perform. When VERIFY is specified, no recovery or output processing is performed. VERIFY is used to verify the recovery assets that are needed to perform the requested action.

    Start of changeYou do not need to stop the database to the use the verify parameter. However, the results are not the same as when the database is stopped. The list of log data sets that are needed for a recovery do not include the active log when the verify recovery is run. Other changes might occur when the database is stopped. You can take a new change accumulation or an image copy.
    If you specify VERIFY without any options, it defaults to VERIFY(LIST).End of change

    Three VERIFY levels can be specified.

    LIST

      If you specify VERIFY(LIST), IMS Database Recovery Facility provides a list of all log, image copy, and change accumulation data sets that is required for recovery. The list contains information that is extracted from DBRC about each data set. LIST is the default value.
    ALLOC
      If you specify VERIFY(ALLOC), IMS Database Recovery Facility obtains the list of data sets and then allocates each one, with a deferred mount for tape data sets, to verify the existence and physical accessibility of each data set. The LIST function is also performed.

      If an error is encountered in the allocation process, the data set entry on the report is flagged as an error with the ALLOC RC = nn message next to the name. nn This parameter specifies the return code from the DYNALLOC macro.

      Tip: Search for FRD4302I or FRD4210I messages in your job log for additional reason codes regarding the cause of image copy, log, or change accumulation processing errors.

    OPEN
      If you specify VERIFY(OPEN), each data set is opened to verify its availability and usability. The LIST and ALLOC functions are also performed.

      If an error is encountered during the OPEN process, the data set entry on the report is flagged as an error and an OPEN RC=nn message is displayed next to the name. nn This parameter specifies the return code from the OPEN macro.

Topic: Administering IMS Database Recovery Facility -> Managing sources of input -> Nonstandard image copy recovery (PDF page 157).

    Start of change Recovering with a nonstandard image copy End of change

    Start of changeYou can recover database data sets and areas even if a nonstandard image copy, such as a user image copy, is restored. However, the nonstandard image copies are not used as input for IMS™ Database Recovery Facility. End of change

    About this task

    Start of change You can recover with nonstandard image copies by using the USEDBDSUSEAREAUSEUICLAST, or USEUICTIME parameters for the ADD command. You must restore the data set with the nonstandard image copy before you recover. You can automatically restore any standard or nonstandard image copy that is registered to DBRC as an IMS image copy. End of change

    Start of changeProcedure

    1. Restore the database data set or area from the nonstandard image copy.

    Requirement: Concurrent nonstandard image copies must be registered to DBRC with the correct USID. See the DBRC NOTIFY.UIC command. If the USID is incorrect, the recovery will be faulty. The correct USID is located in the RECON ALLOC record that corresponds to the time that the concurrent nonstandard image copy was taken.

    2. Depending on the parameter that you use for the ADD command, you might need to use the DBRC NOTIFY.RECOV command:

    • If you are recovering by using the USEDBDS or USEAREA parameters, record the restoration by using a DBRC NOTIFY.RECOV command. Specify the image copy run time for the RCVTIME parameter.
    • If you are recovering by using the USEUICLAST or USEUICTIME parameters, do not use the NOTIFY.RECOV command. Proceed to the next step.

    3. Add the database data set or area to the recovery list by using the  ADD command with the  USEDBDSUSEAREAUSEUICLAST, or  USEUICTIME parameter.

    4. Proceed with recovery by using the RECOVER START command or the ADD command in batch.

    5. If you use FASTIC=DUMP in your IMS High Performance Image Copy job, you must also specify RECFM=V for IMS Database Recovery Facility to restore the image copy.End of change


Topic: Reference: IMS Database Recovery Facility -> IMS Database Recovery Facility abend codes -> Reason codes for logic error abend ABENDU0385 (PDF page 281)

    Start of change 01C

    IMS Database Recovery Facility initialization error

    Explanation

    IMS™ Database Recovery Facility failed to initialize.

    User response

    Contact IBM Software Support.End of change


    Start of change01D

    Cannot recover to specified RCVTIME

    Explanation

    IMS™ Database Recovery Facility attempted to recover to a time where an online reorganization was initiated but the online reorganization was not yet active. The target data set allocation information (x'2930' log) is not available, and therefore recovery cannot finish.

    User response

    Use the start time of the online reorganization to bypass online reorganization processing, or specify a time after the online reorganization was active (x'2940' log).End of change



Update 3
Date of change: July 30, 2013
Change description:
New information is added to the definition of the VERIFY parameter that is located in Using IMS Database Recovery Facility -> Using the IMS Database Recovery Facility basic product -> START command reference (PDF page 108). Changed information is indicated by beginning of change (Start of change) and end of change (End of change) characters.

VERIFY(LIST,ALLOC,OPEN)
This parameter specifies the VERIFY level that you want IMS Database Recovery Facility to perform. When VERIFY is specified, no recovery or output processing is performed. VERIFY is used to verify the recovery assets that are needed to perform the requested action. If you specify VERIFY without any options, it defaults to VERIFY(LIST).

Three VERIFY levels can be specified.

Start of changeNOTE: When verifying logs, if the databases are allocated/updated during the VERIFY, only archived logs can be verified. In this case, the Recovery (without VERIFY) will show a different number of logs since the databases will be deallocated by recovery.End of change


Update 2
Date of change: June 1, 2012
Change description: Various documentation updates made to reflect changes in the SAMPLIB. Changed information is indicated by beginning of change (Start of change) and end of change (End of change) characters.


PDF Page 30
Chapter 3. Configuring the basic product environment -> Environmental control statements

Start of changeDRFIAX(procname)End of change
Start of changeUse this parameter to specify the name of the procedure used to initiate the IMS Database Recovery Facility Utility Address Space (UAS/IAX) for IMS Index Builder, the image copy function of IMS HP Image Copy, DFSPREC0, and the Build Index function of FPA. The default for the DRFIAX parameter is FRXJCLIP. The procedure must reside in a valid z/OS PROCLIB. Samples of this procedure are located in SFRXSAMP(FRXIAX|FRXJCLIP).
Tip: Customize the FRXIAX procedure and rename to FRXIAXxx, where xx is the maintenance
level used (for example, TEST or PROD).
Read syntax diagramSkip visual syntax diagram
DRFIAX parameter syntax

           .-FRXIAXxx-.     
>>-DRFIAX(-+-FRXJCLIP-+-)--------------------------------------><
           '-procname-'     

Start of changeDRFPROC(procname) End of change
Start of changeUse this parameter to specify the name of the procedure used to initiate the IMS Database Recovery Facility recovery sort subordinate address space (RSS).
The procedure must reside in a valid z/OS PROCLIB data set. If you specify this parameter in the SYSIN control statements, the procedure name that is defined by the SET statements in your execution JCL is overridden. Samples of this procedure are located in SFRXSAMP(FRXRSS|FRXJCLSB).
Tip: Customize the FRXRSS procedure and rename to FRXRSSxx, where xx is the maintenance level used (for example, TEST or PROD).
Read syntax diagramSkip visual syntax diagram
DRFPROC parameter syntax

            .-FRXRSSxx-.     
>>-DRFPROC(-+-FRXJCLSB-+-)-------------------------------------><
            '-procname-'     
End of change
PDF Page 75
Chapter 5. Configuring JCL statements and procedures -> Master address space JCL

Start of changeSample JCL is located in SFRXSAMP(FRXDRF/FRXDRFC) and SFRXSAMP(FRXIVPD1/D2) sample members. These JCL members run the SFRXSAMP(FRXMAS) procedure. If you are using a consolidated IMS Tools load library, use the sample JCL located in SFRXSAMP(FRXDRFC) and FRXIVPD2.End of change

Important: The IMS Database Recovery Facility master address space JCL cannot contain any hard-coded database data sets. Because IMS Database Recovery Facility dynamically allocates the database data sets for recovery in the subordinate address space, dynamic allocation will fail if any of the subsequent steps have these same data sets allocated by DD statements in the MAS. This is a z/OS® restriction.

Start of changeThe following master address space DDNAME statements are located in SFRXSAMP(FRXMAS|FRXMASC). With the exception of the PSBLIB and SYSUDUMP DD statements, these DD statements are passed to the recovery sort subordinate address space, the address space for the Build Index function of FPA, as well as the address spaces for IMS Index Builder and DFSPREC0. The DD statements are dynamically allocated if they do not already exist.End of change

PDF Page 81
Chapter 5. Configuring JCL statements and procedures -> Recovery sort subordinate address space JCL


Start of changeThe procedure that is used to create this address space is specified by using the DRFPROC= environmental control statement. The default procedure name is FRXJCLSB. Samples are located in the SFRXSAMP(FRXRSS|FRXJCLSB) members. The FRXJCLSB procedure is used to start the recovery sort subordinate address space and must be placed in a valid z/OS® system procedure library.
Tip: If you have multiple maintenance levels of IMS Tools, you must customize separate FRXRSSxx members, where xx is the maintenance level used. For example, create FRXRSST1 for the IMS Tools load library that is used in your test environments and FRXRSSP1 for the IMS Tools load library that is used in your production environments.
End of change
PDF Page 83
Chapter 5. Configuring JCL statements and procedures -> IMS Index Builder, DFSPREC0, and Build Index function of FPA address space JCL

Start of changeThe address spaces for IMS Index Builder, DFSPREC0, IMS High Performance Image Copy, and the Build Index function of FPA are started by the master address space. The procedure that is used to create these address spaces is specified by using the DRFIAX() environmental control statement. The default procedure name is FRXJCLIP. Samples are located in the SFRXSAMP(FRXJCLIP|FRXIAX) member.
Tip: Customize the FRXRSS procedure and rename to FRXRSSxx, where xx is the maintenance level or IMS subsystem used (for example, TEST or PROD and IMS V11 or IMS V12). For example:

  • If you have different IMS subsystems, you can create FRXIAX11 for your IMS V11 system and FRXIAX12 for your IMS V12 system.
  • If you have different environments with different maintenance levels, you can create FRXRSST1 for IMS SSID IMT1 of your test environment and FRXRSSP1 for your IMS SSID IMP1 of your production environment.
End of change
PDF Page 201
Chapter 14. Usage scenarios for optimizing your IMS Recovery Solution Pack: IMS Database Recovery Facility experience -> Setting up the IMS Recovery Solution Pack -> Customizing the procedures and JCL members

Start of changeDRFMAS procedureEnd of change
Start of changeThis generic procedure is used to allocate the IMS Database Recovery Facility MAS. Make a copy of your.hlq.SFRXSAMP(FRXMAS). All of the variables in this procedure are controlled by the SET statements in the execution JCL that are called by your.hlq.SFRXSAMP(FRXDRF).End of change
Start of changeIf you are using a consolidated IMS Tools load library, copy your.hlq.SFRXSAMP(FRXMASC) and customize the SET statements in your.hlq.SFRXSAMP(FRXDRFC).End of change

Start of changeDRFIAX procedureEnd of change
Start of changeThis IMS Database Recovery Facility UAS/IAX procedure is used to allocate the IB, IC, and DFSPREC0 address spaces. Make a copy of your.hlq.SFRXSAMP(FRXIAX) and customize it by adding the name of your IMS Database Recovery Facility load library or consolidated IMS Tools load library.
Tip: If you have multiple levels of maintenance for the IMS Tools, customize the FRXIAX procedure and rename to FRXIAXxx, where xx is the maintenance level used for each load library. For example, you can create FRXIAXT1 for IMS SSID IMT1 of your test environment and FRXIAXP1 for your IMS SSID IMP1 of your production environment.
End of change
Start of changeDRFPROC procedureEnd of change
Start of changeThis procedure is used to allocate the IMS Database Recovery Facility subordinate address spaces. Make a copy of your.hlq.SFRXSAMP(FRXRSS) and customize it by adding the name of your IMS Database Recovery Facility load library or consolidated IMS Tools load library.
Tip: If you have multiple levels of maintenance for the IMS Tools, customize the FRXRSS procedure and rename to FRXRSSxx, where xx is the maintenance level used for each load library. For example, you can create FRXRSST1 for IMS SSID IMT1 of your test environment and FRXRSSP1 for your IMS SSID IMP1 of your production environment.
End of change
PDF Page 203
Chapter 14. Usage scenarios for optimizing your IMS Recovery Solution Pack: IMS Database Recovery Facility experience -> Recover the database to the current time -> Creating and running a IMS Database Recovery Facility job

Procedure
  1. Install and configure the required IMS Database Recovery Facility load libraries and utilities. For more information, see Installing IMS Recovery Solution Pack libraries
  2. Start of changeCustomize the procedures and JCL found in the your.hlq.SFRXSAMP sample library.
    FRXMAS or FRXMASC
    Sample IMS Database Recovery Facility master address space procedure. If you are using a consolidated IMS Tools load library, use FRXMASC.
    FRXRSS or FRXJCLSB
    Sample IMS Database Recovery Facility subordinate address space procedure.
    Tip: Customize the FRXRSS procedure and rename to FRXRSSxx, where xx is the maintenance level used (for example, TEST or PROD).
    FRXIAX or FRXJCLIP
    Sample IMS Database Recovery Facility subordinate address space procedure.
    Tip: Customize the FRXIAX procedure and rename to FRXIAXxx, where xx is the maintenance level used (for example, TEST or PROD).
  3. Start of changeCustomize the execution JCL located in the your.hlq.SFRXSAMP sample library.
    FRXDRF or FRXDRFC
    Sample batch job to run IMS Database Recovery Facility. If you are using a consolidated IMS Tools load library, use FRXDRFC.
    The following example shows modified IMS Database Recovery Facility JCL to run a recovery:
    a//DRF      EXEC FRXMAS,DRFMBR=ZZ
    //SYSIN DD *  
    REPORT(RPTTYPE=SEP,DRFUNIT=SYSDA,DRFHLQ=MYDRF1)
    SORTPARM(ASPREF(AS))  
    DBDSL101(DISP(NEW))  
    bOUTPUT(PRO)  
    cADD DB(DHVNTZ02) DBATRB(DBDSL(101))
    START ERROR(CONT)
    //  
    Notes:
    a. When you run IMS Database Recovery Facility, the FRXMAS procedure is invoked. DRFMBR=ZZ references the FRXDRFZZ configuration file for IMS Database Recovery Facility.
    b. A combination of OUTPUT(PRO) and DISP(NEW) causes IMS Database Recovery Facility to delete and redefine the production database data sets during recovery to the current time.
    c. The database name is DHVNTZ02 (HIDAM/VSAM). You can specify one or more databases to recover.
      End of change
PDF Page 206
Chapter 14. Usage scenarios for optimizing your IMS Recovery Solution Pack: IMS Database Recovery Facility experience -> Validating recovery by using IMS HP Pointer Checker -> Creating and running a IMS Database Recovery Facility job

Procedure
  1. Install and configure the required IMS Database Recovery Facility load libraries and utilities. For more information, see Installing IMS Recovery Solution Pack libraries
  2. Start of changeCustomize the procedures found in the your.hlq.SFRXSAMP sample library.
    FRXJCLSB or FRXRSS
    Sample IMS Database Recovery Facility subordinate address space procedure.
    Tip: Customize the FRXRSS procedure and rename to FRXRSSxx, where xx is the maintenance level used (for example, TEST or PROD).
    FRXMAS or FRXMASC
    Sample IMS Database Recovery Facility master address space procedure. You must include the name of your HPPC LOADLIB in the STEPLIB. If you are using a consolidated IMS Tools load library, use FRXMASC.
  3. Add the PC() keyword to the IMS Database Recovery Facility ADD statement.
    To call and run HPPC from a IMS Database Recovery Facility job, you must include a new IMS Database Recovery Facility keyword called PC() in your IMS Database Recovery Facility ADD statement. When you include the PC() keyword in the IMS Database Recovery Facility ADD statement, you are telling IMS Database Recovery Facility to run HPPC (for full-function databases) and DEDB PC (for Fast Path databases). You can include other optional keywords in the PC() statement. However, for this scenario, we will keep the standard defaults.
  4. Customize the execution JCL found in the your.hlq.SFRXSAMP sample library.
    FRXDRF or FRXDRFC
    Sample batch job to run IMS Database Recovery Facility. If you are using a consolidated IMS Tools load library, use FRXDRFC.
    The following example shows modified IMS Database Recovery Facility JCL to run a IMS Database Recovery Facility/PC recovery:
    a//DRF      EXEC FRXMAS,DRFMBR=ZZ
    //SYSIN DD *    
    REPORT(RPTTYPE=SEP,DRFUNIT=SYSDA,DRFHLQ=MYDRF1)
    SORTPARM(ASPREF(AS))  
    DBDSL101(DISP(NEW))    
    bOUTPUT(PRO)  
    cADD DB(DHVNTZ02,DEDBJN23) PC() -
     DBATRB(DBDSL(101))
    START ERROR(CONT)
    //  
    Notes:
    1. When you run IMS Database Recovery Facility, the FRXMAS procedure is invoked. DRFMBR=ZZ references the FRXDRFZZ configuration file for IMS Database Recovery Facility.
    2. A combination of OUTPUT(PRO) and DISP(NEW) causes IMS Database Recovery Facility to delete and redefine the production database data sets during recovery to the current time.
    3. DHVNTZ02 (HIDAM/VSAM) is a full-function database and DEDBJN23 is a Fast Path database with eight areas. You can specify one or more databases to recover.
End of change
PDF Page 210
Chapter 14. Usage scenarios for optimizing your IMS Recovery Solution Pack: IMS Database Recovery Facility experience -> Taking an incremental image copy of offline databases -> Identifying the databases to perform incremental image copy -> Creating and running a IMS Database Recovery Facility job

Procedure
  1. Install and configure the required IMS Database Recovery Facility load libraries and utilities. For more information, see Installing IMS Recovery Solution Pack libraries
  2. Start of changeCustomize the procedures found in the your.hlq.SFRXSAMP sample library.
    FRXJCLSB or FRXRSS
    Sample IMS Database Recovery Facility subordinate address space procedure.
    Tip: Customize the FRXRSS procedure and rename to FRXRSSxx, where xx is the maintenance level used (for example, TEST or PROD).
    FRXMAS or FRXMASC
    Sample IMS Database Recovery Facility master address space procedure. You must include the name of your HPIC LOADLIB in the STEPLIB. If you are using a consolidated IMS Tools load library, use FRXMASC.
  3. Customize the execution JCL found in the your.hlq.SFRXSAMP sample library.
    FRXDRF or FRXDRFC
    Sample job to run IMS Database Recovery Facility. If you are using a consolidated IMS Tools load library, use FRXDRFC.
    Make a copy of the your.hlq.SFRXSAMP(FRXDRF) JCL.
    The following example shows modified JCL to run a IMS Database Recovery Facility ICR:
    a//DRF      EXEC FRXMAS,DRFMBR=ZZ
    //SYSIN DD *        
    REPORT(RPTTYPE=SEP,DRFUNIT=SYSDA,DRFHLQ=MYDRF1)  
    SORTPARM(ASPREF(AS))  
    DBDSL101(DISP(NEW))    
    bOUTPUT(ICR)  
    cADD DB(DHVNTZ02) DBATRB(DBDSL(101)) -
    dIC (COMP(Y),-
    COMPRTN(FABJCMP3),-
         DSNTYPE(BASIC),-
         ICHLQ(TEMP.IC),-
         ICNMRULE(Y),-  
         UNIT(SYSDA),-
         SPACE(CYL,1,1,RLSE))
    START ERROR(CONT)
    //  
    Notes:
    1. When you run IMS Database Recovery Facility, the FRXMAS procedure is invoked. DRFMBR=ZZ references the FRXDRFZZ configuration file for IMS Database Recovery Facility.
    2. For more information about how to explicitly instruct IMS Database Recovery Facility to generate an ICR, see the "Environmental control statements" topic in IMS Recovery Solution Pack: IMS Database Recovery Facility User's Guide.
    3. The database name DHVNTZ02 (HIDAM/VSAM) is used by the ICR process in the ADD DB() parameter. You can specify one or more databases to take an ICR.
    4. You can customize the IC keywords to your specifications. For more information, see the "Integrated auxiliary utility parameters for IMS High Performance Image Copy" topic in IMS Recovery Solution Pack: IMS Database Recovery Facility User's Guide. In this case, the output ICR is compressed by using the FABJCMP3 routine, and the output IC data set name follows the ICNMRULE naming convention (ichlq.ICn.dbdname.ddname.Dyyddd.Thhmmss).
      End of change
PDF Page 216
Chapter 14. Usage scenarios for optimizing your IMS Recovery Solution Pack: IMS Database Recovery Facility experience -> Taking an incremental image copy of an online database to the current time or point-in-time -> Creating and running your IMS Database Recovery Facility job

Procedure
1. Install and configure the required IMS Database Recovery Facility load libraries and utilities. For more information, see Installing IMS Recovery Solution Pack libraries
2. Start of changeCustomize the procedures found in the your.hlq.SFRXSAMP sample library.
      FRXJCLSB or FRXRSS
      Sample IMS Database Recovery Facility subordinate address space procedure.
      Tip: Customize the FRXRSS procedure and rename to FRXRSS xx, where xx is the maintenance level used (for example, TEST or PROD).
      FRXMAS or FRXMASC
      Sample IMS Database Recovery Facility master address space procedure. You must include the name of your HPIC LOADLIB in the STEPLIB. If you are using a consolidated IMS Tools load library, use FRXMASC.
      End of change
3. Start of changeCustomize the execution JCL found in the your.hlq.SFRXSAMP sample library.
      FRXDRF or FRXDRFC
      Sample job to run IMS Database Recovery Facility. If you are using a consolidated IMS Tools load library, use FRXDRFC.
      The following example shows modified IMS Database Recovery Facility ICR JCL in which an ICR is being taken with the database allocated:
      a //DRF      EXEC FRXMAS,DRFMBR=ZZ                                  
      //SYSIN DD *                                                      
      REPORT(RPTTYPE=SEP,DRFUNIT=SYSDA,DRFHLQ=MYDRF1)                    
      SORTPARM(ASPREF(AS))  
      DBDSL101(DISP(NEW))                                          
      b OUTPUT(ICR)                                              
      c ADD DB(DHVNTZ02) DBATRB(DBDSL(101)) -                  
      d IC (COMP(Y),-
      COMPRTN(FABJCMP3),-                                              
           DSNTYPE(BASIC),-                                            
           ICHLQ(TEMP.IC),-
           ICNMRULE(Y),-                                              
           UNIT(SYSDA),-                                                
           SPACE(CYL,1,1,RLSE))
      e START ERROR(CONT) RCVTIME(‘11.044 18:25:37.5')
      //  

      Notes:
      1. When you run IMS Database Recovery Facility, the FRXMAS procedure is invoked. DRFMBR=ZZ references the FRXDRFZZ configuration file for IMS Database Recovery Facility.
      2. To explicitly instruct IMS Database Recovery Facility to take an ICR, see the "Environmental control statements" section in the IMS Recovery Solution Pack: IMS Database Recovery Facility User's Guide.
      3. The database name DHVNTZ02 (HIDAM/VSAM), which is identified in step 1, is used to take an ICR by using the ADD DB() parameter. You can specify one or more databases take an ICR of.
      4. You can customize the IC keywords to your specifications. For more information, see the "Environmental control statements" section in the IMS Recovery Solution Pack: IMS Database Recovery Facility User's Guide. In this case, the output ICR is compressed by using the FABJCMP3 routine, and the output IC data set name follows the ICNMRULE naming convention (ichlq.ICn.dbdname.ddname.Dyyddd.Thhmmss).
      5. Specifying RCVTIME() is optional. If you want to run ICR to current time, you do not need to include this parameter because IMS Database Recovery Facility automatically calls HPIC to generate concurrent and fuzzy ICs for the allocated databases that are specified in the ADD DB() statement. However, if you want to generate a point-in-time ICR that is not the current time, you must input the specific time by using RCVTIME(). In this scenario, the chosen time was inserted.
      End of change
PDF Page 220
Chapter 14. Usage scenarios for optimizing your IMS Recovery Solution Pack: IMS Database Recovery Facility experience -> Using IMS Index Builder to rebuild indexes during recovery -> Creating and running a IMS Database Recovery Facility job

Procedure
  1. Install and configure the required IMS Database Recovery Facility load libraries and utilities. For more information, see Installing IMS Recovery Solution Pack libraries
  2. Start of changeCustomize the procedures found in the your.hlq.SFRXSAMP sample library.
    FRXJCLIP or FRXIAX
    Sample utility address space JCL for IB and DFSPREC0.
    Tip: Customize the FRXIAX procedure and rename to FRXIAXxx, where xx is the maintenance level used (for example, TEST or PROD).
    FRXJCLSB or FRXRSS
    Sample IMS Database Recovery Facility subordinate address space procedure.
    Tip: Customize the FRXRSS procedure and rename to FRXRSSxx, where xx is the maintenance level used (for example, TEST or PROD).
    FRXMAS or FRXMASC
    Sample IMS Database Recovery Facility master address space procedure. You must include the name of your IB LOADLIB in the STEPLIB. If you are using a consolidated IMS Tools load library, use FRXMASC.
  3. Start of changeCustomize the execution JCL found in the your.hlq.SFRXSAMP sample library.
    FRXDRF or FRXDRFC
    Sample job to run IMS Database Recovery Facility. If you are using a consolidated IMS Tools load library, use FRXDRFC.
    The following example shows modified IMS Database Recovery Facility JCL to run a recovery and use IB to rebuild the indexes:
    //IMS Database Recovery Facility      EXEC FRXMAS,DRFMBR=ZZ                                  
    //SYSIN DD *                                                      
    aDRFIAX(FRXJCLIP)
    REPORT(RPTTYPE=SEP,DRFUNIT=SYSDA,DRFHLQ=MYDRF1)  
    SORTPARM(ASPREF(AS))  
    DBDSL101(DISP(NEW))                                          
     OUTPUT(PRO)                                              
    bADD DB(DBOHIDK5) IB(HALDB=BOTH,BLD_SECONDARY(ALL)) -
     DBATRB(DBDSL(101))                  
    START ERROR(CONT)
    //  
    Notes:
    1. DRFIAX specifies the name of the procedure that is used to initiate the utility address space for IB.
    2. IMS Database Recovery Facility recovers the DBOHIDK5 (PHIDAM/OSAM) database and rebuilds the primary index and ILE, including rebuilding all of the secondary indexes by using the IB() keyword. You can customize the IB keywords to your specifications. For more information, see IMS Recovery Solution Pack: IMS Database Recovery Facility User's Guide.
End of change


Update 1
Date of change: April 18, 2012
Topics:
Chapter 3. Configuring IMS Database Recovery Facility -> Configuring the basic product environment -> Environmental control statements
Change description:
Corrected the description of DRFVOLSR environmental control statement to remove incorrect reference to DRFVOLSER.

    DRFVOLSR=
    Specifies a 1- to 6-character volume serial number that is passed to the subspaces in order to provide a specific volume on which to allocate any report data sets. Use DRFVOLSR to specify a particular volume serial number on which to dynamically allocate and catalog any required data sets.

    Specifying DRFVOLSR is optional. If you do not specify DRFVOLSR, the temporary data sets are written to local volumes. DRFVOLSR is required when you have insufficient local volumes or if the volumes are not SMS-managed.

Rate this page:

(0 users)Average rating

Document information


More support for:

IMS Tools
IMS Recovery Solution Pack: IMS Database Recovery Facility

Software version:

1.1.0

Operating system(s):

z/OS

Reference #:

7018379

Modified date:

2011-03-15

Translate my page

Machine Translation

Content navigation