The following operating systems are tested and supported: 

• Windows 2000 Professional, Service Pack 2 or Service Pack 3 (Service Pack 2 is recommended)
• Windows XP Professional

In addition, both Microsoft Windows 2000 Server and Windows 2000 Advanced Server are supported.

Notes:

• This Service Release does not support Windows NT.
• Rational recommends that you have local administrator privileges when running Rational XDE. In addition, administrator privileges are required to install this Service Release.

Level 2 support for German, French, Italian, and Swedish. (Supports local character set or English in fields, forms and documents; supports locale-specific conventions for date/time formats, numbering, and currency.)

Level 1 support for Dutch, Hebrew, Japanese, Simplified Chinese, Traditional Chinese, and Korean.

Notes:

• Certain software in this Service Release will not function if ClearCase view root and VOB directories contain 16-bit characters. Please see Internationalization in Known Issues.
• Level 2 support for Japanese and Simplified Chinese is provided by Rational XDE v2002 Release 2.1, but not this Service Release.

Supports Rational ClearCase v.2002.05.00 and ClearCase LT v.2002.05.00, with patch levels as listed below.

ClearCase 4.2 and ClearCase LT v.2001A.04.00 have not been tested and are not supported.

Notes:

• Since Visual SourceSafe and ClearCase use the Microsoft SCC interface, other configuration management systems that use the SCC interface may work with this same release of XDE, but they have not been tested. For further guidance, see Parallel Development with Microsoft Visual SourceSafe below, under "Restrictions and Guidelines for Using this Service Release."
• This Service Release has not been extensively tested with dynamic views; Rational Software recommends using snapshot views with this Service Release where possible.

Prior to deploying this Service Release, your ClearCase installation must include all mandatory patches for your version of ClearCase. Current patch requirements are as follows:

• For ClearCase LT v.2002.05.00, patch 2
• For ClearCase v.2002.05.00, patch 15

To verify the latest patch information for your version of ClearCase, go to http://www.rational.com/support/downloadcenter/

To find out which patches your ClearCase installation has installed, use the cleartool -version command in a DOS command prompt window.

Using XDE with ClearCase: Configuring Your Environment (summary-config.pdf) - This document summarizes the scenario setup environment when using Rational XDE with ClearCase. The recommendations include tool options and configurations.

Category

ID

Summary

Action sequencer problem introduced.

Some RTE Tag Value Sets not generated in the merged model.

Saving merged model crashes Rational XDE.

Incorrect order of added elements.

46469

Subunit directories left checked out.

54381

Multibyte characters displayed incorrectly in Set Activity ID dialog box

46296,230617

46505

230720, 230672

599861

Category

ID

Description

Compare/Merge

45473

Action Sequencer Problem Introduced

Applies To: Users of Professional and Modeler editions of Rational XDE v2002 who installed an earlier hotfix released as ratlc000365915_msmrgeng.zip.

A model with the following example configuration exists:

Mode
    Package1
        Class1
    Package2

The model is changed to the following configuration:

Mode
    Package2
        Class1

If a compare and/or merge of the two models is attempted, Class1 will not be added to the merged model because Compare/Merge does not recognize that the move of Class1 occurred before its previous package was deleted. With this Service Release, Class1 will be added properly to the merged model.

Compare/Merge Performance Improvements for Multiple Units

Applies To: Users of Rational XDE Professional v2002.

Merge sessions involving a large model with a large number of subunit files take an inordinate amount of time to complete. With this Service Release, the time taken is greatly reduced.

Some RTE Tag Value Sets Not Generated in the Merged Model

Applies To: Users of Professional and Modeler editions of Rational XDE v2002.

When starting a merge session on Java models or C# models, some RTE Tagged Value Sets (e.g. “Merge”) will not be generated in the merged model. These Tagged Value Sets are used by the language add-ins while generating the code from the merged model. This Service Release restores the generation of the missing Tagged Value Sets.

Saving Merged Model Crashes Rational XDE

Applies To: Users of Professional and Modeler editions of Rational XDE v2002.

If a new local style gets added to a model element on a diagram, and a new local reference gets added to the same style within the model element, the user may see a stack overflow error message when a Compare/Merge session is initiated. For example, this problem may occur if you change a diagram’s view/print properties. Wtih this Service Release, the stack overflow problem no longer occurs.

Incorrect Order of Added Elements

Applies To: Users of Professional and Moderler editions of Rational XDE v2002.

A model with the following example configuration exists:

Model
    Class1
        Operation1
            Parameter1
            Parameter2

Model
    Class1
        Operation1
            ParameterA
            ParameterB
            ParameterC

In the example used in the above use case, Parameter1 and Parameter2 are deleted and ParameterA, ParameterB, and ParameterC are added as expected. However, the order of the parameters added is not preserved and ParameterB and ParameterC are stored in reverse order. In general, this defect will manifest itself when one or more elements in a collection (classes in a package, operations in a class, etc.) have been deleted in one Compare/Merge contributor, and more than one element has been added at the same location, unless other rules (such as parameter name matching) are in effect. Although the order of the parameters is incorrect, no data is lost.

With this Service Release, the order of the newly added parameters will be preserved in merge sessions.

Subunit Directories Left Checked Out

Applies To: Users of Professional and Modeler editions of Rational XDE v2002 who use the ClearCase Plugin v1.3.0 with XDE.

Steps to Reproduce the Problem

1. Create a new subunit in an XDE package that is already under source control.
2. Add the new subunit to source control and leave the “Keep checked out” option selected.
3. After making changes to the subunit, a subsequent checkin operation does not check in the parent directory of the subunit.

This Service Release will ensure that the parent directory of a newly added model subunit does not appear in the list of units to be added to source control and, therefore, the user will not be able to choose to keep the directory checked out. The directory will be added to source control and will be checked in.

46732

XDE-ClearCase Composite Unit Operations Support

