Problem during Transporting TOC

[former_member588890]

Hi.

I am facing the problem while transporting the TOC from Development to Quality.

I include the object from my task and select the first radio button (object list from my request).

then while transporting directly I got one popup screen saying " Not all object in the request could be locked with an option, Release Anyway, Error details or Cancel.."

I am not sure about this. How to resolve this issue? Could you please guide me!

[RaymondGiuseppi]

Release the original task.

[matt]

Many companies use ToCs as intermediate transports for testing. When testing is complete, original transport is released and transported through to production. ToCs only go to testing. I assume that this is what your company is doing.

If so, you should choose the option "Release Anyway". This leaves the objects locked in the original transport, but allows the ToC to take the current version across. It also creates new versions of the object.

Do note though that you should ask this question locally and seek confirmation. Company policies and procedures vary from one place to another. I might be giving you advice that doesn't apply in your company, and would get you into trouble.

[Tomas_Buryanek]

Is it really a problem?

One object can be locked only in one transport task (usually "original transport"). And if you are transporting just TOC, then it seems to be OK to not lock objects in in. Because it is just Transport of Copies. You are not releasing/transporting original transport. You just use TOC to get current DEV object to Q.

[Sandra_Rossi]

One object can be locked in only one modifiable transport request at a time. It means that:

1. either some of the objects are locked in another modifiable transport request
2. or not locked by anyone at all.

Try to lock them in your transport request (option in the menu of the transport request). It will fail if some objects are already locked in other transport requests (case 1), or objects will be locked in case 2.

If objects can't be locked (case 1), ask the people who are working on these objects if they agree to transport them via your transport request. If so, they will delete the object entries from their transport request, and you may then attempt the lock again.

There are cases where you still want to transport an object even if it's in several transport requests (case 1), for instance because the object is used by 2 programs, and maybe it could still evolve. In that case, you may "Release anyway", but make sure that the other developer gives his agreement, to avoid releasing the object at a moment he's changing the object.