PI50968: AFTER DRF TIME-STAMP RECOVERY, IB DOES NOT INITIALIZE PRIMARY INDEX OF INPUT SIDE AND IMS ISSUES DFS0730I UNABLE TO OPEN DATA

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Index Builder should initialize the primary index of the OLR
  Input side when RECON indicates the OLR cursor is active and the
  OLR cursor in the Input side data set is the high-key value,
  which indicates that all of the segments have been moved to the
  Output side. This condition occurred after time-stamp recovery
  by IMS Database Recovery Facility.
  
  If Index Builder does not initialize the primary index of the
  Input-side, IMS issues DFS730I I,31:
  DFS0730I UNABLE TO OPEN DATA SET WITH DDNAME xxxxxxxx FOR REASON
  I,31, DATABASE xxxxxxxx PSB xxxxxxxx NETO
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of IMS Index Builder for z/OS,     *
  *                 Version 3 Release 1 (FMID=H22O310)           *
  ****************************************************************
  * PROBLEM DESCRIPTION: When RECON shows a HALDB partition is   *
  *                      in the OLR cursor active status and     *
  *                      the OLR cursor in the input-side        *
  *                      dataset shows all of the segments       *
  *                      already have been moved, the primary    *
  *                      index of the output-side should be      *
  *                      initialized.                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  This APAR fixes the following problems:
  (1) When RECON shows a HALDB partition is
  in the OLR cursor active status and
  the OLR cursor in the input-side dataset
  shows all of the segments already have
  been moved, the primary index of
  the output-side should be initialized.
  (2) When an error with IIUB060E REASON=792
  or 793 is detected for a HALDB partition
  with active OLR cursor, the number of
  scanned segments should be printed.
  IIUB060E  NUMBER OF RECORDS MISMATCH
  

Problem conclusion

• This APAR fixes the problems listed in the Problem Summary
  field.
  

Temporary fix

Comments

APAR Information

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

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

  UI32912

Modules/Macros

• IIUMMSGR IIUSCA11 IIUSCA12
  

Fix information

• Fixed component name

  IMS INDEX BUILD

• Fixed component ID

  5655E2400

Applicable component levels

• R310 PSY UI32912

     UP15/11/14 P F511

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.