Applies To: Users of Professional and Modeler editions of Rational XDE v2002.

Changes to the model that resulted in multiple, related control units being checked out, but only part of the model was checked in, encountered errors when loading the model in a second view. In a single development stream, checking in partial models results in other users seeing partial changes leading to model corruption. This can also occur in private streams if changes are delivered piecemeal to a shared (integration) stream.

Steps to Reproduce the Problem

The user will have made changes to the model that resulted in multiple, related control units being checked out.

1. With multiple control units checked out, check in a single element having references to other, new parts of the model (do not check in these new parts).
2. From another view, update the model.
   The model is now inconsistent in the second view as some files are missing. This is the result of the model having been placed in ClearCase in an inconsistent state.

Common Symptoms

Errors are seen when loading the model in a second view. The model may not load under certain circumstances. Changes are lost.

Solution

This Service Release adds functionality to help ensure the model is placed under ClearCase control in a consistent manner. When working with Rational XDE Professional v2002: .NET Edition, a second dialog box for the same operations (checkin, add to source control, update) opens, advising you that more files are being acted upon in order to maintain model consistency. For more information, see Composite Object Versioning Support.

Multibyte Characters Displayed Incorrectly in Set Activity ID Dialog Box

Applies To: Users of Professional and Modeler editions of Rational XDE v2002 who use the ClearCase Plugin v1.3.0 with XDE.

Steps to Reproduce the Problem

1. In a project, check out a file in a UCM view. For that checkout, create a new activity whose name includes multibyte characters.
2. Select the project and click ClearCase > Set Current Activity.

You will see incorrect characters in the pull-down activity menu.

Solution

This Service Release ensures that multibyte characters are displayed correctly.

510494

Updating a Model Does Not Bring in Any New Files/Folders

Applies To: Users of Professional and Modeler editions of Rational XDE v2002.

Updating, or getting the latest version of an XDE model element only updates the control unit of the selected element . This results in inconsistent models in memory and broken links to items that should be present or <<Fail to get name>> instead of a model element name.

Solution

The new composite object versioning (COV) functionality ensures that not only the model, but its associated folder are affected by an update or get latest version operation. In the case of the associated folder, the update is done recursively. The model then reloads to bring in all the new elements. This ensures that the model is consistent both under source control and in memory.

Note   In the case where a first package is added, the COV functionality will not be able to update the folder associated with the model as it does not yet exist in all views. If you encounter this scenario, it is recommended that the complete view be updated. This will occur at most one time for each model. Creating subunits upon creation of a model that will be shared between users will alleviate this latter issue.

510545

Composite Object Versioning (COV) Does Not Operate When Keep Checked-out on VS.NET

Applies To: Users of Rational XDE Professional v2002.

The Composite Object Versioning (COV) functionality does not operate when a checked-in file is kept checked out.

Solution

The COV was updated to detect this new condition and to properly check-in the other control units. 

Note   Other control units remain checked-in; only the selected control unit(s) remain checked-out after processing. This approach ensures the minimum intrusion of the COV in daily operations.

47507,
47552

Browse Model Command Fails

The command Browse Model on a VB.NET "Property" with parameters or a VB.NET "Enum" fails to take you to the model.

Solution

With the Service Release, you can browse to the model from a VB.NET property with parameters or a VB.NET Enum.

47643,
47965,
47966

Editor Windows Opened and Closed Upon Command Execution

Editor windows are opened and closed during the execution of a Round-Trip Engineering command (Synchronize, Reverse Engineer, Generate Code, Browse Code).

Solution

With the Service Release, windows are no longer opened and closed during the execution of the command (other than the Browse Code command, which opens the corresponding code window).

47673,
47674

Synchronizing a C# Project Encounters Conflicts for Class Constructors with Initializers

Preconditions

You have the conflict resolution option set to Leave unresolved. You can access this option by clicking Tools > Options > Rational XDE > Round-Trip Engineering.

Problem

When synchronizing a C# project in XDE v2002 Release 2.1 that was already synchronized using XDE v2002 Release 2.0 and contains class constructors that have initializers, a RTE-conflict TaskItem is logged. The TaskItem states  "Code and Model items changed differently for field ConstructorInitializer".

Solution 

With this Service Release, no conflict is encountered and model is updated correctly.

Problem

Synchronizing with conflict resolution option set to Always replace code causes problems for the class constructors with initializers.

Solution

With this Service Release, the constructor initializer is removed from code as expected.

47690

Reside Relationship Not Removed in Multiple Synchronizations of a Project

When the code and model are in a synchronized state, if a class is moved from one file to another file, the next synchronization of the project does not remove from model the previous Reside relationship which points to the class from the component representing the previous file.

Solution

With this Service Release, next top-level synchronization (i.e., from the project in the Solution Explorer or the code model in Model Explorer) removes the invalid Reside relationship.

47886,
56047

Parser Errors Encountered While Synchronizing VB.NET Code

Problem

Synchronizing VB.NET code that uses commas for optional arguments at the calling side causes a parser error.

The following code demonstrates the problem:

Public Class Class1
Public Sub Hello(ByVal Arg1 As String, _
Optional ByVal Arg2 As Integer = 0, _
Optional ByVal Arg3 As Boolean = False)
End Sub
Public Sub World(ByRef P1 As Object)
Me.Hello("World", , )
End Sub
End Class

Solution

With this Service Release, the parser recognizes this code correctly.

Problem

Synchronizing VB.NET code that uses the "Static" modifier for a variable inside a method/property body causes parser error.

The following code demonstrates the problem:

Public Class Class1
Public Sub Sub1()
Static Foo As Integer
End Sub
End Class

Solution

With this Service Release, the parser recognizes this code correctly.

48051

XDE Does Not Create Relationships to Objects Within the Assembly CrystalDecisions.CrystalReports.Engine.dll

Problem

