PI16840: FORWARD FIT ORF V1.3 APARS TO DBSP V2.1 ORF

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• Forward fit ORF V1.3 APARs to DBSP V2.1 ORF
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of IBM IMS Database Solution Pack V2.1 *
  *                 IMS Online Reorganization Facility           *
  ****************************************************************
  * PROBLEM DESCRIPTION: Forward fit of fix in ORF V1.3 APAR     *
  *                      PI13112, PI09890, PI15987, PI20268 and  *
  *                      PI18538.                                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  This APAR fixes the following problems:
  
   1.Even when the OPTID keyword is specified, some of
     configuration parameters are not read from the configuration
     module specified by the OPTID keyword.
     This problem applies to the following parameters: FEOV,
     ILDSDSPR, DFDSS.
  
   2.This APAR adds support for the new LOGICALDBD keyword. This
     keyword is used to specify the names of the logical DBDs
     that are defined to the physical database specified by the
     DBD keyword.
     Specify this keyword only if you have applications that
     update the database during the reorganization process by
     using a PCB that references a logical DBD.
  
   3.When the reorganized database is non-recoverable PSINDEX
     with multiple partitions, ORF tries to make the index
     recoverable without stopping all partitions, which usually
     fails with the following error: DSP1095A DATABASE dbname
     IS AUTHORIZED.
  
   4.When the main processing abended in HRFOREO2 module, the
     cleanup processing tries to call the HRFOREO2 module again
     and gets another S0C4 abend, which causes the job not to
     end.
  
   5.HP Unload V1.2 APAR PI19021 (PTF UI19112) enables HP Unload
     API to support the HSSROPT DECN control statement under ORF.
     This APAR modifies ORF to dynamically allocate HSSROPT DD
     and automatically specify DECN control statement when
     appropriate. When HP Unload does not have APAR PI19021
     applied, HP Unload just ignores the DECN statement in the
     HSSROPT DD.
  

Problem conclusion

Temporary fix

Comments

• ========================
  = DOCUMENTATION CHANGE =
  ========================
  IBM IMS Database Solution Pack for z/OS Version 2 Release 1
  IMS Online Reorganization Facility User's Guide (SC19-4103-00)
  ----------------------------------------------------------------
  Chapter 2. Using IMS Online Reorganization Facility
   HRFSYSIN DD statement
    HRFSYSIN DD statement keywords
  :
  
    Table 3. HRFSYSIN DD statement keyword
    +----------+------------+--------------+---------------------+
    |Keyword   |REORG       |UNLOAD        |Link to topic        |
    |          |HRFSYSIN DD |HRFSYSIN DD   |                     |
    +----------+------------+--------------+---------------------+
    |DATACLAS  |Optional    |Not applicable|"DATACLAS keyword"   |
    +----------+------------+--------------+---------------------+
        :          :             :                 :
    +----------+------------+--------------+---------------------+
    |LOG2DSN   |Optional    |Not applicable|"LOG2DSN keyword"    |
    +----------+------------+--------------+---------------------+
  ADD:
  | |LOGICALDBD|Optional    |Not applicable|"LOGICALDBD keyword" |
  | +----------+------------+--------------+---------------------+
  ADD:
        :
  ADD:
  | LOGICALDBD keyword
  | Use this keyword to specify the names of the logical DBDs that
  | are defined to the physical database specified by the DBD
  | keyword.
  |
  | Specify this keyword only if you have applications that update
  | the database during the reorganization process by using a PCB
  | that references a logical DBD. You can specify up to five
  | logical DBD names.
  |
  | This keyword is optional for REORG HRFSYSIN DD statements, but
  | is not applicable for UNLOAD HRFSYSIN DD statements.
  |
  | Format
  |  (dbdname1 ,dbdname2 ,dbdname3 ,dbdname4 ,dbdname5     )
  |
  | Default value
  |  None.
  ADD:
  
  Chapter 5. Troubleshooting
   Messages and codes
    Messages
  ADD:
  |
  | HRF01181E Logical DBD dbdname is invalid
  |
  | Explanation: The indicated logical DBD does not reference the
  | database that is specified by the DBD keyword.
  | System action: Processing terminates.
  | User response: Ensure that the indicated logical DBD is
  | defined to the database that you are reorganizing.
  |
  ADD:
        :
  ADD:
  |
  | HRF01573E Logical DBD dbdname is not specified by the
  | LOGICALDBD keyword
  | Explanation: The database was updated by using a PCB that
  | references the indicated logical DBD, but the logical DBD is
  | not specified by the LOGICALDBD keyword.  Any logical DBD that
  | applications use for update during the reorganization must be
  | specified with the LOGICALDBD keyword.
  | System action: Processing terminates.
  | User response: Specify the logical DBD by using the LOGICALDBD
  | keyword.
  |
  | HRF01574E DBD dbdname has insert, delete, or replace rules
  | that are not supported
  | Explanation: Unsupported path type is specified in the insert,
  | delete, or replace rules of the indicated DBD.  For HALDB
  | databases that have internal logical relationships, the
  | following restrictions apply to the insert, delete and replace
  | rules. The rules are specified by using the RULES= keyword of
  | a SEGM statement in the physical DBD.
  | - Insert rules L and V are not supported for logical parents.
  |   Only the P insert rule is supported.
  | - Delete rules L and V are not supported for logical parents.
  |   Only the P deletion rule is supported.
  | - Replace rule V is not supported for logical parents.
  | No restrictions apply to the insert, delete, and replace rules
  | of full-function databases.
  | System action: Processing terminates.
  | User response: None. You cannot use IMS Online Reorganization
  | Facility to process a HALDB DBD with such rules.
  |
  ADD:
  ×**** PE14/08/11 FIX IN ERROR. SEE APAR PI23627  FOR DESCRIPTION
  

APAR Information

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

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

  UI19354

Modules/Macros

• HAHP210J HRFDBUX1 HRFFLGX0 HRFOAPLY HRFOAPL0
  HRFOAPL1 HRFOARC0 HRFOBKO0 HRFODBDL HRFODBRN HRFOFLGX HRFOFMTT
  HRFOHAL0 HRFOLEV0 HRFOLOGF HRFOREOD HRFOREO0 HRFOREO1 HRFOREO3
  HRFOREO5 HRFOREO9 HRFOROLS HRFORQ02 HRFORQ04 HRFORQ06 HRFORQ11
  HRFOSUB0 HRFOUNL2 HRFYCCDF HRFYDBD0 HRFYDBD2 HRFYDBD3 HRFYDBD5
  HRFYIXRC HRFYMSGT HRFYPRES HRFYPSBG HRFYPSB5 HRFZLOGI
  

Fix information

• Fixed component name

  IM DB SOLUTION

• Fixed component ID

  5655S7700

Applicable component levels

• R210 PSY UI19354

     UP14/07/08 P F407

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.