APAR status
Closed as user error.
Error description
During an IBM Rational ClearCase Unified Change Management (UCM) deliver, elements of type copy_merge will not be copied over if the file size and the checksum of the version element on both branches is the same. Steps to repro: 1. Create a copy merge file type cleartool mkeltype -supertype compressed_file \ -mergetype copy -nc FILE_COPY_MERGE 2. cleartool chtype FILE_COPY_MERGE ?element? 3. Check version number and note it. 4. Check file size and make sure they are the same size. 5. From dev stream, checkout and checkin identical. 6. Deliver. Deliver will show a merge but no version will be created or merge arrow will be drawn. Workaround: Change file size or manually merge the files.
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
This is not a defect and is working as designed. As the contents of the file have not changed, there is no need f or a separate version, nor is a merge arrow needed. A new version is always created in the development stream for ea ch checkin that we do on that stream, that doesn't mean or imply the creation of a new version after a deliver operation. A new version in the integration stream is only created when the new v ersion that is being merged is different in its contents than th e previous version existing in the integration stream. When a ne w version is created, a merge arrow is also drawn. A new version is also created and a merge arrow drawn, even if t he file size remains constant, given the fact that the contents of the file have changed. As for the message telling about a successful merge, that's used to convey a successful delivery and to specify that version rel ated information for the element was merged with internal CC rec ords.
APAR Information
APAR number
PK46684
Reported component name
CC&CC MSITE WIN
Reported component ID
5724G3300
Reported release
700
Status
CLOSED USE
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-06-07
Closed date
2007-07-31
Last modified date
2011-12-19
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":"SSSH3S","label":"Rational ClearCase MultiSite"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
19 December 2011