XDE does not create relationships to objects within the assembly CrystalDecisions.CrystalReports.Engine.dll due to one or both of the following:

• XDE expected the top-level classes in assemblies to have "empty" namespaces instead of "null".
• The project does not reference the dependent assembly CrystalDecisions.Shared.dll.

Solution

XDE now accepts top-level all types of classes in assemblies. This resolves the first issue above. However, to entirely remove the problem, you must ensure that whenever the assembly CrystalDecisions.CrystalReports.Engine.dll is added is a reference, CrystalDecisions.Shared.dll is also referenced.

48672

Explicit Operator Does Not Synchronize Properly on Second and Subsequent Synchronizations

Problem

In C#, if there is a struct with an "explicit operator" or "implicit operator", the second synchronize gives error message or in some cases causes XDE to crash. This is due to  XDE not capturing all the necessary information from the code during the first synchronize. This happens only in the case of explicit and implicit operators contained within a struct (already works correctly in all other cases).

Solution

XDE now correctly synchronizes C# implicit and explicit operators contained in a struct, the first time itself.

48789

Type Picker Needs to Show the Classes/Delegates in Non-VSRTE-Stereotyped Packages

Problem

The Type Picker dialog box does not display classes placed in packages without a stereotype (i.e., virtual packages). This was originally by design. All packages not having the stereotype "namespace" were ignored when the type tree was being populated.

Solution

The contents of these packages are now displayed in the dialog box, and the fully qualified name that is generated by the dialog box omits the names of these packages, as it should.

Storage Unit Reference Repair Is Broken

Applies To: Users of Professional and Modeler editions of Rational XDE v2002 who work on models under source control and create new files (separate units) in shared containers such as packages.

Elements Disappear from the Model Explorer on Undo Checkout

Applies To: Users of Professional and Modeler editions of Rational XDE v2002.

When making separate units within a model and adding them to source control, sometimes undoing the checkout of an element that hasn't changed causes elements to disappear from the Model Explorer. In this Service Release, the model element no longer disappears.

230681

Copy and Paste Breaks Element References

Previously, when copying a collaboration from one model to another, references from some of the elements in the collaboration to elements outside the collaboration were broken. For example, the reference from an object or classifier role in a collaboration to the classifier of which it was an instance was not preserved when performing a cross-model paste.

Solution

This has been fixed and the references now refer back to the elements in the original model after a cross-model paste (assuming they were not included in the set of elements pasted, in which case the references point to the pasted elements).

Package Does Not Expand When There Is a Zero-Length Unit

Applies To: Users of Professional and Modeler editions of Rational XDE v2002 who have zero-length subunit files in a model (RATLC00046296, RATLC00230617).

Steps to Reproduce the Problem

1. Create a model.
2. Create a package and make it a unit.
3. Add a Collaboration Instance and make it a unit.
4. Add some other elements to the package.
5. Save and close the model.
6. Replace the Collaboration Instance unit (cix file) with a file of zero length.
7. Reopen the model.
8. Try to expand the package.

All elements added to the package after the zero-length subunit is introduced do not appear in the Model Explorer when the package is expanded.

This Service Release fixes the issue.

231979

Printing Diagrams on a Single Page

Unable to satisfactorily print a diagram on letter-size paper that was set up to print on plotter paper.

Solution

Rational XDE now allows you to "fit to page," so you can print the diagram to a single page, regardless of the paper size.

232035

Broken Diagram Results When a Checkout or Activity Dialog Box Interrupts Creation of the Diagram

Problem found when using ClearCase 5.0 with service packs through 12 on a separate server, and XDE Type Manager. Source Control options set to Prompt for check out when checked-in items are edited or Always prompt for an activity, or both options are set. (This also applies to other configuration management applications.)

Solution

With this Service Release, diagram creation is not interrupted by source-control dialog boxes.

232106

Error When Resolving References to Component Without Location Registry Entry

An error, "Component already exists," is received when attempting to resolve unresolved external references. This occurs when opening a model that contains references to a component whose entry in the location registry has been removed. This has been resolved and the component will now be registered in the appropriate location rather than re-created.

232598

Moving Sequence Diagram Components in Zoom-Out Magnification Causes Data Corruption of Diagram

Applies To: Users of Professional and Modeler editions of Rational XDE v2002.

If you open a sequence diagram, zoom out, then move lifelines, the diagram is corrupted.

With this Service Release, you can make modifications in the zoomed out state. XDE verifies that all lifelines are selected before extending lifelines or bumping messages to prevent diagram corruption.

232920

Package Renamed in the Model Explorer Not Updated in Diagram Window

In some cases, when a package was renamed in the Model Explorer, the new name would not be updated in the diagram window until the diagram was refreshed.

This is now resolved and the name is correctly updated in both locations when the name is changed.

233712

Error on Saving Updated Subunits When Parent Is Unchanged

When attempting to save updates to subunits within a model, an error was sometimes encountered if the
parent unit was read-only as it had not changed and did not need to be saved.

Subunits are now saved without error when the parent unit is read-only and does not need to be saved.

599277

Rose Diagrams Appear Distorted When Imported to XDE

All diagrams created in Rose have to be modified because auto-resize is turned off on all imported diagram elements in XDE.

Solution

Importing Rose diagrams in XDE now behaves correctly. If AutoSize is turned on in Rose, XDE correctly enables auto-resizing after the import.

Find: Modeler Error When Finding Elements on the Drawing Surface with Unresolved Note

Applies To: Users of Professional and Modeler editions of Rational XDE v2002.

If the user has any note or text in his/her search space with a broken reference, XDE’s find command will return no search results.

Steps to Reproduce the Problem

