|
Mark, How about using WDSC? With it you can set up connections to your other boxes and browse the source as needed. This is outside of the CMS though. Does Implementer have WDSC plugins? If so, give them a try. WDSC may give you a more integrated look and feel even when the source is on different boxes. -- Scott J. > -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx > [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of M. Lazarus > Sent: Tuesday, December 02, 2003 8:31 PM > To: Midrange Systems Technical Discussion > Subject: Re: change management software > > > Pete, > > At 12/2/03 06:43 PM, you wrote: > >We're using MKS Implementer, currently deploying to 4 > different AS400s. It > >handles multiple development and QA environments, has rudimentary > >concurrent development support > > I was wondering if you knew a way around a limitation we're running > into. The environment I'm working with has Production, > Development and > Source on 3 different boxes. The checkout process works fine. The > limitation is that I can't seem to browse sources that aren't > checked out, > since they're on a remote box. > > This is a large limitation, that in IMHO shouldn't be > there. Is there > any way around it, short of moving the source? > > -mark >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.