IBM Support

PM97088: CPS corruption if sub folder is moved and converted to project

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • It is possible to corrupt a CPS if a sub-folder containing a
    configured module is moved then converted to a project.
    
    If this is done, it will not be possible to add further modules
    to the CPS. the following message is given:
    
    'The selected module is not within the scope of the change
    proposal system.'
    
    To recreate:
    
    
     - create a project containing 2 modules and a folder
     - create another module inside the sub-folder
     - create a CPS and add to it one of the top-level modules, and
    the module in the sub-folder
     - cut/paste the folder outside of the project, then convert to
    to a project
     - now try to add the other top-level module to the CPS
    
    Workaround:
    
    Move the project/folder back to its original location and
    convert it back to a folder
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    It is possible to corrupt a CPS if a sub-folder containing a
    configured module is moved then converted to a project.
    
    If this is done, it will not be possible to add further
    modules to the CPS. the following message is given:
    
    "The selected module is not within the scope of the change
    proposal system."
    
    To recreate:
    
    
     - create a project containing 2 modules and a folder
     - create another module inside the sub-folder
     - create a CPS and add to it one of the top-level modules,
    and the module in the sub-folder
     - cut/paste the folder outside of the project, then convert
    to to a project
     - now try to add the other top-level module to the CPS
    
    Workaround:
    
    Move the project/folder back to its original location and
    convert it back to a folder
    

Problem conclusion

  • The code has been changed so that the product issue no
    longer occurs.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM97088

  • Reported component name

    TLOGIC DOORS

  • Reported component ID

    5724V61DR

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-09-16

  • Closed date

    2013-12-13

  • Last modified date

    2013-12-13

  • 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 DOORS

  • Fixed component ID

    5724V61DR

Applicable component levels

  • R910 PSN

       UP



Document information

More support for: Rational DOORS

Software version: 9.1

Reference #: PM97088

Modified date: 13 December 2013