1. Start Rational XDE and create a new model file (e.g. Model1).
2. From the Toolbox, drag a Class and a Note onto the drawing surface of the Main diagram. Class1 and Note now appear on the drawing surface.
3. Close the Main diagram by clicking on the Close (“X”) button at the right top corner of the drawing surface.
4. In the Model Explorer, right-click Note and click Delete from Model.
5. Reopen the Main diagram by double-clicking on the Main diagram node in the Model Explorer. The unresolved Note appears on the drawing surface.
6. Right-click an empty area of the drawing surface and click Find on the shortcut menu to bring up the Find dialog box.
7. Type "Class" in the Find what field and click OK.

Solution

Category

ID

Summary

Configuration Management

Category

ID

Description

49273

Rational XDE Patterns Can Be Corrupted During Merge

Rational XDE stores pattern-processing instructions as properties (tagged values) of model elements; for instance, the location where the results of a pattern expansion should be placed is called it’s “expansion location” and that location is determined by a set of properties that includes ExpansionLocationType and ExpansionLocationContextElement. Choices for the type can be Context or Argument, which indicate (respectively) that the expansion location is some specific model element or that the location is determined (indirectly) by one of the template argument values supplied to the pattern at expansion time. To make the pattern consistent (and expandable), the value stored in ExpansionLocationContextElement must be either a reference to a particular element in the target model or a reference to one of the pattern’s template parameters, depending on the value of the ExpansionLocationType property. If the pair of properties has inconsistent values (e.g., type says Context but the context element value is a template parameter of the pattern), then the pattern won’t expand correctly.

A common symptom of this problem is to see errors when trying to apply a pattern following a merge.

Steps to Reproduce the Problem

1. A user edits an existing pattern, setting ExpansionLocationType to Context and ExpansionLocationContextElement to a package in their model.
2. The user checks in and delivers the model with the updated pattern.
3. Another user edits the same (original) pattern, setting ExpansionLocationType to Argument and ExpansionLocationContextElement to a template parameter of the pattern.
4. The second user checks in the model with the updated pattern, rebases, and proceeds to merge the pattern.
5. The second user chooses the ExpansionLocationType that the first user contributed, but the ExpansionLocationContextElement that they specified.
6. Since the ExpansionLocationType and ExpansionLocationContextElement properties are now inconsistent, the pattern will not expand correctly.

Solution

When merging patterns, the recommended approach is to consistently choose all properties of a pattern from the same contributor.

49273

Rational XDE Code Templates Can Be Corrupted During Merge

Applies To: Users of Professional and Modeler editions of Rational XDE v2002.

Rational XDE stores code templates as a set of properties (tagged values); for instance, Template1Body stores the text of the code template and Template1ParameterValueReferences stores references to the argument values used to replace the parameterized pieces of the text. The text property is dependent on the argument value property — if every parameter appearing in the text doesn’t have an argument supplied for it, then the code template won’t expand correctly. During a CM merge operation, it is possible for a user to choose properties from different contributors such that these dependencies between the properties are violated.

A common symptom of this problem is to see errors when trying to expand the code template following a merge.

Steps to Reproduce the Problem

1. A user adds a new parameter with a default argument value to an existing code template and makes use of the new parameter in the text of the code template.
2. The user checks in and delivers the model containing the updated code template.
3. Another user adds two new parameters with default argument values to the same code template and makes use of the new parameters in the (original) text of the code template.
4. The second user checks in the model with the updated code template, rebases, and proceeds to merge the code template.
5. The second user chooses the text property that they added but the parameter property that the first user added.
6. Since the text of the code template now uses one more parameter than there are template argument values, the code template will not expand correctly.

Solution

When merging code templates, the recommended approach is to consistently choose all properties of a code template from the same contributor.

232092

Avoid Working in Second VS.NET Window Opened for Compare/Merge

Applies To: Users of Professional and Modeler editions of Rational XDE v2002.

When working with XDE and ClearCase in Visual Studio .NET, a second Visual Studio .NET window will be started if you initiate a ClearCase command, such as a checkin, from within Visual Studio .NET and that ClearCase command triggers a merge of XDE model units. This second Visual Studio .NET window will be closed automatically after the Compare/Merge session completes and so you should not use this window for any other purpose.

Solution

If Visual Studio .NET opens a second window to perform a Compare/Merge, do not use it for any purpose other than the Compare/Merge.

234288

Resource Error When Invoking Type Manager with -status_only Flag

In instances where an XDE Compare/Merge session is started through a Type Manager-initiated session from ClearCase with the -status_only flag, the following dialog box will appear: "Resource error."

The –status_only flag is used rarely by ClearCase when invoking the XDE Type Manager and the fact that it is not handled properly has no impact on the Compare/Merge session.

Solution

Clicking the OK button to dismiss the dialog box will not affect the XDE Compare/Merge session. Proceed as normal after clicking OK.

510631

Potential Data Loss When Separate Subunits Made Under CM Control

Applies To: Users of Professional and Modeler editions of Rational XDE v2002.

When combining or separating model units, you should ensure no one else is working on the same units. Otherwise, you can run into scenarios like the following:

1. You make package P in model M a separate unit.
2. In parallel with you, someone else modifies P while it is still combined with M.
3. You deliver your changes.
4. The other person delivers changes.
5. A merge is needed but will be performed silently. The separation of package P from model M is applied automatically and will result in your changes in that separate unit being applied while the other user's changes to P (while it was still combined with model M) are lost.

Since the separation of package P from model M is applied automatically during the merge, no visible merge session is needed and the merge occurs silently. However, should there be conflicts for other reasons, then a merge session will be presented to the user. At that point, the user will be able to reverse the automatic application of the separation of package P from model M. However, this would result in the loss of the separated version of package P.

Failure to Combine Separate Units During a Merge Involving ClearCase

Compare/Merge can silently fail to combine a unit during a merge. For example, consider the following scenario:

1. Start with model M containing diagram D and separate unit package P.
2. User 1 combines package P into model M.
3. User 2 makes some other modification of M, such as renaming D.
4. User 1 delivers.
5. User 2 delivers.

