First, Rocket/Aldon support is quite good. They may have an answer. I
presume they helped you with the initial setup.
When promoting a PF you typically also promote dependent objects, which
may be other PFs, LFs, programs, etc. I imagine that is what you did.
In theory when Aldon moves an object on to the next environment it
deletes it in the from environment if it is no longer needed there.
That said, I do have a feeling that it leaves some stuff around that it
shouldn't. Might be due to objects that are associated with more than
one open task.
And by environments, I assume you mean INT and QUA? Or were you also
referring to data libraries?
Sam
On 2/28/2013 5:14 PM, Peter Thomas wrote:
We have recently installed Aldon LME on our system and we are finding it quite different from our previous change control system.
I would be interested to hear from people who have been using Aldon for a while how they handle Physical File promotions.
We are finding that Aldon seems to leave objects in all environments that are recreated due to file dependencies.
Previous change control system would only leave objects in environments where there was still a dependency required.
Any help would be appreciated.
