RE: audit source member adds/mods/deletes

Dan,

IMHO, thinking that a change management system is strictly for larger shops
is a mistake.  My first exposure to Aldon CMS was at a two-man shop were I
did all the iSeries development!

I think the smaller shops benefit almost as much from CMS than the larger
shops do.  The development process is more efficient and you get to
concentrate on writing code.  Granted, a long established shop probably has
plenty of own grown tools to help.  But again, how much time is lost
maintaining those tools?  Can you keep using those tools from WDSc?

One final point in regards to CMS raising the complexity level for what you
are trying to accomplish; CMS complexity should be tied up in the setup and
configuration.  For day to day use, I'd think you'd find it let complex to
use than a manual process.  I strongly believe that I could never have
accomplished as much as I did on my own at my previous employer without a
CMS system.

Charles


> -----Original Message-----
> From: Dan Bale [mailto:dbale@xxxxxxxxxxxxx]
> Sent: Monday, June 28, 2004 10:38 AM
> To: Midrange Systems Technical Discussion
> Subject: RE: audit source member adds/mods/deletes
> 
> 
> 
> Good points to consider, Charles.  CMS, by its definition & 
> purpose, is not
> really the issue for us, and would really raise the 
> complexity level for the
> simple tracking we are attempting to accomplish.  I don't 
> want to have to
> force check in / check out processes -- there aren't that 
> many of us that we
> can't keep track of who is working on what.  Not to mention 
> the expense of
> CMS.  As far as resources, we are literally "swimming" in 
> available DASD &
> CPU, so resources are not an issue (at this time).  At the 
> very least, we
> need to see what the resource hit will be.
> 
> Thanks,
> db
>