Tasks are not associated to CRs in Central Server environment

Technote (troubleshooting)


Problem(Abstract)

Associating a task to a CR from the Rational Change show form can fail while writing a success message to the CR status log.

Symptom

In the Rational Change show form, associating a task to a CR does not print a message to the log indicating that an associated_task relationship has been created between the task and the CR. The task is not listed in the associated task list in the form.


Cause

This issue can be caused by the task missing its cluster_id attribute. Rational Change Central Server relies on the cluster_id of a task to uniquely identify task objects when performing associations and creating ghost CRs in development databases. The absence of the cluster_id attribute prevents ghost CRs from being created in development databases.

There is no reason for the cluster_id attribute to go missing unless deleted manually.


Environment

Rational Change Central Server setup using Change 5.2.x and Synergy: 7.1.x

Resolving the problem

Perform a copy task operation on the problematic task, keeping the same objects associated. Place the original task in the excluded state and complete the new copied task. The new task has a cluster_id attribute. Use DCM to transfer it to other development databases as required.

Cross reference information
Segment Product Component Platform Version Edition
Software Development Rational Synergy AIX, Linux, Solaris, Windows, HP-UX 7.1a, 7.1.0.2, 7.1.0.1, 7.1, 7.0 All Editions

Rate this page:

(0 users)Average rating

Document information


More support for:

Rational Change
General Information

Software version:

5.0, 5.1, 5.2, 5.2.0.2, 5.2.0.3, 5.2.0.4

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Reference #:

1473056

Modified date:

2012-10-30

Translate my page

Machine Translation

Content navigation