RE: Change Managament multi-platform support, setup support, cons ulting

[rick.baird@xxxxxxxxxxxxxxx]

Charles,

Thanks for the info - I was surprised that I got so few responses -
especially when I added the "responses from vendors welcome" line near the
end.  I was expecting to be deluged.

I'm most familiar with Aldon, I used it briefly 5 or 6 years ago at another
assignment, but only as a user - and only with traditionally iseries
specific objects.  It seemed pretty robust even then.

Thanks again,

Rick

---------original message--------
Rick,

1) I think the thing to look at for multi-platform is how the distributions
are done.  IIRC, Aldon and turnover did some things differently.  Don't
remember details, even if I did what was bets for me might not be best for
you.  Other than distribution, there not much to "multi-platform".  It's
not
like iSeries change management with the cross-references and auto
dependency
rebuild.  Lastly, if you don't have any non-iSeries change
management/version control in place.  Aldon is nice since the version
control is built in and PC objects stored on the iSeries.  Handy for
backups.  But, if you're already using PVCS or Sourcesafe or whatever,
Turnover will work with it.

2) Aldon includes 4 days of on-site implementation by default in their
contracts.  I believe Softlanding does something similar.
-----in another post----------
Oh yeah, one other thing.

1) If you're PC development is using MS Visual Studio, might want to look
at
the support for MSSCCI.  MSSCCI allows the change management functions to
be
done from the IDE.  Aldon's Lifecycle Manager (Affiniti)  supports this, I
don't believe Softlanding'sTurnover does.  But you'll have to decide if it
really matters to you or not.


HTH,
Charles