Note that this defect applies to UCM rebase operations as well, and also applies even if UCM isn't used and simple check-ins trigger merges.

When user 2 delivers, ClearCase sees that both contributors have modified M.mdx and so the type manager for XDE models is invoked to perform the merge silently. XDE Compare/Merge is invoked. However, the result of the merge passed back to ClearCase will not have package P combined with model M—it will remain a separate unit. There is no warning or other indication of this failure to combine the units.

Even when the merge isn't silent, this will occur. For example, consider the following scenario:

1. Start with model M containing diagram D and separate unit package P.
2. User 1 renames D and combines package P into model M.
3. User 2 renames D.
4. User 1 delivers.
5. User 2 delivers.

When user 2 delivers, ClearCase sees that both contributors have modified M.mdx and so the type manager for XDE models is invoked to perform the merge silently. XDE Compare/Merge is invoked. However, XDE Compare/Merge detects that there is a conflict in the renaming of diagram D and so the silent merge fails. ClearCase then invokes the type manager for XDE models to resolve the conflict via the user. Consequently, an XDE Compare/Merge session is presented to the user. The user will see a conflict regarding the name of the diagram. The user will also see that the merged model indicates <failed to get unit> for the package P, which is normal for a ClearCase-initiated merge since the P.pkx unit isn't accessible during the merge of M.mdx. The package P will have a delta on it. Clicking on the package will show that the delta is for the name of the package's storage unit. In the merged model, the name is combined with the model and the other contributors show P as a separate unit. However, in the saved merged model, P erroneously remains a separate unit.

Workarounds

To work around this issue, combining of units needs to occur in such a way that the resulting merge will be trivial--that is, the version of the M.mdx file being delivered is the immediate successor to the version in the integration stream. One way to achieve this is to do the following:

1. Everyone delivers their changes.
2. Create a new baseline and recommend it.
3. Everyone rebases and doesn't touch model M, to ensure the eventual combine will succeed, and doesn't touch package P, to ensure no data is lost.
4. One user combines the unit, delivers the change, creates a baseline, and recommends it.
5. Everyone rebases again.

This procedure is sure to work. However, it isn't necessary if you practice strong ownership of the type of parent unit into which the subunit is being combined. In this case, the parent unit is the root model file itself. However, in many cases it will be a package that might be "owned" by a particular developer who knows that nobody else is working on it. Then, the combining of the unit can proceed without the full procedure above.

Note that it isn't sufficient to simply succeed in the delivery—if others have the older versions of the model with P still a separate unit, then their rebase will result in a merge that leaves P as a separate unit. The procedure just above avoids this.

If you aren't using UCM, then you simply need to ensure that the merge is trivial. Typically, this occurs when you check out a file and no one else has subsequently checked in any changes before you check in your changes. Furthermore, to avoid potential data loss, it's best that no one even have the file checked out. For example, suppose you successfully combine the unit because no one checked in a change to M.mdx between the time you checked it out and checked it back in. If someone had checked out the unit before you checked in your changes, then that person still has package P as a separate unit. However, any changes to P as a separate unit will be ignored since the model now has P combined into M.mdx—the separate P.pkx file is no longer part of the model.

233125

Unable to Add to Source Control After Reconnecting ClearCase to Network

Applies To: Users of Rational XDE Professional v2002.

When using Rational XDE with Rational ClearCase in a disconnected manner, and then reconnecting, errors are displayed:

• Error checking out the file <filename> from source control. Unable to determine view for <viewpath>: not a ClearCase object
• The operation could not be completed. You may be unable to work in the model after reconnecting to ClearCase.
  
  Note: This problem is not particular to XDE and may be encountered when XDE is not being used.

Solution

When you need to work in VS.NET disconnected from ClearCase,  use File > Source Control > Change Source Control to rebind the solution to the source control provider. You should select Checkout in the resulting dialog box and use the modified version of the files as the checked-out version.

Pending Checkins Not Updated After UCM Rebase

Applies To: Users of Professional and Modeler editions of Rational XDE v2002 who use Rational ClearCase in conjunction with XDE.

Expected model changes will not appear in Rational XDE, but will appear in the ClearCase Explorer, as expected, after a rebase operation if the rebase is performed while Rational XDE models are open.

Part of the Rational ClearCase UCM process mandates that users rebase their development stream in order to get updated artifacts from the latest project baseline. This rebase operation is typically conducted in parallel to, and often outside of, the usage of the integrated development environment (IDE). This may result in changes that are not automatically reflected in the IDE.

Steps to Reproduce the Problem

1. Open Rational XDE.
2. Open a model.
3. Using the ClearCase tools—for example, ClearCase Explorer—rebase the development stream to bring in changes from the latest baseline.
   The XDE model is not reloaded, even though new and updated files are available on disk.

Solution

Whenever running the Rational ClearCase UCM rebase operation, first close any open Rational XDE models. It is not necessary to close the IDE. Reopening the model after the rebase operation has completed will show all the changes.

510080

Composite Object Versioning (COV) Does Not Cross Model Boundaries

Applies To: Users of Professional and Modeler editions of Rational XDE v2002.

Background

The new composite object versioning (COV) functionality provided in this Service Release only covers related model elements in a single model. Related model elements between models will not be listed by the COV dialog boxes. This may result in inconsistencies between models.

Steps to Reproduce the Problem

1. Create two models.
2. Add both models to source control.
3. Create a class in model 1 and a diagram in model 2 and make them both controlled units.
4. Drag and drop the class in the diagram.
   This creates a relationship between the two models.
5. Add the class to source control.
   Only the class is added, the diagram is not affected.
6. Add the diagram to source control.
7. Rename the class on the diagram.
   Both files are checked out as both are modified.
8. Check in the diagram.
   Only the diagram is checked in, not the class.

Solution

When working with multiple, related models, you must do the CM operation at least once in each model to ensure consistency.

