Updates to IMS Database Repair Facility for IMS Solution Packs User's Guide

Product documentation


Abstract

Updates that apply to IMS Database Repair Facility for IMS Solution Packs User's Guide (SC19-2916-00).

Content

The most recent update is listed first.



Update 12
Date of change: July 2014
Change description: Documentation changes by APAR PI21383. The length of the data set group field or the area number field in certain panels is now extended. The position of some columns are updated.
Topics: Changes apply to the following multiple topics.

> 2.0 Using IMS Database Repair Facility interactively
>> 2.7 View/update database
>>> 2.7.5 Processing HD or DEDB databases
>>>> 2.7.5.8 Segment prefix dump panel

The image of the Segment prefix dump panel has been replaced with the following image:
Start of change

End of change
Figure 14. Segment prefix dump panel (FABZPS5P)

----------------------------------
>>>> 2.7.5.9 Display segment data in hex format

The image of the Segment data in hex format panel has been replaced with the following image:
Start of change

End of change
Figure 15. Segment data in hex format panel (FABZPS5)

Description for the DSG field has been updated as follows:

The fields on this panel are:
...

DSG

    Start of changeThe number of the data set group or, for a DEDB, the area number. End of change

----------------------------------
>>>> 2.7.5.10 Display segment data in character and hex format

The image of the Segment data in character and hex format panel has been replaced with the following image:
Start of change

End of change
Figure 16. Segment data in character and hex format panel (FABZPS6)

Description for the DSG field has been updated as follows:

This panel contains the following fields:
...
DSG
    Start of changeThe number of the data set group or, for a DEDB, the area number. End of change

----------------------------------
>>>> 2.7.5.11 Display block or CI in hex format

The image of the Block or CI in hex format panel has been replaced with the following image:
Start of change

End of change
Figure 17. Block or CI in hex format panel (FABZPS10)

Description for the DSG field has been updated as follows:

The fields on this panel are:
...
DSG
    Start of changeThis is the number of the data set group or, for a DEDB, the area number. End of change

----------------------------------
>>>> 2.7.5.12 Display block or CI in character and hexadecimal format

The image of the Block or CI in character and hexadecimal format panel has been replaced with the following image:
Start of change

End of change
Figure 18. Block or CI in character and hexadecimal format panel (FABZPS11)

Description for the DSG field has been updated as follows:

The fields on this panel are:
...
DSG
    Start of changeThe number of the data set group or, for a DEDB, the area number. End of change

----------------------------------
>> 2.8 Undo changes
>>> 2.8.4 Undo changes

The image of the Undo changes panel has been replaced with the following image:
Start of change

End of change
Figure 29. Undo changes panel (FABZPS7)

----------------------------------
>> 2.9 View audit history of processed segments
>>> 2.9.4 Audit history of processed segments

The image of the Audit history of processed segments panel has been replaced with the following image:
Start of change

End of change
Figure 33. Audit history of processed segments panel (FABZPS4)

Description for the DSG field has been updated as follows:

The fields on this panel are:
...
DSG
    Start of changeThe data set group or, for a DEDB, the area number to which this segment belongs. End of change

==================================
> 5.0 Messages and codes of IMS Database Repair Facility
>> 5.2 Messages

Message FABZ086W has been updated as follows:
Start of change
FABZ086W SELECTED DATA SET GROUP (DSG) value1 DOES NOT EXIST. THE NUMBER OF DATASET GROUP S FOR THIS DBD IS value2

Explanation: The specified data set group number or the area number ( value1) does not exist. value2 shows the total number of data set groups or areas in this database.
System action: Processing is interrupted until the problem is corrected.
Programmer response: Specify the correct number of the data set group or the correct area number.
End of change
------
The following new message has been added:
Start of change
FABZ101W AREA area IS NOT DEFINED IN RECON

Explanation: The indicated area is not found in the RECON data sets.
System action: Processing is interrupted until the problem is corrected.
Programmer response: Specify the correct RECON data sets.
End of change


Update 11
Date of change: December 2013
Change description: Documentation changes by APAR PM97585. By applying this APAR, you can use the HD Pointer Checker utility (of IMS High Performance Pointer Checker) and the ILK Repair utility to repair HALDB databases that have corrupted HALDB partition reorganization numbers, duplicate indirect list keys (ILKs), or potentially duplicate ILKs.

> 1.0 IMS Database Repair Facility overview

The following paragraph has been added to the bottom of the topic:

...

Start of changeIMS Database Repair Facility also provides the ILK Repair utility. Use the ILK Repair utility together with the HD Pointer Checker utility (of IMS High Performance Pointer Checker) to repair HALDB databases that have corrupted HALDB partition reorganization numbers, duplicate indirect list keys (ILKs), or potentially duplicate ILKs. For information about corrupted HALDB partition reorganization numbers, duplicate ILKs, or potentially duplicate ILKs, see the IMS High Performance Pointer Checker User's Guide. End of change

