A fix is available
APAR status
Closed as program error.
Error description
Usability problem with mirrored attributes. If a CR has two or more related CRs, the mirrored attribute values for each of these CRs in a query or report are separated by commas. If the attribute has no value on any one related CR, it is difficult to identify which attribute value is mapped to which related CR by looking at the report. Tools: Tested on Change 5.2.0.6 and Change 5.3.0.2 OS: Any Description. Steps: -To reproduce this behavior with mirrored attributes, consider the basic example of having duplicate CRs -Create a CR(CR1) with a few duplicate CRs(CR 2, CR 3, CR 4 CR 5) -Select a particular attribute that you would like to see values for on each of the Duplicate CRs(for example: 'keyword' attr) -Set the 'keyword' attribute with any value on CR3 and CR5. (example: on CR2 --keyword = ?blank?, CR 3 --keyword = 'testing', CR 4--keyword = ?blank?, CR 5--keyword = 'rational') -Create a query to fetch CR1 and list its duplicate CRs with the mirrored attribute 'keyword' for each of the CRs Result: In the result, the mirrored attribute 'keyword' should show each of the values separated by commas. However, in this case, it is impossible to know which CR had a blank value, because the output on the report looks like this for attribute 'keyword' --- testing,rational --- The blank values are ignored and there is no way of knowing which of these values are mapped to which CR from the list of CR2, CR3, CR4 and CR5.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * **************************************************************** * PROBLEM DESCRIPTION: * **************************************************************** * RECOMMENDATION: * **************************************************************** mirrored attribute values UI inconsistency
Problem conclusion
Fixed in IBM Rational Change Fix Pack 5.3.0.3
Temporary fix
Comments
APAR Information
APAR number
PM55556
Reported component name
TLOGIC CHANGE
Reported component ID
5724V87CG
Reported release
520
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-01-09
Closed date
2012-03-16
Last modified date
2012-03-16
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 CHANGE
Fixed component ID
5724V87CG
Applicable component levels
R520 PSN
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYQQ2","label":"Rational Change"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
16 March 2012