510186

XDE Does Not Return Dependent CM Units When Model Is Closed

Applies To: Users of Professional and Modeler editions of Rational XDE v2002.

Steps to Reproduce the Problem

1. Open an XDE model.
2. Perform a CM operation that would cause the composite unit functionality to be activated (e.g., updates a single element).
   Observe that multiple elements are affected by the operation.
3. Perform a CM operation on a file element in the Solution Explorer in VS.NET.
   Observe that multiple elements are affected by the operation.
4. Close the model.
5. Perform a CM operation on a file element in the Solution Explorer in VS.NET.
   Observe that a single element is affected by the operation when multiple elements are expected to be affected.

Solution

Perform all CM operations on XDE model elements from within the XDE Model Explorer. Enhanced functionality has been added to perform composite unit operations within an XDE model (see release note for RATLC00046732). However, this functionality is only available on models that are open.

510188

Hijacked Files Still Shown as Source Controlled

Applies To: Users of Rational XDE Professional v2002.

Background

Files that have been hijacked during a session disconnected from ClearCase appear as if they were controlled and checked in.

Steps to Reproduce the Problem

1. Create a new solution and add the solution to source control.
2. Create a model and add two packages (P1 and P2), with a class in each (P1::C1 and P2::C1) and a diagram in one (P2::D1).
3. Add both classes to the diagram (P2::D1).
4. Make all model elements into separate units.
5. Save and check in the entire model.
6. Close the solution and exit Visual Studio .NET.
   The workstation is disconnected from the network.
7. Start VS.NET and open the solution by browsing to it, and then open the model.
8. Rename P2 to P2B.
9. Cancel “Edit of read-only file” dialog and make the file writable, thereby hijacking it.
10. Save the file.
11. Rename P1::C1 to P1::C1B, and repeat steps 10 and 11.
12. Save P2B and exit VS.NET.
    Workstation is reconnected to the network.
13. Start VS.NET and opens the solution from source control.
    The hijacked files (P2B and P1::C1B) are still shown as controlled, checked in. Modifying any of the previously modified files will not result in a dialog being displayed.

Common Symptoms

Editing files that are marked as checked in does not trigger a checkout operation.

Solution

It is recommended that you update your view and convert the hijacked files to checkouts prior to continuing your work when reconnecting to ClearCase.

510561

Rebase with an Open Model Fails to Reload

Applies To: Users of Professional and Modeler editions of Rational XDE v2002 who use Rational ClearCase in conjunction with XDE.

Expected model changes will not appear after a rebase operation if the rebase is performed while Rational XDE models are open.

Part of the Rational ClearCase UCM process mandates that users rebase their development stream in order to get updated artifacts from the latest project baseline. This rebase operation is typically conducted in parallel to, and often outside of, the usage of the integrated development environment (IDE). This may result in changes not being automatically apparent in the IDE.

Steps to Reproduce the Problem

1. Open Rational XDE.
2. Open a model.
3. Using the ClearCase tools—for example, ClearCase Explorer—rebase the development stream to bring in changes from the latest baseline.
4. New and changed files are available on disk.
5. The XDE model is not reloaded, even though new and updated files are present.

Solution

Whenever running the Rational ClearCase UCM rebase operation, first close any open Rational XDE models. It is not necessary to close the IDE. Reopening the model after the rebase operation has completed will show all the changes.

510600,
510738

Updating a Model that Results in a New Version Being Loaded also Causes the Model to be Reloaded Twice

Applies To: Users of Rational XDE Professional v2002: .NET Edition.

The composite object versioning (COV) functionality is able to ensure model consistency under VS.NET by monitoring CM activities. When a supported configuration management (CM) activity is detected, such as Get Latest Version, it determines the XDE model control units that also need to participate in the operation and executes the operation on these.

Steps to Reproduce the Problem

1. User1 makes a modification that affects the model file to a model that is under ClearCase control.
2. User1 checks in the changes.
3. User2 selects the model file in their view and updates it.
   At this point, the model is reloaded, all other new elements are then loaded in view, and the model is reloaded again.

Solution

This is actually correct behavior because of the post-event detection of the CM operation by XDE. As such, VS.NET generates the update of the model, which changes on disk and which causes the model to reload. XDE then determines that an update occurred, updates the rest of the model on disk, and forces the model to reload to pick up any and all new files.

510601

User Prompted to Choose Between Two Versions of Project File When Updating Model

Applies To: Users of Rational XDE Professional v2002: .NET Edition who use Rational ClearCase in single-stream mode in conjunction with XDE.

In certain situations, the user may see a Confirm Version to Check out dialog box and need to choose between two project or solution files.

Microsoft Visual Studio.NET (VS.NET) saves all solution and project information in specially formatted files.
These files contain, for example, the list of files making up the project. These files are also typically kept
under source control.

Updating a Rational XDE model may bring new files into the project or solution. The project or solution files must be modified to bring in these new files. Since the new files had also been added to the project in another view, a new version of the project therefore exists. The VS.NET-ClearCase integration then correctly prompts the user to determine which version to use.

Steps to Reproduce the Problem

1. User1 creates a new empty C# project, Proj1, in a snapshot view.
2. User1 adds Proj1 to source control.
3. User1 adds a model to Proj1.
4. User1 adds two packages to the model, makes package1 a separate unit
5. User1 clicks on Save All.
6. User1 selects Package1 and checks it in. The model is also checked in.
7. User1 checks in the project.
8. User2 creates a snapshot view pointing to the same VOB.
9. User2 opens Proj1.
10. User2 opens the model.
11. User2 makes package 2 a separate unit (check out when prompted).
12. User2 clicks Save All (check out when prompted).
13. User2 clicks on Package2 and checks it in. The model is also checked in.
14. User2 checks in the project.
15. User1 right-clicks the model in the Model Explorer and clicks Get Latest Version.
    The model is reloaded. Afterwards, a reload dialog box appears as a result of the composite object versioning (COV) process and the model is reloaded a second time.
