IBM Support

IZ96857: OBJECTS MISSING FROM PROMOTION AND EXPORT OPERATION WHEN RELATIONSHIP EXISTS BETWEEN TWO GOVERNED COLLECTIONS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If a governed collection is being exported or promoted and there
    is a relationship from this governed collection to an object
    that exists in a second governed collection and that target
    object is not the root governed object of that second collection
    then the export will not contain the correct objects.
    
    I there are no relationships from the objects in the governed
    collection being exported to the root governed object in the
    second collection then only the objects that are related to the
    exported governed collection will be exported/promoted.
    
    Consider this scenario:
    Create A,B, X and Y
    setup relationship AtoB and XtoY
    Govern A
    Govern X
    Add relationship BtoY
    
    You now have two governed collections Gov(A,B) and Gov(X,Y)
    
    When you export A you will get Gov(A,B) and Y (Y is no longer in
    a governed collection) but you won't get X at all.
    
    You should get Gov(A,B) and Gov(X,Y).
    

Local fix

Problem summary

  • During export and promotion an incomplete graph of objects was
    being created under some circumstances when objects from one
    governed collection had relationships to objects in another
    governed collection.
    

Problem conclusion

  • A fix was made so that the entire governed collection in which
    an ojbect exists is exported/promoted if that object is the
    target of a relationship from another object in another governed
    collection that is being exported/promoted.
    
    This fix will be shipped in v7.0.0.4
    

Temporary fix

Comments

APAR Information

  • APAR number

    IZ96857

  • Reported component name

    SERVICE REGISTR

  • Reported component ID

    5724N7200

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-03-16

  • Closed date

    2011-03-16

  • Last modified date

    2011-03-16

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

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

Fix information

  • Fixed component name

    SERVICE REGISTR

  • Fixed component ID

    5724N7200

Applicable component levels

  • R610 PSY

       UP

  • R620 PSY

       UP

  • R630 PSY

       UP

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSWLGF","label":"WebSphere Service Registry and Repository"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
16 March 2011