IBM Support

PI43626: RATIONAL PROGRAMMING PATTERNS - JOURNAL EXTRACT MISS ENTITY WHEN USING MERGE MIGRATION.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • The merge process used at migration time aggregates all Pacbase
    artifacts in the library of the lowest level in the network.
    
    When using incremental migration (MIBJ procedure) if en entity
    is created and deleted in the lower level library and then
    created in an upper level, only the movements of the lower level
    library are taken into account by the MIBJ procedure.
    
    This may lead to inconsistency in the migration, missing
    entities and "unresolved" errors in the workspace.
    
    
    this issue was for us to modify the element in DRM the following
    week.
    That caused synchronization to add the element.
    
    Currently, the element only exists in DRM.
    
    The problem is that the deletion of the element in AC1 is
    considered as
    the final state. Even though the deletion was done prior to the
    Add/Modify in DRM. I would expect them to be evaluated
    chronologically.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * all users of the MIBJ users                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When using incremental migration (MIBJ procedure) if en      *
    * entity                                                       *
    * is created and deleted in the lower level library and then   *
    * created in an upper level, only the movements of the lower   *
    * level                                                        *
    * library are taken into account by the MIBJ procedure.        *
    *                                                              *
    * This may lead to inconsistency in the migration, missing     *
    * entities and "unresolved" errors in the workspace.           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PI43626

  • Reported component name

    RATL PROG PATTE

  • Reported component ID

    5725H0300

  • Reported release

    900

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-06-23

  • Closed date

    2015-11-18

  • Last modified date

    2015-11-18

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

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

Fix information

Applicable component levels

  • R850 PSY

       UP

  • R900 PSY

       UP

  • R901 PSY

       UP

  • R910 PSY

       UP

  • R911 PSY

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSKPEG","label":"Rational Programming Patterns"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
14 October 2021