Let me point out that there's a different between "change management" and
version control of source.
Granted, version control of source is usually built into CMS.
But there's a world of difference between for instance using Git for
version control and using Aldon LM(i) or PTC Implementor; the latter not
only controls source but handle automated deployments of new objects to
production (useful even if you have development and production on the same
Also note that for instance, Aldon LM(i) only works with objects in the
library file system. If for instance, you've got java/php source, .html
files or other types of stream files in the IFS you'd want handled by the
CMS, you have to move up to the LM(e) product; which IMHO is overkill (and
overpriced) for IBM i centric shop. Even if you don't currently need IFS
support...you will sooner or later.
On Wed, Jul 23, 2014 at 1:21 PM, Kurt Anderson <Kurt.Anderson@xxxxxxxxxxxx>
We're a shop of at most 4 people who would be checking in and out source.
I'm doing a little preliminary investigation to pass on to my manager to
see about budgeting some change management software for the next year.
I know there are people on the list who work with CM companies (such as
David), so I'm open to both vendor responses as well as small shop CM
software experiences people have had.
One product I looked at while at the last conference I attended was
TD/OMS. Has anyone had experience using that product?
Sr. Programmer/Analyst - Application Development, Service Delivery Platform
web: www.customcall.com<http://www.customcall.com/> | email:
A Division of Enghouse Systems Ltd.<http://www.enghouse.com/> (TSX:ESL)
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives