PK59804: INVALID SECONDARY INDEX AFTER ORF RUN

APAR status

• Closed as program error.

Error description

• Database has secondary index source on second level and target
  on root.  When index records are created during load time, we
  remember  the RBA OF the segment in a level table. However,
  the root  segment had never been passed to the index routine,
  leaving  its RBA to zero. When the index source segment was
  processed,  it picked up the RBA from the root, this having a
  pointer of  zero.
  A second problem addressed by this APAR is
  when using the standard IMS routines instead of the
  HP utilities, the non unique segments were not captured.
  A third problem addressed by this APAR is:
  HRF01009E Invalid syntax for keyword ICDDN in line 005
  HRF01014I Reason is unbalanced parenthesis
  When you resubmit the job, it completes normally.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of IMS Online Reorganization       *
  *                 Facility Version 1.2.                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: Invalid secondary index created.        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  This APAR is correcting the following problems:
  1. Invalid secondary index created. Database has secondary index
  source on second level and target on root. When index records
  are created during load time, we remember the RBA of the
  segment in a level table.  However, the root segment had never
  been passed to the index routine, leaving its RBA to zero.
  When the index source segment was processed, it picked up the
  RBA from the root, this having a pointer of zzero.
  2. Non unique key segments not processed. When using the
  standard IMS routines instead of the HP utilities, the non
  unique segments were not captured.
  3. Unbalanced parenthesis error message. Unbalanced parenthesis
  is detected, but the parenthesis are balanced. This error is
  temporary. When processing the next line, the starting point
  was not moved up.  If the chaining address between the line
  contained an "(" an additional parenthesis was detected. )
  

Problem conclusion

• The following corrections have been made to correct the above
  mentioned problems:
  1. Logic has been changed to pass all segments to the index
  routine to make sure that a valid RBA can be stored.
  2. Logic has been changed to capture the non unique segments.
  Additionally, we had to make sure that the true utilities
  are used, which may not be the case when the HP utilities
  are using IMS alias names.
  3. Code has been changed to reset the starting address.
  

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:

  UK33713

Modules/Macros

• HRFOBLDX HRFOLEV0 HRFONKEY HRFOREO0 HRFOREO4
  HRFOREO5 HRFORLD0 HRFORLD1 HRFOUNL0 HRFYBLDX HRFYCC01 HRFYMSGT
  

Fix information

• Fixed component name

  IMS ONLINE REOR

• Fixed component ID

  5655H9700

Applicable component levels

• R120 PSY UK33713

     UP08/02/15 P F802 Ž