IBM Support

PM39003: Copy to filesystem fails to copy multiple occurrences of the same project version.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If you have a static hierarchy that contains the same version of
    the same project in different places in the hierarchy,  a copy
    to filesystem operation will write only the contents of one to
    the filesystem.
    
    Example - consider static projects top, A, B, and C in a
    structure like this:
    
     top~1
     |- A~1
     |- B~1
        |- C~1
        |- A~1
    
    All subprojects A, B, and C have no WA maintained are marked as
    relative to parent.
    
    Note that project A~1 is marked as relative to two parent
    projects; this is possible if A~1 is already marked relative to
    a parent that does not maintain its WA and the gets added to
    another parent that does. Creating a baseline creates the static
    hierarchy with no workarea.
    
    Running the copy to filesystem operation results in the highest
    A~1 project NOT getting written.  The 'lowest' one, beneath C~1,
    is the one that gets written.
    
    If the subprojects are not marked as being relative to the
    parent project then they will each get written once to the same
    level in the filesystem. This is only a problem if the same
    project version is relative and used multiple times in the
    hierarchy.
    
    There is no notice of error when this occurs.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Copy to filesystem fails to copy multiple occurrences of the
    same project version.
    

Problem conclusion

  • This problem was fixed in Synergy 7.1.0.3.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM39003

  • Reported component name

    TLOGIC SYNERGY

  • Reported component ID

    5724V66SN

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-05-11

  • Closed date

    2011-06-17

  • Last modified date

    2011-06-17

  • 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

    TLOGIC SYNERGY

  • Fixed component ID

    5724V66SN

Applicable component levels

  • R710 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSC6Q5","label":"Rational Synergy"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
22 December 2020