IBM Support

PM09335: There is no link in the history view between a baseline and a su ccessor project after the baseline project is created.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as user error.

Error description

  • When a baseline is created in the java client on a project in
    the prep state, the history view does not create a link between
    the baseline and the successor project.
    
    Also, when updating members in the 'successor' project, the
    following error is displayed in the messages log:
    
    WARNING: could not identify baseline project for ?project?
    matching baseline selection criteria of process rule.
    
    
    Steps to Reproduce:
    
    1. Install Synergy 7.1.0.1 Ifix 02
    
    2. Create a Project.
    
    3. Check in the Project to the prep state.
    
    4. Right click on the top level of the project and click on
    'Create Baseline....'
    
    5. After creating the baseline, view the history.
    
    NOTE: The baseline is not linked to the successor project.
    
    6. Return to the successor project (the originally created
    project) and click on Update Members.
    
    Note the Error: WARNING: could not identify baseline project for
    ?project? matching baseline selection criteria of process rule.
    
    
    Note: Projects in this instance were created with the process
    rule 'Integration Testing'.
    
    
    WORKAROUND:
    
    Use the classic client to overcome the issue with the history
    view.
    

Local fix

Problem summary

Problem conclusion

  • This is not a problem. The product is working as designed. The
    behavior of the history view changed in 7.1.0.1 to show links
    based on the project's baseline, and not the predecessor and
    successor.
    

Temporary fix

Comments

  • Ignore the APAR Reason code.  It is not relevant.
    

APAR Information

  • APAR number

    PM09335

  • Reported component name

    TLOGIC SYNERGY

  • Reported component ID

    5724V66SN

  • Reported release

    710

  • Status

    CLOSED USE

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-03-08

  • Closed date

    2010-05-14

  • Last modified date

    2013-01-29

  • 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

[{"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