PI27564: SUPPORT FOR IMS V14

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• Support for IMS V14
  KEYWORDS: IMSV14TGT/K IMSV13TGT/K
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: IBM IMS Database Repair Facility (DBRF) for  *
  *                 z/OS Version 3 Release 1 (FMID=H22K310)      *
  *                 users who use IMS Version 14.                *
  ****************************************************************
  * PROBLEM DESCRIPTION: This APAR adds IMS V14 support and IMS  *
  *                      V14 and V13 HALDB OSAM 8GB data set     *
  *                      support to DBRF V3.1.                   *
  ****************************************************************
  * RECOMMENDATION: Apply the maintenance for this APAR.         *
  ****************************************************************
  DBRF has been modified to support IMS Version 14 and IMS Version
  14 HALDB OSAM 8GB data sets.
  
  *** Note ***
  - When you use the ILK Repair utility to repair HALDBs that are
    used under IMS Version 14 environment, you need to apply APAR
    PI27563 to IMS High Performance Pointer Checker V3.1.
  
  
  Additionally, this APAR fixes the following problems that are
  caused when you run DBRF in interactive mode and try to process
  an HDAM or HIDAM database whose data set is a OSAM data set with
  an even-length block size:
  
  1. DBRF displays incorrect data in the RAP Pointers panel when
     the relative byte address (RBA) beyond 4 GB and the RAPs
     option are specified in the Initial selection panel.
  2. DBRF displays incorrect data in the Free Space Element Chain
     panel when the relative byte address (RBA) or block number
     beyond 4 GB and the FSE chain option are specified in the
     Initial selection panel.
  

Problem conclusion

Temporary fix

Comments