----------------------------------
>> 1.1 Highlights and benefits of IMS Database Repair Facility
The following paragraph has been added to the bottom of the topic:

Start of changeBy using the ILK Repair utility together with the HD Pointer Checker utility of IMS High Performance Pointer Checker, you can:
  • Repair corrupted HALDB partition reorganization numbers, duplicate ILKs, and potentially duplicate ILKs in HALDB databases. All the databases that are logically related and PSINDEX databases are also repaired.
  • Generate Control Statements and Messages reports that list the repaired databases.End of change

----------------------------------
>> 1.3 Supported databases

The following paragraph has been added to the bottom of the topic:

Start of changeThe ILK Repair utility supports HALDB partitioned hierarchical direct (PHDAM) databases, partitioned hierarchical index direct (PHIDAM) databases, and partitioned secondary index (PSINDEX) databases that use VSAM or OSAM access methods. End of change

----------------------------------
>> 1.7 Examples of IMS Database Repair Facility usage

The following new topic has been added:

Start of change Scenario 3 - Repairing duplicate ILKs in HALDB databases

After checking databases with the HD Pointer Checker utility of IMS High Performance Pointer Checker, you identified corrupted HALDB partition reorganization numbers, duplicate ILKs, and potentially duplicate ILKs in your HALDB databases. Such errors cannot be corrected with the standard IMS recovery methods or by database reorganization. Because such errors can cause data loss, you want to repair the databases as soon as possible.

You can fix such errors by using the HD Pointer Checker utility and the ILK Repair utility. The HD Pointer Checker utility generates repair information records that you use as input to the ILK Repair utility. All the databases that are logically related and PSINDEX databases are also repaired. End of change

==================================
The following new topics have been added before the messages and codes topics:

Start of change x.1 Repairing HALDB databases by using the ILK Repair utility

If you identify corrupted HALDB partition reorganization numbers, duplicate ILKs, or potentially duplicate ILKs in your HALDB databases, you must correct them because these problems can cause data loss.

To repair such errors, use the HD Pointer Checker utility of IMS High Performance Pointer Checker and the ILK Repair utility. The HD Pointer Checker utility generates repair information records in a data set that you use as input to the ILK Repair utility. The ILK Repair utility corrects the errors in the HALDB databases, all the databases that are logically related, and PSINDEX databases.

For more information, see the topic "Repairing HALDB partition reorganization numbers and duplicate ILKs" in the IMS High Performance Pointer Checker User's Guide. End of change

Start of change x.1.1 Running the ILK Repair utility

