What are your promote settings in the release definition? It's been a while
since I worked with LME, but in LMI, there is a setting in the release
definition that tells the software to always leave objects behind, never
leave them, or only leave something behind if another object might need it
for creation.
Paul Nelson
Cell 708-670-6978
Office 512-392-2577
nelsonp@xxxxxxxxxxxxx
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Peter Thomas
Sent: Thursday, February 28, 2013 7:13 PM
To: Midrange Systems Technical Discussion
Subject: RE: Aldon and file promotions
____________________________________________________________________________
___________
Note: This e-mail is subject to the disclaimer contained at the bottom of
this message.
____________________________________________________________________________
___________
For some reason Aldon doesn't seem to be removing the dependent objects when
it moves from I to Q or from Q to P.
I know that the objects are not there due to other dependencies as I
followed some instructions on the Aldon support web site to clean up the
*CRTNONRES objects and we dropped from around 1500 to about 300.
The problem may be caused by the recursive way Aldon decides which objects
are dependents. For example, we have a few logical files which are joins to
other files. When the physical file is promoted we not only get the logical
for the physical being promoted but it includes the joined physical and all
its logical etc. These extra physicals remain in the environments as
*CRTNONRES.
---------------------------------------------
Peter Thomas
INSURE/90 Consultant, BTS
CGU Insurance
T (03) 9601 8885 (xtn 38885)
M 0412 812 615
E peter.thomas@xxxxxxxxxx
www.cgu.com.au We put the You in CGU.
Please consider the environment
before printing this email.
---------------------------------------------
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Sam_L
Sent: Friday, 1 March 2013 11:54 AM
To: Midrange Systems Technical Discussion
Subject: Re: Aldon and file promotions
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.
midrange.com
