Nobody ever starts developing a new program (component) from scratch, typically everybody always starts from a copy of an existing component. Just performing a checkout from baseline is not a solution, because you cannot change the member name, the library type or the application you are checking out from).

To take this even a step further: the (existing) component to be cloned may or may not have the same library type, and typically resides in either of these libraries: 

• In a staging library of the same package or another package.
• In a baseline library of the same application or another application.

So how can you do this cloning in ChangeMan ZMF?

Test environments typically use concatenations of promotion (or shadow) libraries concatenated ahead of production (or baseline libraries). When an application in a test environment produces unexpected results, it is usually caused by old versions of a component still hanging around in one of the promotion (or shadow) libraries  in the concatenation list. That's where the ChangeMan ZMF helpdesk calls typically come in.