Run the ILK Repair utility to repair corrupted HALDB partition reorganization numbers, duplicate ILKs, and potentially duplicate ILKs in HALDB databases. The utility also repairs such errors in the logically related databases and PSINDEX databases at the same time.

    Before you begin
    This utility requires the repair information records that are created by the HD Pointer Checker utility of IMS High Performance Pointer Checker. Complete the instructions in the topic "Repairing HALDB partition reorganization numbers and duplicate ILKs" in the IMS High Performance Pointer Checker User's Guide.

    Procedure
    1. Specify the JOB and the EXEC statements.
      Define the JOB and the EXEC statements in the utility JCL. Code the EXEC statement as follows:

      //         EXEC PGM=IKJEFT1B,DYNAMNBR=25

    2. Specify the DD statements.
      Define the DD statements in the utility JCL. Use the following JCL example to code the JCL statements:


      //DBRFZAP  JOB  (installation accounting information)
      //*        
      //BATCHTSO EXEC PGM=IKJEFT1B,DYNAMNBR=25
      //*                                    
      //SYSEXEC  DD   DISP=SHR,DSN=HPS.SFABCLIB
      //SYSTSIN  DD   *  
        PROFILE PREFIX(DBT)
        ISPSTART CMD(FABZREPR HPS DBT FABZ)
      /*                                    
      //FABZIN   DD   DISP=SHR,DSN=HPS.HDPC.FABPILK  
      //*                                          
      //SYSTSPRT DD   SYSOUT=A                      
      //SYSPRINT DD   SYSOUT=A                      
      //*                                          
      //ISPPLIB  DD   DISP=SHR,DSN=ISP.SISPPENU    
      //ISPMLIB  DD   DISP=SHR,DSN=ISP.SISPMENU    
      //ISPSLIB  DD   DISP=SHR,DSN=ISF.SISFSLIB    
      //ISPTLIB  DD   DISP=SHR,DSN=ISP.SISPTENU    
      //ISPPROF  DD   DISP=(NEW,PASS),DSN=&TEMP,      
      //             UNIT=SYSALLDA,SPACE=(CYL,(3,10,15)),
      //             DCB=(LRECL=80,BLKSIZE=3120,RECFM=FB)
      //ISPLOG   DD   SYSOUT=A,DCB=(LRECL=125,BLKSIZE=129,RECFM=VA)

      The following DD statements are supported:

      SYSEXEC
        Required. Defines the REXX procedure library of IMS Database Repair Facility (SFABCLIB).

      SYSTSIN
        Required. Defines the input data set that contains the PROFILE and ISPSTART commands and their parameters. The PROFILE command is optional but the ISPSTART command is required. The PROFILE command must precede the ISPSTART command.

        //SYSTSIN  DD   *
         PROFILE PREFIX( userid )
         ISPSTART CMD(FABZREPR smphlq workhlq workmlq debug )
        /*
        userid
          Optional. Specifies the prefix portion for the data set names that are used by ISPF.
          If the userid is defined to RACF, instead of specifying the PROFILE PREFIX( userid) statement, you can specify the USER= userid parameter on the JOB statement.
        smphlq
          Required. Specifies the high-level qualifier of the IMS Database Repair Facility load module library (SFABLMD0).
        workhlq
          Required. Specifies the high-level qualifier for the work data sets that are used by IMS Database Repair Facility.
        workmlq
          Required. Specifies the middle-level qualifier for the work data sets that are used by IMS Database Repair Facility.
        debug
          Optional. Code this parameter only for debugging purposes.
          To report problems to IBM for diagnosis, set this parameter to 1 to turn on the debug trace, rerun the failing job, and send the job log to IBM.

      FABZIN
        Required. Specifies the input data set, which is the FABPILK data set that is created by the HD Pointer Checker utility.

      SYSTSPRT
        Required. Specifies the output data set for the Control Statements and Messages repor. This report contains the result of the job, and when OSAM data sets are processed, it also contains the process logs, and messages.
        This data set contains 133-byte fixed-length records. If a block size is coded in your JCL, it must be a multiple of 133. Code your DD statement as follows:

         //SYSTSPRT DD SYSOUT=A

      SYSPRINT
        Required. Specifies the output data set for the Control Statements and Messages report. This report contains the process logs and messages for VSAM data sets.

        This data set contains 133-byte fixed length records. If a block size is coded in your JCL, it must be a multiple of 133. Code your DD statement as follows:

         //SYSPRINT DD SYSOUT=A

      ISPPLIB
      ISPMLIB
      ISPSLIB
      ISPTLIB
      ISPPROF
      ISPLOG
        Except for the ISPLOG DD statement, all these DD statements are required. These DD statements specify the ISPF data sets. For more information about these DD statements, see the z/OS ISPF User’s Guide, Volume 1.

    3. Submit the job.

    4. Ensure that the job completed successfully by locating the FABZ800I message in the Control Statements and Messages report in the SYSTSPRT data set. This message indicates the successful completion of the job.

    5. In the Control Statements and Messages report in the SYSTSPRT data set and the SYSPRINT data set, locate the following indicator:

      * DBNAME: dbdname   PARTNAME: partname  DSG:  A
      * DS NAME: dataset_name
      ***********************************************
      * THE ILDS MUST BE REBUILT FOR THIS PARTITION *
      ***********************************************


      This indicator notifies the HALDB partition whose indirect list data sets (ILDSs) must be rebuilt. Locate all the indicators in the reports and make a list of the partitions whose ILDSs must be rebuilt. You will use this list in the subsequent repair process.

    What to do next
    Continue with the repair procedure described in the topic "Repairing HALDB partition reorganization numbers and duplicate ILKs" in the IMS High Performance Pointer Checker User's Guide. End of change


Start of change x.1.2 ILK Repair utility reports

The ILK Repair utility generates the Control Statements and Messages reports in the SYSTSPRT and the SYSPRINT data sets.

The report in the SYSTSPRT data set contains the result of the job, and when OSAM data sets are processed, it also contains the process logs and messages that are issued during the job. The report in the SYSPRINT data set is generated only when VSAM data sets are processed, and it contains the process logs and messages issued during the job.

    SYSTSPRT data set
    The following figure shows an example of the report.



    SYSPRINT data set
    The following figure shows an example of the report.

    End of change
==================================
> 5.0 Messages and codes of IMS Database Repair Facility
>> 5.2 Messages

The following new messages have been added:

Start of change
FABZ800I DBRF ENDED NORMALLY
Explanation: The ILK Repair utility ended successfully.
System action: The ILK Repair utility ends with a return code of 0.
User response: None. This message is informational.
End of change
------
Start of change
FABZ801E ddname DD WAS NOT FOUND
Explanation: The indicated DD statement must be supplied but was not found in the JCL stream.
System action: The ILK Repair utility ends with a return code of 20.
User response: See "Running the ILK Repair utility" to learn how to code the required DD statement. Rerun the job.
End of change
------
Start of change
FABZ802E SPECIFIED FABZIN DATA SET IS INVALID
Explanation: An incorrect data set is specified on the FABZIN DD statement. The FABPILK data set that was created by the HD Pointer Checker utility must be specified on the FABZIN DD statement.
System action: The ILK Repair utility ends with a return code of 20.
User response: Specify the correct data set to the FABZIN DD statement and then rerun the job.
End of change
------
Start of change
FABZ803E ZAP FAILED FOR [OSAM | VSAM] DATA SET RC= rc
Explanation: The ILK Repair utility failed to update an OSAM or VSAM data set.
System action: The ILK Repair utility ends with the indicated return code.
User response: Locate the messages that explain the error in the Control Statements and Messages report. The report is generated in the SYSTSPRT data set for OSAM data sets, and in the SYSPRINT data set for VSAM data sets.
End of change
------
Start of change
FABZ804E DBRF ENDED WITH ERRORS
Explanation: The ILK Repair utility encountered errors.
System action: The ILK Repair utility ends with a return code of 20.
User response: Locate the messages that explain the error in the Control Statements and Messages reports. Correct the errors and then rerun the job.
End of change
------
Start of change
FABZ805E [ALLOCATION | UNALLOCATION] FAILED FOR ddname DD, DATA SET DSNAME= data_set_name
Explanation: The ILK Repair utility failed to allocate the indicated data set to the indicated DD statement, or failed to unallocate the indicated data set from the indicated DD statement.
System action: The ILK Repair utility ends with a return code of 20.
User response: For an allocation failure of the database data set, ensure that the data set is cataloged and is not used by other jobs or users. For an unallocation failure, release the data set from the DD statement.
End of change
------
Start of change
FABZ806E MEMBER member_name NOT FOUND IN DATA SET DSNAME= data_set_name
Explanation: The indicated member is not found in the indicated data set. The indicated data set is either smphlq.SFABLMD0 or smphlq.SFABCLIB, where smphlq is the parameter that you specified on the SYSTSIN DD statement.
System action: The ILK Repair utility ends with a return code of 20.
User response: Specify the correct smphlq parameter in the SYSTSIN DD statement and then rerun the job.
End of change
------
Start of change
FABZ807E DELETE FAILED FOR DATA SET DSNAME= data_set_name
Explanation: The ILK Repair utility could not delete the indicated data set.
System action: The ILK Repair utility ends with a return code of 20.
User response: Delete the data set and then rerun the job.
End of change
------
Start of change
FABZ808I ZAP FOR THE DATA SET ENDED WITH RC= rc
Explanation: This message indicates the return code for each OSAM data set that is processed.
System action: Processing continues.
User response: If the return code is not zero, locate the preceding error messages in the Control Statements and Messages report in the SYSTSPRT data set.
End of change
------
Start of change
FABZ0013I ZAP FOR THE DATA SET ENDED WITH RC= rc
Explanation: This message indicates the return code for each VSAM data set that is processed.
System action: Processing continues.
User response: If the return code is not zero, locate the preceding error messages in the Control Statements and Messages report in the SYSPRINT data set.
End of change


Update 10
Date of change: December 2013
Change description: User's guide updates.
Topics: Changes apply to the following multiple topics.

> 1.0 IMS Database Repair Facility overview
>> 1.3 Supported databases

The following description has been corrected:

IMS Database Repair Facility, when run interactively, supports:
  • ...
  • Fast Path DEDBs. The DEDB data sets can be defined in your dynamic allocation library or in the RECON data sets using the INIT.DBDS and INIT.ADS records.
    Start of changeNote: IMS Database Repair Facility does not support Fast Path secondary index databases and Fast Path DEDBs with Fast Path secondary index databases.End of change

==================================
> 3.0 Using IMS Database Repair Facility in batch mode for VSAM
>> 3.2 Operating instructions
>>> 3.2.3 Job control language

The title of the following example has been changed:


//         EXEC   PGM=FABZVZAP                      
//STEPLIB  DD     DSN=smphlq.SFABLMD0,DISP=SHR      
//SYSLIB   DD     DSN=DBT.VSAM,DISP=SHR              
//SYSPRINT DD     SYSOUT=A                          
//SYSIN    DD     *                                  
    (control statements)                            
/*                              

Start of changeFigure 38. JCL example for Batch IMS Database Repair Facility for VSAM End of change

==================================
> 4.0 Using IMS Database Repair Facility in batch mode for OSAM
>> 4.2 Operating instructions
>>> 4.2.3 Job control language

The following figure and the title of the figure have been updated:

SYSIN DD
    This statement defines the input data set that contains your control statements.


    //DBRFOBT4 JOB (installation accounting information)                
    //*                                                                
    //BATCHTSO EXEC PGM=IKJEFT1B,DYNAMNBR=25,REGION=0M,COND=EVEN        
    //*                                                                
    //SYSLIB   DD DISP=OLD,DSNAME=DBT.HPPC.DB.DSFACHO0                  
    //SYSEXEC  DD DISP=SHR,DSN=DBT.DBRUT.FABZ110G.SFABCLIB              
    //*                                                                
    //ISPPLIB  DD DISP=SHR,DSN=SPF.PRODUCT.ISPPLIB                      
    //ISPMLIB  DD DISP=SHR,DSN=SPF.PRODUCT.ISPMLIB                      
    //ISPSLIB  DD DISP=SHR,DSN=SPF.PRODUCT.ISPSLIB                      
    //ISPTLIB  DD DISP=SHR,DSN=SPF.PRODUCT.ISPTLIB                      
    //ISPLOG   DD SYSOUT=*,DCB=(
    LRECL=125,BLKSIZE=129,RECFM=VA)        
    //ISPPROF  DD DSN=&TEMP1,DISP=(NEW,PASS),UNIT=SYSALLDA,            
    //         SPACE=(CYL,(3,10,15)),DCB=(LRECL=80,BLKSIZE=3120,RECFM=FB)
    //SYSTSPRT DD SYSOUT=*                                              
    //* 3RD LINE IN SYSTSIN. SMPHLQ UHLQ PID DBG                        
    //SYSTSIN  DD *                                                    
     PROFILE PREFIX(DBT)                                              
     ISPSTART CMD(FABZOSMB  -                                          
     DBT.DBRUT.FABZ
    310G DBT FABZ  )                                    
    /*                                                                  
    //SYSIN    DD *                                                    
     OBLK 2                                                            
     DUMP                                                              
     VER 0020 F9C3C4E9                                                
     VER 0024 C2C3D9C4                                                
     REP 0020 F9C4C4E9                                                
     REP 0024 C2C4D9C4                                                
     DUMP                                                              
    /*    

                             
    Start of changeFigure 47. JCL example for Batch IMS Database Repair Facility for OSAM End of change

----------------------------------
>> 4.4 SYSTSPRT data set
>>> 4.4.1 Control Statements and Messages report

Figure "Example of repairing an OSAM data set" (Figure 48) has been moved from 4.4.2 "Control statements to repair and dump an OSAM data set" to this topic. Also, the figure has been updated as follows:

Start of changeThe following figure shows an example of a Control Statements and Messages report. End of change

Start of changeFigure 48. Control statements and messages report End of change

----------------------------------
>>> 4.4.2 Control statements to repair and dump an OSAM data set

Figure " Example of repairing an OSAM data set" (Figure 48) has been removed from this topic and the description has been updated as follows:

Start of changeFigure 47 provides an example of control statements to repair and dump an OSAM data set. End of change

==================================
> 5.0 Messages and codes of IMS Database Repair Facility
>> 5.2 Messages

The following messages have been updated as follows:

Start of change FABZ901I FABZ901I VER WORKED. End of change
Explanation: The verify action, as requested by the VER input record, worked.
System action: None.
User response: None.

------
Start of change FABZ902I FABZ902I REP WORKED. End of change
Explanation: The replace action, as requested by the REP input record, worked.
System action: None.
User response: None.

------
Start of change FABZ910E MISSING REQUIRE D PARAMETERS. SMPHLQ,UHLQ,PID End of change
Explanation: Start of changeThese parameters (SMPHLQ, UHLQ, and PID) are required in the SYSTSIN data set in JCL. End of change
System action: Batch Repair for OSAM terminates with return code 20.
User response: Start of changeSpecify these required parameters. For more information about these parameters, see 4.2.3 "Job control language". End of change

------
Start of change FABZ911E DATASET NOT FOUND, text1 text2 End of change
Explanation: A data set was not found, text1 is the data set name.
System action: Batch Repair for OSAM terminates with return code 20.
User response: Start of change text2 might contain some diagnostic information, for example, if the data set name includes an execution parameter, like SMPHLQ, text2 will note this. User should check and correct the parameter. If this is not the case, specify DBG parameter = 1 in the SYSTSIN data set in JCL and rerun the job. Then, send the entire job output to IBM. End of change



Update 9
Date of change: February 2013
Change description: Documentation changes by APAR PM83096. By applying this APAR, you can specify the library that contains a HALDB partition selection exit routine on the Specify Libraries panel and the Update libraries panel.
Topics: Changes apply to the following multiple topics.

> 2.0 Using IMS Database Repair Facility interactively
>> 2.6 Set up IMS environment
>>> 2.6.2 Specify libraries

Part. Selection exit library field has been added to the Specify libraries panel as follows:

The Specify Libraries panel, Figure 3, is used to specify the libraries needed by IMS Database Repair Facility to access your database.

This panel displays after you make your selection on the Set up IMS system ID panel, (Figure 2).

Figure 3. Specify libraries panel (FABZP01)

When this panel is initially displayed, no RECON data sets are shown.

The fields on this panel are:
...
Start of change Randomizer l ibrary End of change
    ...
Start of change Part. Selection exit library
    Specify the name of the library containing the HALDB Partition Selection exit routine. End of change
DBD library
    ...

----------------------------------
>> 2.7 View/update database
>>> 2.7.3 Update libraries

Update libraries panel for HALDB databases (FABZP02) has been added:

Start of changeWith the Update libraries panel, Figure 6 or Figure x, you can override the IMS data set names associated with this database. Initially, the default library names are those you specified on the Specify libraries panel, Figure 3. If you change the library names on this panel, the new names become the default library names for this database until you modify them again. End of change

If the database is not contained in the dynamic allocation library, you can also specify the name of a data set containing a list of DD names and the data set names associated with the database.


Start of changeFigure 6. Update libraries panel for non-HALDB databases (FABZP02) End of change


Start of changeFigure x. Update libraries panel for HALDB databases (FABZP02) End of change

The fields on this panel are:
...
Randomizer load library
    ...
Start of change Part. Selection exit library
    Modify the name of the library containing the HALDB Partition Selection exit routine. This field is displayed only for HALDB databases. End of change
DBD library
    ...

----------------------------------
>>> 2.7.5 Processing HD or DEDB databases

PSE Name field has been added to the Initial selection panel as follows:

Initial selection panel for PHDAM and PHIDAM databases

If the database you specified is partitioned, that is, a PHDAM or PHIDAM database, the Initial selection panel for PHIDAM and PHDAM databases panel, Figure 9, is displayed rather than the Initial selection panel for HDAM, HIDAM and DEDB databases, Figure 8. You enter more information on this panel that is used to identify the segment you want displayed.

This panel also provides you with the option to have the FSE chain or root anchor points displayed.


Figure 9. Initial selection panel for PHIDAM and PHDAM databases (FABZPS1P)

The fields on this panel are:
...
DB organization
    ...
Start of change PSE Name
    Shows the name of the HALDB Partition Selection exit routine. If the HALDB database that you specified does not use a HALDB Partition Selection exit routine, **NULL** is displayed. End of change
Access method
    ...

----------------------------------
>>> 2.7.6 Processing HISAM, SHISAM, INDEX, Secondary Index (SINDEX), and Partitioned Secondary Index (PSINDEX) databases

PSE Name field has been added to the Initial selection panel as follows:

Initial selection panels

PSIndex database: If the database you specified is a partitioned secondary index database, Figure 22 is displayed. Enter the key to access the segment you want to display.


Figure 22. Initial selection panel for partitioned secondary index databases (FABZPS1X)


The fields on these panels are:
DBD name
    ...
Start of change PSE Name
    Shows the name of the HALDB Partition Selection exit routine. If the database that you specified does not use a HALDB Partition Selection exit routine, **NULL** is displayed. End of change
DB organization
    ...



Update 8
Date of change: February 2013
Change description: User's Guide update.
Topic:
> 2.0 Using IMS Database Repair Facility interactively
>> 2.7 View/update database
>>> 2.7.5 Processing HD or DEDB databases

The following description has been changed:

Initial selection panel for HDAM, HIDAM, and DEDB databases
...

FSE chain
    ...
RAPs
    Start of changeSpecify Y to see the Root anchor points associated with the HDAM or HIDAM database. For HIDAM databases, this field is displayed only if RAPs exist in the database. End of change



Update 7
Date of change: December 2012
Change description: User's Guide update.

Topic:
> 5.0 Messages and codes of IMS Database Repair Facility
>> 5.2 Messages

The following message has been added:

Start of change
FABZ056W No available datasets for this DBD

Explanation: When IMS Database Repair Facility is used for a DEDB database interactively, IMS Database Repair Facility checks with the RECON data sets whether the area data sets of the database are in available status. This message indicates that none of the area data sets of the database are in available status in the RECON data sets.
System Action: Processing is halted.
Problem Determination: None.
User Response: See "General note on DEDB database usage" on page xx. Then follow these steps:
  • Examine the RECON data sets and ensure that the area data sets of the database are in available status. If the area data sets are in unavailable status, issue CHANGE.ADS commands to change the status of the area data sets.
  • If you specified the dynamic allocation library to supply the names of the area data sets (Update Libraries panel), ensure that the dynamic allocation library contains the correct dynamic allocation members for the database areas.
End of change




Update 6
Date of change: May 2012
Change description: User's Guide update.

Topic:
> 1.0 IMS Database Repair Facility overview
>> 1.3 Supported databases

The following restriction item has been added:

Start of changeRestriction: IMS Database Repair Facility does not support IMS catalog databases. End of change





Update 5
Date of change: May 2011
Change description: User's Guide update.

Topic:
> 1.0 IMS Database Repair Facility overview
>> 1.3 Supported databases

IMS Database Repair Facility, when run interactively, supports:
  • Hierarchical Direct (HDAM), Hierarchical Indexed Direct (HIDAM) and Hierarchical Indexed Sequential (HISAM) databases using VSAM or OSAM access methods
  • HALDB partitioned hierarchical direct (PHDAM), partitioned hierarchical index direct (PHIDAM) and partitioned secondary index (PSINDEX) databases using VSAM or OSAM access methods
  • Nonpartitioned HIDAM index and secondary index databases
  • Start of changeFast Path DEDBs that reside in a single address space . The DEDB data sets can be defined in your dynamic allocation library or in the RECON data sets using the INIT.DBDS and INIT.ADS records.
    Note: IMS Database Repair Facility does not support Fast Path secondary index databases.End of change





Update 4
Date of change: May 2011
Change description: User's Guide correction.

Topic:
> 2.0 Using IMS Database Repair Facility interactively
>> 2.7 View/update database
>>> 2.7.5 Processing HD or DEDB databases
>>>> 2.7.5.10 Display segment data in character and hex format

The following description is corrected:

>4G
    An N indicates that the segment is in the first 4 gigabytes of the database.
    Start of changeA N Y indicates that the segment is in the second 4 gigabytes of a non-partitioned OSAM database. End of change




Update 3
Date of change: November 2010
Change description: Updates to the user's guide
  • Compatibility with the former product, IMS Database Repair Facility Version 1 Release 2
  • Functional enhancements
  • JCL example for batch mode for OSAM

Topic:
> 1.0 IMS Database Repair Facility overview

The following topics are added:

Start of change Compatibility with IMS Database Repair Facility Version 1 Release 2

The JCLs, procedures, and input control statements that are used in IMS Database Repair Facility Version 1 Release 2 can be used with the Database Repair Facility that is provided in IMS HP Pointer Checker, IMS Database Solution Pack, and IMS Fast Path Solution Pack. End of change

Start of change Functional enhancements

The following functions have been enhanced in the Database Repair Facility that is distributed within IMS HP Pointer Checker, IMS Database Solution Pack, and IMS Fast Path Solution Pack:
  • The CHECK control statement has been introduced for batch mode. This new control statement enables the Database Repair Facility to check if the syntax of the control statements is correct and whether the values that are specified on the control statements, such as keys or RBAs, are valid. When the CHECK control statement is specified, the Database Repair Facility does not update data sets.
  • The Database Repair Facility has been enhanced to prevent you from changing a data set beyond EOF when you run the Database Repair Facility in interactive mode.End of change

==================================
> 4.0 Using IMS Repair Facility in batch mode for OSAM
>> 4.2 Operating instructions
>>> 4.2.3 Job control language

Figure "Batch IMS database Repair Facility control statements" is replaced with the following figure:


Figure 47. Batch IMS Database Repair Facility control statements





Update 2
Date of change: August 2010
Change description: Update 2 includes documentation changes by APAR PM18995, which is for the IMS Database Repair Facility.

Topic:
> 1.0 IMS Database Repair Facility overview
>> 1.6 Restrictions of IMS Database Repair Facility

The following description, which has been added by Update 1 of this techdoc, is now deleted:

Restrictions for OSAM data sets that are lager than 4 GB
    When the Repair Facility is used interactively, it can process data that is located between 4 GB and 8 GB. However, you cannot specify data that is beyond 4 GB by using the BLK# option. To specify data beyond 4 GB, use the RBA or the Root Key option. For more information for specifying the RBA that is beyond 4 GB, see "2.7.5.2 Initial selection panel for HDAM, HIDAM, and DEDB databases".

    When the Repair Facility is used in batch mode, it does not support data that is located between 4 GB and 8 GB.

==================================
Topic:
> 2.0 Using IMS Database Repair Facility interactively
>> 2.7 View/update database
>>> 2.7.5 Processing HD or DEDB databases

The description for RBA is changed as follows:

RBA
    You can specify the relative byte address with which to access a database segment. You can access any segment provided the RBA points to a valid segment code.

    To display an individual segment, the RBA must point to a valid segment code. For any other RBA, the Repair Facility displays the block containing that RBA.

    Start of changeWhen the database is HDAM or HIDAM and the database data set is an OSAM with an even block size, the maximum database size can be 8 GB.

    The RBA beyond 4 GB for the OSAM database data set can be specified in hexadecimal by the following expressions:
    • Nine digit value (the maximum value is X'1FFFFFFFF')
    • Eight digit value, the RBA value by incrementing the last bit by 1. In this way, IMS Database Repair Facility assumes the value is over 4 GB for the even-block size OSAM. (the maximum value is X'FFFFFFFF')

    For example, to specify 4294968320, you can use the following nine or eight digits:
    • Nine digits: 100000400
    • Eight digits: 00000401

    Note: Nine digit RBA is used only at the time you enter the value. Even if you enter a nine digit value, the RBA value is displayed in eight digits on the panels and messages. End of change

==================================
Topic:
> 4.0 Using IMS Repair Facility in batch mode for OSAM
>> 4.3 SYSIN data set
>>> 4.3.3 ORBA control statement

The description for record-rba is changed as follows:

record-rba
    The relative byte address of the OSAM record. It can be specified as either of the following expressions:
    • Start of changeA decimal expression (for example, 4096). The allowable maximum value is 8589934591.End of change
    • Start of changeA hexadecimal expression (for example, X'1000'). The allowable maximum value is X'1FFFFFFFF'. End of change
    • Start of changeWhen the database is HDAM or HIDAM and the database data set is an OSAM with an even block size, the maximum database size can be 8 GB.
      The RBA beyond 4 GB for the OSAM database data set can be specified in hexadecimal by the following expressions: 
      • Nine digit value (the maximum value is X'1FFFFFFFF')
      • Eight digit value, the RBA value by incrementing the last bit by 1. In this way, IMS Database Repair Facility assumes the value is over 4 GB for the even-block size OSAM. (the maximum value is X'FFFFFFFF')

      For example, to specify 4294968320, you can use the following nine or eight digits:
      • Nine digits: 100000400
      • Eight digits: 00000401
      Note: Nine digit RBA is used only at the time you enter the value. Even if you enter a nine digit value, the RBA value is displayed in eight digits on the reports and messages. End of change


The following note, which has been added by Update 1 of this techdoc, is now deleted:

Note: This control statement does not support data that is located over 4GB. Use the IMS Database Repair Facility interactively to process the data of an OSAM data set that is located between 4 GB and 8 GB.

==================================
Topic:
>>> 4.3.4 OBLK control statement

The following description is deleted:
  • A hexadecimal expression that consists of an even number of digits (for example, X'1000'). A leading zero must be added to an odd number of digits (for example, X'010B00'). The allowable maximum value is X'FFFFFFFF'.




Update 1
Date of change: May 2010
Change description: This update includes the documentation changes to complement the operational description.

Topic:
> 1.0 Introduction
>> 1.6 Restrictions of IMS Database Repair Facility

This section is changed as follows:

Start of changeRestrictions for compressed data

When the IMS Database Repair Facility is used interactively, it does not support the repair of compressed data. In addition, IMSPLEX is only supported through the use of the DSPSCIX0 exit in the RESLIB. End of change

When running the IMS Database Repair Facility in batch mode to access a compressed data set,
  • You cannot perform any Repair Facility function using the relative byte address of the control interval on the CNV Control statement.
  • You cannot perform the Replace function using the relative byte address of the VSAM record on the RBA control statement.

Note: You can perform all batch Repair Facility functions -- Verifying, Replacing, and Dumping -- using the fully qualified key of the VSAM record on the KEY control statement.


Start of changeRestrictions for IMSPLEX End of change

IMSPLEX is only supported through the use of the DSPSCIX0 exit in the RESLIB.


Start of changeRestrictions for OSAM data sets that are lager than 4 GB

When the IMS Database Repair Facility is used interactively, it can process data that is located between 4 GB and 8 GB. However, you cannot specify data that is beyond 4 GB by using the BLK# option. To specify data beyond 4 GB, use the RBA or the Root Key option. For more information for specifying the RBA that is beyond 4 GB, see "2.7.5.2 Initial selection panel for HDAM, HIDAM, and DEDB databases".

When the IMS Database Repair Facility is used in batch mode, it does not support data that is located between 4 GB and 8 GB. End of change

==================================
Topic:
> 2.0 Using IMS Database Repair Facility interactively
>> 2.7 View/update database
>>> 2.7.5 Processing HD or DEDB databases

The description for RBA is changed as follows:

Initial selection panel for HDAM, HIDAM, and DEDB databases

RBA
    You can specify the relative byte address with which to access a database segment. You can access any segment provided the RBA points to a valid segment code.

    To display an individual segment, the RBA must point to a valid segment code. For any other RBA, the Repair Facility displays the block containing that RBA.

    Start of changeFor an OSAM HD database, if you want to process data that is located between 4 GB and 8 GB, enter the RBA value by incrementing the last bit by 1. In this way, IMS Database Repair Facility assumes the value is over 4 GB.

    For example:
    • In case of X'1 0000 0800' (lager than 4 GB), enter 00000801 in the RBA field. IMS Database Repair Facility displays the data at RBA X'1 0000 0800'.
    • In case of X'1 FFFF FFFE' (smaller than 8 GB), enter FFFFFFFF. IMS Database Repair Facility displays the data at RBA X'1 FFFF FFFE'.End of change

==================================
Topic:
> 4.0 Using IMS Database Repair Facility in batch mode for OSAM
>> 4.3 SYSIN data set
>>> 4.3.3 ORBA control statement

A note is added as follows:

    ORBA record-rba

Operand Description
ORBA Control statement identifier. It must be coded as shown.

This statement specifies the position of the physical record in one OSAM data set to be verified or changed.
record-rba The relative byte address of the OSAM record. It can be specified as either of the following expressions:
  • A decimal expression (for example, 4096). The allowable maximum value is 4294967295.
  • A hexadecimal expression that consists of an even number of digits (for example, X'1000'). A leading zero must be added to an odd number of digits (for example, X'0100'). The allowable maximum value is X'FFFFFFFF'.
Start of changeNote: This control statement does not support data that is located over 4GB. Use IMS Database Repair Facility interactively to process the data of an OSAM data set that is located between 4 GB and 8 GB.End of change

Publication number

SC19-2916-00

Copyright date

2000, 2010

Original publication date

2010/5/14

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

IMS Tools
IMS Database Repair Facility for IMS Solution Packs

Software version:

1.0.0

Operating system(s):

z/OS

Reference #:

7018784

Modified date:

2014-07-09

Translate my page

Machine Translation

Content navigation