PM75413: USING THE EXTRACT FACILITY THE FRAGMENTS ARE COMING OUT IN A WRONG ORDER.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Error DescriptionÏ
  An IMS extract is done.
  
  One of the dependent segments is unkeyed. The segments are
  extracted in order as expected.
  
  The problem occurs on the import.
  
  The segments, after the import, are reordered.
  
  The dbd definition for this segment looks like:
  
        SEGM    NAME=xxxxxxxx,PARENT=yyyyyyyy,BYTES=40,PTR=T,
           RULES=(LLL,FIRST),
  
  The LOADTYPE = 2 as they want to just backfill an existing
  database.
  
  It would appear that File Manager makes no attempt to maintain
  sequence and just mindlessly inserts, which in this case based
  on the dbd exactly reverses the segment sequence.
  

Local fix

• Local FixÏ
  n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All FM/IMS Extract (IXB) and Load (ILB)      *
  *                 users.                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION: Twin segments extracted from one        *
  *                      database and loaded into another are    *
  *                      not in the same sequence in the loaded  *
  *                      database as they were in the extracted  *
  *                      database.                               *
  *                      The problem occurs when the insert      *
  *                      rule for the twin segment is FIRST or   *
  *                      HERE.                                   *
  ****************************************************************
  * RECOMMENDATION: Apply the provided PTF.                      *
  ****************************************************************
  The Extract and Load does not maintain the sequence of twin
  segments when the insert rule for these segments is FIRST or
  HERE.
  

Problem conclusion

• FM/IMS has been modified to maintain the sequence of twin
  segments when they are extracted from one database and loaded
  into another.
  

Temporary fix

Comments

APAR Information

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

  PM70710

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

Modules/Macros

• FMN1LVL
  

Fix information

• Fixed component name

  FILE MANAGER Z/

• Fixed component ID

  5655W6800

Applicable component levels

• RC14 PSY UK90284

     UP12/12/16 P F212

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.