Re: Aldon Lifecycle Manager Help.

[Charles Wilt <charles.wilt@xxxxxxxxx>]

Think you're confusing a couple of things...

You could have Aldon manage a *BNDDIR as either non-source or as pseudo-source.

If non-source, then you simply check it out make the changes outside
of Aldon using ADDBNDDIRE, and promote it.

If pseudo-source, you check it out make the changes to the source and
create/promote the object normally.

Pseudo-source is a little more work, especially for existing objects.
But you get better change tracking.

HTH,
Charles


On Fri, Feb 24, 2012 at 1:37 PM, Tyler, Matt <matt.tyler@xxxxxxxxxxxxxx> wrote:
> Aldon manages Pseudo source objects with delete functions thus you do
> not need to perform that operation, it needs to manage the object as
> though it were new on the system (service program objects are similar).
> Aldon does not have a good way to update *BNDDIR entries.  Updating a
> BNDDIR outside of the Aldon management will cause those changes to be
> lost the next time the *BNDDIR is promoted.
>
> The nice part about the Pseudo source is the change tracking.   Bad part
> is that Aldon allows only one check out per release and adds conflicts
> to delta release checkouts.  This can cause an unexpected delay in
> promotion of changes.
>
>
> Contact Aldon support at support@xxxxxxxxx or go to www.aldon.com.
>
> They are very wonderful about answering questions like this.    I send
> them questions all the time and I get responses back quickly.
>
>
> Thanks, Matt
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.