Fixes are available
Rational Synergy Interim Fix 1 for 7.2.1.5
Rational Synergy Interim Fix 2 for 7.2.1.5
Rational Synergy Interim Fix 3 for 7.2.1.5
Rational Synergy Interim Fix 4 for 7.2.1.5
Rational Synergy Interim Fix 5 for 7.2.1.5
Rational Synergy Fix Pack 6 (7.2.1.6) for 7.2.1
Rational Synergy Interim Fix 1 for 7.2.1.6
Rational Synergy Fix Pack 7 (7.2.1.7) for 7.2.1
APAR status
Closed as program error.
Error description
This is a follow on APAR to PI54006. (NO WARNING GIVEN WHEN A MULTI-PROJECT SYNC USES THE INCORRECT TASK) That APAR fixed one scenario as documented. There are a number of other scenarios where multi project sync does not result in a warning if the task is associated with a different release. For example: 1. Create Collaborative Project P_a with Release R_a/1 (default process rules; possibly an existing Build Management Project with corresponding Baseline is required in advance) 2. Create Collaborative Project P_b with Release R_b/1 (default process rules; possibly an existing Build Management Project with corresponding Baseline is required in advance) 3. Create Task 1 with Release R_a/1 and add a dummy text file to Project P_a, then check in file and close Task 1 4. Create Task 2 with Release R_b/1 and add a dummy text file to Project P_b, then check in file and close Task 2 5. Create Task 3 with Release R_a/1 and keep it selected as "Current Task" 6. From outside Synergy client, modify both dummy text files 7. In the "Projects" list, select both projects P_a and P_b as a multi-selection (requires expanding the related "Project Groupings" if done using the default "My Project Groupings" query) and select "Sync Work Area" > "Members and Subprojects" 8. In the appearing "Work Area Conflicts" view, select at least the dummy file from the "wrong" project (i.e. Project P_b), or both dummy files together and select "Keep Work Area Changes". Expected Results: An onscreen warning should be issued. This APAR should limit itself to this scenario. All Warnings that are provided in a single project sync should also be provided in a multi project sync.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * All users that use multi project Sync with different release * * values. * **************************************************************** * PROBLEM DESCRIPTION: * * No task release warning given when a user perform a multi * * project sync with different release values. * * * * 1. Create Collaborative Project P_a with Release R_a/1 * * (default process rules; possibly an existing Build * * Management Project with corresponding Baseline is required * * in advance) * * 2. Create Collaborative Project P_b with Release R_b/1 * * (default process rules; possibly an existing Build * * Management Project * * with corresponding Baseline is required in advance) * * 3. Create Task 1 with Release R_a/1 and add a dummy text * * file to Project P_a, then check in file and close Task 1 * * 4. Create Task 2 with Release R_b/1 and add a dummy text * * file to Project P_b, then check in file and close Task 2 * * 5. Create Task 3 with Release R_a/1 and keep it selected as * * "Current Task" * * 6. From outside Synergy client, modify both dummy text files * * 7. In the "Projects" list, select both projects P_a and P_b * * as a multi-selection (requires expanding the related * * "Project * * Groupings" if done using the default "My Project Groupings" * * query) and select "Sync Work Area" > "Members and * * Subprojects" * * 8. In the appearing "Work Area Conflicts" view, select at * * least the dummy file from the "wrong" project (i.e. Project * * P_b), or * * both dummy files together and select "Keep Work Area * * Changes". * * * * Actual Result * * No warning message about incorrect task release * * * * Expected Results: * * An onscreen warning should be issued. * **************************************************************** * RECOMMENDATION: * * N/A * **************************************************************** N/A
Problem conclusion
Fixed in Rational Synergy 7.2.1.5 iFix001
Temporary fix
Comments
APAR Information
APAR number
PI60864
Reported component name
TLOGIC SYNERGY
Reported component ID
5724V66SN
Reported release
721
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-04-15
Closed date
2016-06-28
Last modified date
2016-06-28
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
R721 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSRNYG","label":"Rational Synergy"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"721","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
16 October 2021