• Documentation Changes:
  Note: The Chapter numbers are those of the PDF file.
  The documentation is modified as follows:
  ==============================================================
    IMS Database Repair Facility for IMS Solution Packs
    User's Guide (SC19291601)
  ==============================================================
  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
  Chapter 2. Repairing IMS databases in interactive mode
  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
  --------------------------------------------------------------
  - Viewing and updating the database
    - Viewing and updating an HD or DEDB database
  --------------------------------------------------------------
  <<The description of step 3 in the procedure is changed:>>
  Procedure
  The Initial selection panel differs by database organization
  type.
  1 ...
  2 ...
  3 Enter one of the following fields to display the information
    about a specific segment, block, or CI.
    RBA
     Specify the relative byte address (RBA) used for accessing a
     database segment.
     :
     If the database is an HDAM or HIDAM and the database data set
  |  is OSAM with even block size or if the database is a PHDAM or
  |  PHIDAM that is registered in the RECON data sets as a
  |  database that supports up to 8 gigabytes of data, the maximum
     database size can be 8 GB.
     :
  --------------------------------------------------------------
      - Viewing and updating segment prefix
  --------------------------------------------------------------
  <The following description is changed:>
  >4G
   N Indicates that the segment is in the first 4 GB of the
     database.
  |Y Indicates that the segment is in the second 4 GB of an OSAM
     database.
  :
  >4G
   N Indicates that the Tgt-RBA is in the first 4 GB of the
     database.
  |Y Indicates that the Tgt-RBA is in the second 4 GB of an OSAM
     database.
  
  --------------------------------------------------------------
      - Viewing and updating segment data
  --------------------------------------------------------------
  <The following description is changed:>
  >4G
   N Indicates that the segment is in the first 4 GB of the
     database.
  |Y Indicates that the segment is in the second 4 GB of an OSAM
     database.
  
  --------------------------------------------------------------
      - Viewing and updating FSEAP and FSE chain within block or
        CI
  --------------------------------------------------------------
  <The following description is changed:>
  >4G
   N Indicates that the source RBA is in the first 4 GB of the
     database.
  |Y Indicates that the source RBA is in the second 4 GB of an
     OSAM database.
  
  --------------------------------------------------------------
      - Viewing and updating RAP pointers within block or CI
  --------------------------------------------------------------
  <The following description is changed:>
  >4G
   N Indicates that the source RBA is in the first 4 GB of the
     database.
  |Y Indicates that the source RBA is in the second 4 GB of an
     OSAM database.
  
  --------------------------------------------------------------
  - Viewing audit history of processed segments
  --------------------------------------------------------------
  <The following description is changed:>
  >4G
   N Indicates that the segment is in the first 4 GB of the
     database.
  |Y Indicates that the segment is in the second 4 GB of an OSAM
     database.
  
  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
  Chapter 4. Repairing OSAM data sets in batch mode
  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
  --------------------------------------------------------------
  - SYSIN data set
    - ORBA control statement
  --------------------------------------------------------------
  <<The following description is changed:>>
  record_rba
   :
   If the database is an HDAM or HIDAM and the database data set
  |is OSAM with even block size or if the database is a PHDAM or
  |PHIDAM that is registered in the RECON data sets as a database
  |that supports up to 8 gigabytes of data, the maximum database
  size can be 8 GB.
  
  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
  Chapter 6. Troubleshooting
  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
  --------------------------------------------------------------
  - IMS Database Repair Facility messages
  --------------------------------------------------------------
  <<The following messages are added:>>
  FABZ102W: Specify an even value for the RBA because this HALDB
  is registered in RECON as DSORG=OSAM and the active DBDS is an
  A-side data set.
  Explanation: This database that you tried to process is
  registered in RECON as DSORG=OSAM, that is, is a HALDB that
  supports up to 4 gigabytes of data, and the active DBDS is an
  A-side data set. In such databases, you need to specify an even
  value for the RBA. But you specified an odd value for the RBA.
  System Action: Processing is halted until the error is
  corrected.
  User Response: Specify an even value for the RBA.
  
  FABZ103W: The selected pointer must have an even value for the
  RBA because this HALDB is registered in RECON as DSORG=OSAM and
  the active DBDS is an A-side data set. Correct the RBA so it
  contains an even value.
  Explanation: This database that you tried to process is
  registered in RECON as DSORG=OSAM, that is, is a HALDB that
  supports up to 4 gigabytes of data, and the active DBDS is an
  A-side data set. In such databases, pointers must contain an
  even values. But the pointer that you selected contains an odd
  value.
  System Action: Processing is halted until the error is
  corrected.
  User Response: Correct the RBA so it contains an even value.
  
  FABZ104W: The specified RBA points to a location beyond the
  maximum size of this DBDS. Because this DBDS is xxx, the maximum
  size is nGB. Specify a valid RBA within the DBDS.
  Explanation: The specified RBA points to a location beyond the
  maximum size of this database data set. You must specify an RBA
  within the DBDS. The maximum size of a database data set is:
  - 4GB for a VSAM data set
  - 4GB for a non-HALDB OSAM data set with an odd block size
  - 8GB for a non-HALDB OSAM data set with an even block size
  - 4GB for an OSAM data set of a HALDB that is registered as
    DSORG=OSAM in RECON
  - 8GB for an OSAM data set of a HALDB that is registered as
    DSORG=OSAM8G in RECON
  System Action: Processing is halted until the error is
  corrected.
  User Response: Specify a valid RBA within the database data set.
  
  FABZ105E: This HALDB is registered in RECON as DSORG=OSAM8G. But
  the active DBDS is an M-side data set.
  Explanation: This database that you tried to process is
  registered in RECON as DSORG=OSAM8G, that is, is a HALDB that
  supports up to 8 gigabytes of data. But the active database data
  sets of this database are M-side data sets. There is an
  inconsistency in the RECON data sets.
  System Action: Processing is halted until the error is
  corrected.
  User Response: Specify the correct RECON data sets.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UI24021

Modules/Macros

• FABZDATA FABZMAIN FABZPROC FABZPRO2 FABZPS1P
  FABZPS7  FABZ10
  

Fix information

• Fixed component name

  IMS DATABASE RE

• Fixed component ID

  5655E0300

Applicable component levels

• R310 PSY UI24021

     UP14/12/20 P F412

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.