IBM Support

PI08263: BASELINE SET DEFINITIONS CONTAINING PURGED MODULES RESULT IN SETS NOT BEING CLOSED CORRECTLY

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If a baseline set definition contains a module which has been
    purged, when all valid modules are added to a set, that set does
    not get automatically closed.
    
    To recreate:
    
     - create a project containing 3 modules
     - create a baseline set definition containing all 3 modules
     - delete and purge one of the modules
     - create a baseline set using the definition
     - add the remaining 2 modules to the set
    
    At this point, since all valid modules have been added to the
    set, it should get closed automatically, this does not happen.
    
    Workaround: close the set manually (or using the DXL close()
    perm).
    
    Attempts to get the definition to refresh itself e.g. by adding
    and removing other modules, did not suceeed, the record of the
    purged module remains in the definition internally, and so the
    problem will continue to manifest itself when using that
    definition.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users affected                                           *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * If a baseline set definition contains a module which has     *
    * been                                                         *
    * purged, when all valid modules are added to a set, that set  *
    * does                                                         *
    * not get automatically closed.                                *
    *                                                              *
    * To recreate:                                                 *
    *                                                              *
    *  - create a project containing 3 modules                     *
    *  - create a baseline set definition containing all 3 modules *
    *  - delete and purge one of the modules                       *
    *  - create a baseline set using the definition                *
    *  - add the remaining 2 modules to the set                    *
    *                                                              *
    * At this point, since all valid modules have been added to    *
    * the                                                          *
    * set, it should get closed automatically, this does not       *
    * happen.                                                      *
    *                                                              *
    * Workaround: close the set manually (or using the DXL close() *
    * perm).                                                       *
    *                                                              *
    * Attempts to get the definition to refresh itself e.g. by     *
    * adding                                                       *
    * and removing other modules, did not succeed, the record of   *
    * the                                                          *
    * purged module remains in the definition internally, and so   *
    * the                                                          *
    * problem will continue to manifest itself when using that     *
    * definition.                                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • Fixed - client-side fix
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI08263

  • Reported component name

    TLOGIC DOORS

  • Reported component ID

    5724V61DR

  • Reported release

    950

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-12-17

  • Closed date

    2014-06-07

  • Last modified date

    2014-06-07

  • 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

  • R960 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYQBZ","label":"Rational DOORS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.5","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
17 October 2021