16. User1 clicks Checkout when prompted to check out the project.
    A Confirm Version to Check out dialog box appears, informing the user that a newer version of the project exists and asking the user to choose between two versions.

Solution

It is recommended that whenever the Confirm Version to Check out dialog box is shown, the user selects the current version in view. This will ensure the least amount of problems when working with the model from this point on. The required merge is also simpler when done during a subsequent check-in operation.

510620

Failure to Load Model When Updating a Subunit

Steps to Reproduce

1. User1 creates a new empty C# project, Proj1, in a snapshot view and adds it to source control.
2. User1 adds a model to a project under source control and adds two packages to that model, making them separate units, and then saves all.
3. User1 selects Package1 and checks it in.
   The model and Package2 are also checked in.
4. User1 checks in the project.
5. User2 creates a snapshot view pointing to the same VOB.
6. User2 opens Proj1 and opens the model.
7. User2 adds a third package, Package3, makes it a separate unit, and saves it (check out when prompted).
8. User2 adds a class to Package1 (check out when prompted).
9. User2 checks in Package3.
   The model and Package1 are also checked in.
10. User2 checks in the project.
11. User1 checks out the project and selects Version after Update.
    User1 receives an error: "Failed to load model File <model name> and the model is not opened."

Solution

When you are in the position of User1 and receive the Confirm Version to Check Out dialog box, select Loaded Version, not Version after Update.

510701

Composite Object Versioning (COV) Fails to Chain Merge Sessions

Applies To: Users of Rational XDE Professional v2002: .NET Edition who use Rational ClearCase in single-stream mode in conjunction with XDE.

Under some circumstances, not all control units are merged when performing an update with multiple conflicting control units.

In Rational XDE Professional v2002: .NET Edition, the composite object versioning (COV) functionality is triggered by a change in the source-control status of one of the model subunits. As such, it is doing post-processing that may not trigger all the correct merge operations.

Steps to Reproduce the Problem

1. User1 creates a new solution.
2. User1 adds the solution to source control.
3. User1 creates a Rational XDE base model.
4. User1 adds the following to the model:
   Package1
       Class1
   Package2
       Class1
       Diagram1
5. User1 drags both classes onto Diagram1.
6. User1 makes sll units separated.
7. User1 selects the root node and saves.
8. User1 checks in the root node and see this message: "In order to ensure model Integrity in the source control system, the following files have been checked in for you. <List of files>
9. User1 clicks OK.
10. User1 checks in his solution.
11. User2 updates his view from outside the tool.
12. User2 opens the solution.
13. User1 renames Package1 and Package2.
14. User1 checks in his changes.
15. User2 renames Package1 and Package2 to something other than User1 did (to create two conflicts).
16. User2 checks in his changes.
17. When asked which version to take, User2 keeps the current version in view.
    The first merge does happen, but the second (or any subsequent) merge will fail.

Solution

The user should perform the check-in and merge by selecting all the individual subunits. This can be done as a remedy after the discovery of the failure.

510838

Incorrect Configuration Management Status After Model Update

The Configuration Management status becomes incorrect in certain situations while using XDE and ClearCase, after issuing an update to the model. A symptom of this is that you cannot rename classes in the Model Explorer.

Solution

To work around this problem, close and reopen your model after doing an update on the view.

510850

Error Checking in Separate Units, Then Unable to Add to Source Control

Applies To: Users of Rational XDE Professional v2002: .NET Edition.

The description for this defect reflects a problem that has been partially fixed. The composite object versioning (COV) functionality makes it possible for the merge to complete and for the correct elements to be retrieved, but some other subunits that require merges are left checked out instead of being merged and checked in.

Steps to Reproduce the Problem

1. User1 creates a new blank solution in a ClearCase view and adds it to source control.
2. User1 adds a base model to the solution containing a class within a package.
3. User1 makes the package and class separate units.
4. User1 selects the root (model) node and saves it.
5. User1 checks in the package and class.
   A dialog box opens stating: "In order to ensure model Integrity in the source control system, the following files have been checked in for you. <List of files>
6. User1 clicks OK.
   All elements are added to source control and checked in.
7. User1 checks in the solution.
8. User2 updates her view from ClearCase Explorer.
9. User2 starts VS.NET and opens the solution from source control.
10. User2 opens the model.
11. User1 adds another package and makes it a separate unit.
12. User1 checks in the change and is prompted to check out the solution.
13. User1 checks out the solution.
    A dialog box opens stating: "In order to ensure model Integrity in the source control system, the following files have been checked in for you. <List of files>
14. User1 clicks OK.
15. User1 checks in the solution.
16. User2 adds a package and names it "MyPackage".
    The model is checked out and User2 gets prompted to select either the loaded version or the
    latest version.
17. User2 uses the loaded version.
18. User2 makes the new package a separate unit and checks it in.
    A message states:
    "There are multiple versions of ...\Solution.vssscc…"
    and "There are multiple versions of ...\Solution.sln."
19. User2 selects the loaded version in both cases.
    The COV functionality attempts to check in the other files and shows errors indicating that the files
    cannot be checked in because later versions exist on the branch.

Solution

Select the subunits that were not checked in, and check them in one by one. This ensures that the merge occurs correctly and that the files are checked in. In order to ensure model integrity in the CM system, you should do this as soon as possible after detecting the problem.

510974

Check-in Fails If the Files Were Checked-out from Outside the Shell

Applies To: Users of Rational XDE Professional v2002: .NET Edition.

Users may be tempted to use applications and tools external to the VS.NET shell in order to execute configuration-management operations. However, if a file is checked out from outside VS.NET while a model is open, it may cause confusion inside the shell.

Steps to Reproduce the Problem

