5.2.1 Developer for C++ Known Problems

5.2.1 Developer for C++ Known Problems
Date: 99/02/02
 
Fr No Title External Description
3409 Editing Modes: "Version mismatch warning preference" not supported for MS VSS The "Version mismatch warning preference" editing mode user preference is not supported in supplied MS Visual Source Safe library interface scripts.

3304 RobotProbes and StateChanger model examples do not appear output to System Log When running the RobotProbes or StateChanger model examples on NT with TO, there may not be any output displayed to the System Log. It is related to buffering of stderr/stdout on NT.

The workaround is to add log.commit(); after each Log SAP command in the transition code blocks to ensure that the output is flushed to the system log.

3042 Clearcase checkout scripts display wrong error message The library interface scripts display an incorrect error message of "Can not make an element", if a second user tries to check out a class which is already checked out.

This only impacts ClearCase and will occur for both linear and binary formats. It will only happen when two users are sharing a common view or the image is out of sync with the library status. The misleading error is caused by the following: when the image believes the element is not checked out and the file is writable the ClearCase check_out script executes a make element because it assumes that the file is view private. This operation fails because the element already exists and is checked out; however, the error refers to the make element error not the check out issue.

2672 Toolset allows names of MSC components to be all uppercase The toolset disallows the use of all uppercase letters for names of many items, but it does allow all uppercase names of MSC components. Using all uppercase letters for names can cause problems during parse and code generation, therefore do not use all uppercase letters for names of MSC components.


 
 

5.2.1 Developer for C++ Known Problems
Date: 99/02/02
 
Fr No Title External Description
2517 Launcher on NT does not recognize sessions in view private ClearCase directories The Launcher, on Windows NT, does not recognize sessions created as view private directories under ClearCase after disconnecting and reconnecting the view containing the session. If you create an Developer session as a view private directory in a ClearCase view, and then disconnect the view and reconnect it later (e.g., shutdown your workstation and restart it), the session is no longer presented as an Developer working session in the Launcher dialog, and is not recognized as a valid session if it is selected using the Browse tool. There currently is no way to re-use such sessions.


2217 Context threads browser has wrong caption The name at the top of the Threads Browser window opened from a context is not the name of the context, but instead it is the name of the update from which the context was created.