scm: why goes to another URL?!

I've seen this myself. Use scm list credentials to view what is mapped to your login session.

I've also noted that you can only have a single login session per user id (the -u option), so if you first create a session with nickname SessionA for user Bob, and then create a session with a different nickname, ie SessionB, for user Bob, SessionA no longer is valid.

Look at this, it's asking password for another URL. I am working on the test server, and it's asking the password for production server URL.

I was running some scm command and suddenly see production data. Then I found this problem. It seems store the connections? How can I find out the current connection it stored?

I think it may related to the current workspace is loaded from production. What's the scm command to unload a workspace?

Thanks
Jirong

C:\Workspace\Cognos_SSSMP_huji>scm login -r https://localhost:9443/ccm -u huji -
P aaaaa -n rtc
Logged in to https://localhost:9443/ccm

C:\Workspace\Cognos_SSSMP_huji>lscm status
Password (huji @ https://cyspqpvspaap001.cihs.ad.gov.on.ca:9443/ccm/): Terminat
e batch job (Y/N)? y

I've seen this myself. Use scm list credentials to view what is mapped to your login session.

I've also noted that you can only have a single login session per user id (the -u option), so if you first create a session with nickname SessionA for user Bob, and then create a session with a different nickname, ie SessionB, for user Bob, SessionA no longer is valid.

It's the production one! How can I get rid of it?

C:\Sandbox\Cognos_SSSMP_huji\Cognos_SSSMP>scm list credentials
https://cyspqpvspaap001.cihs.ad.gov.on.ca:9443/ccm/, huji, rtc, <No>
, <No>, <Password>

I don't understand. I logout from the production session and login to test again, and now everything works fine. Why it's still store the production one. What does this credentials mean?

C:\Sandbox\Cognos_SSSMP_huji\Cognos_SSSMP>lscm checkin "Release Notes.txt"
Password (huji @ https://localhost:9443/ccm/):
Committing...
Workspace: (1000) "Cognos SSSMP Development Stream Workspace -huji" <-> (1001) "
Cognos SSSMP Development Stream"
Component: (1002) "Cognos_SSSMP" <-> (1001) "Cognos SSSMP Development Stream"
Outgoing:
Change sets:
(1036) *--@ <No>
Changes:
---c- \Release Notes.txt

C:\Sandbox\Cognos_SSSMP_huji\Cognos_SSSMP>lscm status
Password (huji @ https://localhost:9443/ccm/):
Workspace: (1000) "Cognos SSSMP Development Stream Workspace -huji" <1001>

Component: (1002) "Cognos_SSSMP" <-> (1001) "Cognos SSSMP Development Stream"
Baseline: (1005) 2 "v1"
Outgoing:
Change sets:
(1036) *--@ <No>

C:\Sandbox\Cognos_SSSMP_huji\Cognos_SSSMP>scm list credentials
https://cyspqpvspaap001.cihs.ad.gov.on.ca:9443/ccm/, huji, rtc, <No>
, <No>, <Password>

Is the current directory content loaded from the production server or the test server?

Is the current directory content loaded from the production server or the test server?

test server. I used the same nickname to login to production and test. Maybe it's confused.

If what you've indicated is your work flow, you're not even using the session associated with the stored credentials as displayed with scm list credentials. Because you're not adding -n rtc (the nickname of the production server login session), you are being prompted for the password to your test server.

As you are only wanting to work on your local test server, to correctly use the saved session, you should have:

1. scm login -c -r https://localhost:9443/ccm/ -u huji -P <passwd> -r rtc
2. lscm checkin -n rtc
3. lscm status -n rtc

This will eliminate the Password (huji @ https://localhost:9443/ccm/): prompt each time you execute an lscm command.

Note that if you do not do an explicit scm logout -n rtc, the session will persist until you do so.

It's the production one! How can I get rid of it?

C:\Sandbox\Cognos_SSSMP_huji\Cognos_SSSMP>scm list credentials
https://cyspqpvspaap001.cihs.ad.gov.on.ca:9443/ccm/, huji, rtc, <No>
, <No>, <Password>

I don't understand. I logout from the production session and login to test again, and now everything works fine. Why it's still store the production one. What does this credentials mean?

C:\Sandbox\Cognos_SSSMP_huji\Cognos_SSSMP>lscm checkin "Release Notes.txt"
Password (huji @ https://localhost:9443/ccm/):
Committing...
Workspace: (1000) "Cognos SSSMP Development Stream Workspace -huji" <-> (1001) "
Cognos SSSMP Development Stream"
Component: (1002) "Cognos_SSSMP" <-> (1001) "Cognos SSSMP Development Stream"
Outgoing:
Change sets:
(1036) *--@ <No>
Changes:
---c- \Release Notes.txt

C:\Sandbox\Cognos_SSSMP_huji\Cognos_SSSMP>lscm status
Password (huji @ https://localhost:9443/ccm/):
Workspace: (1000) "Cognos SSSMP Development Stream Workspace -huji" <1001>

Component: (1002) "Cognos_SSSMP" <-> (1001) "Cognos SSSMP Development Stream"
Baseline: (1005) 2 "v1"
Outgoing:
Change sets:
(1036) *--@ <No>

C:\Sandbox\Cognos_SSSMP_huji\Cognos_SSSMP>scm list credentials
https://cyspqpvspaap001.cihs.ad.gov.on.ca:9443/ccm/, huji, rtc, <No>
, <No>, <Password>

If what you've indicated is your work flow, you're not even using the session associated with the stored credentials as displayed with scm list credentials. Because you're not adding -n rtc (the nickname of the production server login session), you are being prompted for the password to your test server.

As you are only wanting to work on your local test server, to correctly use the saved session, you should have:

1. scm login -c -r https://localhost:9443/ccm/ -u huji -P <passwd> -r rtc
2. lscm checkin -n rtc
3. lscm status -n rtc

This will eliminate the Password (huji @ https://localhost:9443/ccm/):

prompt each time you execute an lscm command.

Note that if you do not do an explicit scm logout -n rtc, the session will persist until you do so.


This explains most of the problem. But why the stored one is not the test one (localhost), the last login I issued is for test like this: scm login -c -r https://localhost:9443/ccm/ -u huji -P <passwd> -r rtc

test server. I used the same nickname to login to production and test. Maybe it's confused.

As I noted in a previous reply, you can have only a single session active using a particular user name. I don't know if this is how RTC CLI is supposed to work but my observations seem to merit this behavior.

If you first created a login session to the test server using your user id, then later created a login session to the production server using your user id, your original test server session no longer exists.

Further, you inflicted more damage/confusion upon yourself by using the same nickname to access both your test and production servers. If you had used -r rtc_test and -r rtc_prod to distinguish the sessions, you'd have known the session to your test server was closed as lscm ... -n rtc_test commands would once again start prompting you for a password (not using stored credentials).

This explains most of the problem. But why the stored one is not the test one (localhost), the last login I issued is for test like this: scm login -c -r https://localhost:9443/ccm/ -u huji -P <passwd> -r rtc

No idea. I've always run list credentials after a login just to verify.

This explains most of the problem. But why the stored one is not the test one (localhost), the last login I issued is for test like this: scm login -c -r https://localhost:9443/ccm/ -u huji -P <passwd> -r rtc

No idea. I've always run list credentials after a login just to verify.

Thank you very much! I think I got the point.

The problem is the document and sample in infocenter never mentioned this. The checkin, status command has even no -n parameter mentioned:
http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0/topic/com.ibm.team.scm.doc/topics/r_scm_cli_status.html

Jirong