1. User creates a new solution and adds it to source control.
2. User creates a base model containing classes within two packages.
3. User makes each model element a separate storage unit.
4. User selects the root node, saves it, then checks it in.
5. A dialog box opens stating: "In order to ensure model Integrity in the source control system, the following files have been checked in for
   you. <List of files>
6. User clicks OK
7. User checks in the solution.
8. From outside Rational XDE, user checks out both package (.pkx) files.
9. From inside the tool, user clicks File > Source Control > Refresh Status. This properly shows both packages checked out.
10. User renames one of the packages and checks it in.
    The status does not get updated and the check-in does not happen.

Solution

The check-in operation will be successful if tried a second time. However, it is recommended that configuration-management operations always be executed from within the shell.

Internationalization Support in XDE Startup and XDE ClearCase Installer

Components of this Service Release will fail on 16-bit character operating systems if 16-bit characters are part of pathnames to ClearCase view root and VOB directories. For example, on a Japanese operating system, if these paths contain Kanjii (16-bit) characters, XDE startup and the XDE ClearCase Type Manager installer will not function; however, if these paths are restricted to 8-bit Latin characters, they will operate correctly running on a Japanese operating system.

Models Created in Miscellaneous Files Folder in Solution Explorer

If you add a reference to an assembly from a client project and then synchronize the client project, the referenced assembly is reverse engineered into an assembly model. However, a model of 0 bytes with a name similar to " _Model1.mdx" is added to the Miscellaneous Files folder in the Solution Explorer.

It is safe to ignore this model.

General XDE

231927

Model Validation Warnings

If you validate a Rational XDE model and receive the following warnings or errors as a result, no action is required. The warnings do not affect synchronization and you can safely ignore them.

• Enumeration "<EnumName>" has an invalid Generalization to Class "Enum".
  The Validate command generates this warning for all enumerations in the model.
  
• Attribute(s) named "<AttributeName>" conflict between Class "<ClassName>" and classifier(s) "<ClassName>".
  The Validate command generates this warning for a property that overrides a virtual property in the base class.
  
• The Interface "<InterfaceName>" should not contain an Attribute.
  A property is modeled as a UML attribute with dependencies to the get and/or set UML operations. An event is modeled either as an attribute or as an association. The Validate command generates a warning whenever there is a UML attribute inside an interface.

233755, 228464

Errors Produced Upon Creation of ASP.NET Web Application

Applies To: Users of Rational XDE Professional v2002: .NET Edition.

Before creating any ASP.NET Web Application under ClearCase, the following procedure must be followed:

To create an ASP.NET Web application

1. In the Tools menu, click Options.
   The Options dialog box appears.
2. Expand Rational XDE.
3. Click Cancel in the Options dialog box.
4. Create the ASP.NET Web application by clicking File > New > Project, and then selecting the ASP.NET Web Application template from one of the supported project types in the New Project dialog box.

Failing to do this may cause an exception dialog box to appear with the following message:

Trying to g.DTE.GetObject(ICTFactory), Err.Description: Class does not support Automation or does not support expected interface

If you don't perform the above workaround prior to creating an ASP.NET Web application and see the exception dialog box, you will first need to get back to a clean post-install configuration and then create an ASP.NET Web application as explained above.

To get back to a clean post-install configuration

1. Exit Visual Studio .NET.
2. From the Start menu, click Programs > Microsoft Visual Studio .NET > Visual Studio .NET Tools > Visual Studio .NET Command Prompt.
3. At the command prompt, type devenv /resetskippkgs.
   Visual Studio .NET launches.

To create an ASP.NET Web application without the exception, follow the procedure "To create an ASP.NET Web Application" above.

598017

Obsolete Documentation for Adding Template Arguments for Template Parameters

The Help topic "Adding Template Arguments for Template Parameters" includes obsolete procedures.

Solution

The updated procedures are provided below:

To add  a template argument for a model element template parameter 

1. If necessary, add a binding relationship between the model element and template.
2. Right-click the «bind» relationship, and click Collection Editor.
   The Template Arguments tab of the Collections dialog box opens.
3. Click the Insert New Template Argument button.
   If you have multiple template parameters specified in the template, then the Choose a Parameter dialog box opens. If you have only one template parameter specified, then a browser window opens.
4. For multiple template parameters only, select a model element type template parameter, and then click OK.
5. In the browser window, select which model element you want to use for your template argument, and then click OK.
   A row opens in the Template Arguments tab of the Collections dialog box.
6. Click the property pages (ellipsis) button in the Collections column.
   The Values tab of the Collections dialog box opens.
7. Enter the appropriate values for the listed properties.
   Note   For details on the listed properties, click Help in the Collections dialog box.
8. Click Close, and do one of the following:
   • Click Close again to close the Collections dialog box.
   • Repeat step 3.

To add a template argument for a data type template parameter 

1. If necessary, add a binding relationship between the model element and template.
2. Right-click the «bind» relationship, and click Collection Editor.The Template Arguments tab of
   the Collections dialog box opens.
3. Click the Insert New Template Argument button.
   If you have multiple template parameters specified in the template, then the Choose a Parameter
   dialog box opens. If you have only one template parameter specified, then a row opens in the
   Template Arguments tab of the Collections dialog box.
4. For multiple template parameters only, select a data type template parameter, and then click OK.
5. Click the property pages (ellipses) button in the Collections column.
   The Values tab of the Collections dialog box opens.
6. Enter a value in the value column.
   Note: For details on the listed properties click Help in the Collections dialog box.
7. Click Close, and do one of the following:
   • Click Close again to close the Collections dialog box.
   • Repeat step 3.
     

(800) 433-5444
(toll free)

(408) 863-4000
Cupertino, CA

(781) 676-2460
Lexington, MA

+ 31 (0) 20 4546 200
Netherlands

+31 (0) 20-4545-201
Netherlands

+61-2-9419-0111
Australia

+61-2-9419-0123
Australia