Our standards committeee has decided to use either PCVS or CVS as our company standard version control software since we have a wide array of development platforms -- RPG/COBOL (iSeries), C/C++, Java, HTML (various warehouse/distribution apps run within our server farm). <p>I've been asked to look into how we could use the aforementioned version control software on the iSeries. We are currently developing w/in SEU only yet we're anticipating moving to WSDc. <p>I'm open for ideas...

Bob, <p>I had a similar task of implementing across the board source / version control for our development projects. There are several commercial products that facilitate cross-platform source / versioning control / SCM including traditional green-screen development on iSeries. There is a CVS client for iSeries <a href="http://store.march-hare.com/s.nl/it.A/id.47/.f?sc=2&category=2">http://store.march-hare.com/s.nl/it.A/id.47/.f?sc=2&category=2</a>. However in my case the budget for this initiative was rather limited and that effectively excluded most of commercial options. <p>There is a built-in support for CVS in WDSc but for several reasons this option was discarded: <p>- Development teams are geographically dispersed and not all developers have ability / hardware to install and / or be productive with WDSc <BR>
- At the time it was available only for the so called iSeries projects (where developer maintains the code in the studio and then pushes it to the iSeries, as opposed to direct editing of the source on iSeries. <p>So the solution we finally came up with was the daily automatic load of all sources from our development system into CVS (later we migrated to Subversion) using a process on iSeries that copies all sources from development libraries into staging folders on IFS and Window batch process that loads new / changed sources into the repository. The trade off was that this does not allow to track particular change to particular developer and just captures the day's worth of changes. <p>Dmitriy Kuznetsov