John,
As you say you can have as many sessions of NX running as you like on a single workstation including different versions, and it only checks out one license. I have needed to do this in the past to have a model open in two sessions in order to pick apart how it was built so I can rebuild a better version after deleting a root feature. By opening the native part from disk and modifying it in a session without necessarily saving anything I can then open a second copy based on the original disk image and use it to interrogate the original feature tree.
In teamcenter however you can have two teamcenter logins running on the one tube, but they seem to be locked to only one NX session. In addition the owner of that session is the first login only. All this is quite logical, but I can't for the life of me manage to do the same trick in teamcenter as I do in native when picking apart a model in two NX sessions.
No matter what your system is whether in teamcenter or native you can't have open two copies of the same file, or any two files called the same thing, (from different directories for example), in the one NX session. It just wouldn't make sense to do that. As I said you can have two sessions open in native and work in alternate parallel sessions as it were. Teamcenter does not seem to be able to to the same.
What I have to do in teamcenter is export the model to native and open it in a second session from there. It seems to be either that or save it under a different name, which I don't favor because every extra item you add in teamcenter has to be managed and incurs some cost to do so.
Now I don't have much of a question, just noticed that the teamcenter guys are calling native "Naive" and kind of wanted to know if there was any way to match the level of sophistication that I'm able to manage in native.
In case anyone is wondering, we really do need to do this from time to time. Sometimes we find that the best way forward is to rebuild part of the model. Some of those times things already got tooled up, and worse we pay the toolmaker for additional changes, so we need to keep the majority exactly the same. To keep it the same the only way to do that is by re-applying variable radius blends with setback and multiple edge sets, using exactly the same parameters. These blends got deleted because we trashed the root feature to fix a problem that probably shouldn't have been there in the first place. Hence it's real handy to flick back and forth between session so I can fix what radii were applied where in these variable blends I'm trying to rebuild.
Best Regards
Hudson