How to import transport of copies to productive systems

Question

Hello,
I have been experiencing a problem that even the guys from admin could not solve (yet). I should say I work in a development team.
Imagine you have two landscapes, one DEV-QAS(1) to develop big projects and a normal DEV-QAS-PRD(2) landscape where my objects will be imported. After a new group of objects is finished in (1), we ask to import the workbench request in the STMS queue of DEV(2). After this, and after some small test, we create a transport of copies in DEV(2) where we include the first transport, release it and import it to the QAS(2) queue. After the tests in QAS(2) the idea would be to import the transport of copies to productive system PRD(2). But it does not work...
In STMS queue for PRD(2), there is no entry for the transport of copies. Also, when I tried to add the transport request to the import queue (via menu -> Extras -> Other requests -> Add), I get an error message stating that no co-files where found for the transport.
Does anyone know this problem? I suspect it can have sothing to do with the use of a transport of copies, but, if I don't use this kind of transport, how can I get objects from other systems to production?
Thanks in advance.
Davide Sepanas, Portugal

Answer 1

Davide,
Re your latest questions:
> 1) Why this problem with transport of copies doesn't happen from DEV(2) to QAS(2), since these systems are also not in the same transport directory?
>
I think the answer is in your original problem description:
we create a transport of copies in DEV(2) where we include the first transport
>
When you create a transport of copies you must indicate a terget system and I suppose you enter QAS(2) there. In that case the TMS will add the request to the import buffer of the target system when you export the request from DEV(2). I understand that you never have to add transports of copies to the import buffer of QAS(2) manually, which proves the TMS does this for you. However, for further imports into systems that are not designated as target system of the transport of copies, like PRD(2), the TMS will do nothing of the sort and you must add the request to the queue yourself - which in your case also means you have to forward the transport files first.
> Can we assume, then, that, where I was working before, all three systems were configured in the same transport directory, avoiding thus the problem with the transport of copies requests?
Yes, and that is the most common way of setting up the transport system. Having separate transport systems really only makes sense when sharing the transport directory between the dev, qas and prd systems (via NFS for UNIX, via network shares for Windows) is not possible, either because there is no local network between the servers or because some security policy forbids it. I'd advise you to certainly ask the question to your system admin.
Regards,
Mark