Why did you initially copy your workspace from A to B? Do you intend to
use the files on disk in location A in the future with that repository
workspace? What do you mean by auto-sync with your remote workspace (is
workspace A part of a build process? Or do you just mean it uses
auto-commit turned on?)

Loading into location B sounds like the proper thing you should be doing.
Loading 1 workspace into more than 1 locations can still make you
out-of-sync, but perhaps in a way thats more expected than copying your
filesystem. In either case, can you describe what you're trying to do to
give more context?


On Tue, 11 Aug 2009 12:53:00 -0400, zhengxie
<zhengxie> wrote:

See the following error in error log
Status INFO: com.ibm.team.filesystem.client code=4 Contents are out of
sync. Consider creating a patch and reloading. null children=

I think it is because I have two sandboxes.

I had a workspace in location A, then in the file system, I move it
from locaiton A to location B. then start workbench in location B.
Jazz source control now has two sand boxes each in location A and B.

How can I change to use location B only?

My local workspace is in auto snych with my remote repository. I'm not
allowed to deliver then load into location B.

Thank you for your help.

--

I think you should be able to just delete your location A and do load in
location B (sounds like you didn't want A to begin with).

The out of sync should only be a problem if you have loaded the same stuff
into A as the stuff B.
- If you have changes in A that you want to keep, and see them reflected
in B, then check them in (they should be automatically checked in because
you have auto-check in on.). This puts B out of sync.
- Now that everything you want in A is checked in, you can delete A, or
atleast the parts of A that overlap with the parts of B. Having multiple
sandboxes is ok and will not cause out of sync if there's a 1-to-1 with
the contents of the sandboxes on disk compared to the repository workspace.
- Now reload B to make the out of sync go away.

If I'm reading you correctly I think you're misunderstanding the
relationship of checkin (and auto-checkin) vs deliver. When you say "You
can't deliver the change set and then load again", this is because you're
not ready to share with the stream, right? Well that's ok because the
auto-checkin should have copied your changes from your local workspace
into the repository workspace. (and now you have an outgoing change to the
stream). You do not need to deliver to the stream to load your workspace
again. Your repository workspace should have the changes that you want to
keep. And the stream will continue to not have them until you do the
deliver.

I hope that clarify things. Let me know if its still confusing or if
you're cautious about losing some of your changes.





On Wed, 12 Aug 2009 05:08:04 -0400, zhengxie
<zhengxie> wrote:

Hi Andrew, thanks for the reply.
I meant to load files into Location B on my local drive, but by
mistake, loaded into location A. Now I have part of my workspace
loaded into A, another part into B, which causes out of synch
problem.
By "auto-synch", I mean in preferences, "Jazz Souce
Control" - "Check-in policies" - "Perform
check-in wheneer a resource is modified" is selected.
Can you let me know, how can I change to only use location B?
I can't deliver the change set and then load again.
Thanks a lot.
Zheng


Andrew Hoowrote:
Why did you initially copy your workspace from A to B? Do you intend
to
use the files on disk in location A in the future with that
repository
workspace? What do you mean by auto-sync with your remote workspace
(is
workspace A part of a build process? Or do you just mean it uses
auto-commit turned on?)

Loading into location B sounds like the proper thing you should be
doing.
Loading 1 workspace into more than 1 locations can still make you
out-of-sync, but perhaps in a way thats more expected than copying
your
filesystem. In either case, can you describe what you're trying to
do to
give more context?


On Tue, 11 Aug 2009 12:53:00 -0400, zhengxie
zhengxie> wrote:

See the following error in error log
Status INFO: com.ibm.team.filesystem.client code=4 Contents are out
of
sync. Consider creating a patch and reloading. null
children=

I think it is because I have two sandboxes.

I had a workspace in location A, then in the file system, I move it
from locaiton A to location B. then start workbench in location B.
Jazz source control now has two sand boxes each in location A and
B.

How can I change to use location B only?

My local workspace is in auto snych with my remote repository. I'm
not
allowed to deliver then load into location B.

Thank you for your help.



--

--

Maybe take another glance over http://jazz.net/library/article/40 and
http://jazz.net/library/article/41

I'll just explain some stuff here anyways and hope that some of it
overlaps with what you're doing.

With your multistream development, you're working with 3 'configurations
(places where your files live).
1) Your local workspace
2) Your Repository Workspace
3) The stream, shared by the team.

When files are sent from your local workspace to your repository
workspace, we call that a checkin. When they go from your Repository
Workspace to the stream we call that deliver.
- Since you have auto-checkin on, your local workspace and repository
workspace are always in sync... so it might only look like you have 2
configurations. Your stuff (local workspace = repository workspace), and
secondly the stream.

The pending changes view shows when your repository workspace and stream
are different by incoming/outgoing changesets. (the pending changes view
also shows when your local workspace is different from your repository
workspace via unresolved-file changes... but you won't see that since you
have autocheck-in turned on).

So when you do a deliver, all 3 configurations look exactly the same.

Now, you've said you've unloaded and you want to load 'only the projects
that are different', but you don't know which those are because they have
'disappeared' from the pending changes view. What the pending changes view
is telling you is that all 3 configurations are the same! There is no
difference and so your question of 'how do I see the projects that are
different' doesn't make sense. If you wanted to review your changes that
are 'different', you should have done that while they were 'outgoing
nodes' before you delivered.


Depending on how you work, you might be getting confused with what you
expected compared to either
1) working with auto-checkin turned off, which then has an extra step of
checking it but might make things more clear
or 2) maybe you're thinking of 'projects that are different' in your
stream compared to yet-another stream (like an integration stream or
something).


I hope that helps.


On Thu, 13 Aug 2009 13:23:04 -0400, zhengxie
<zhengxie> wrote:

Thanks Andrew. You are right.

So I did some reload and resolved some unresolved changes. A lot of
back and forth, seems a lot of safety checks have being build into
Jazz, at last I was fine even I was worried in the beginning:-). Good
job!

Now I did unload, so all the projects are deleted from my local
workspace. I have Pending Changes view open, from which I'd like to
load only the changed projects into my local workspace, but I don't
seem to be able to find out how to.

If a change set is delivered, it disappears from Pending Changes view.
If I'd like to see a list of delivered change set on a stream, what
can I do?

If you think I should have done my research before asking question,
please tell me... I did look at the tutorials...

Thanks a million.

Zheng

--