Re: Source Code management - Migrating packages

We also use MKS

One of the nice things it does for you is warn you that someone else has
already checked a source out. You then have the option of taking a copy of
the production version or the one that has already been checked out (Hint -
use the production version.)
It will also halt you when you attempt to promote the changed version and
inform you of the concurrent development of that source.

Our cycle is that we check out the source (see above), change it in
development (with unit testing). Promote into QA for testing by the QA
group. Then promote it into PRODUCTION.
You also have the option of rejecting from QA into development.
One option I wish was available. When a reject from QA back to development
is required (project cancelled etc) would be to have the option of
refreshing QA with the version in production, instead of manually having to
do this



Alan Shore
Programmer/Analyst, Distribution
E:AShore@xxxxxxxxxxx
P:(631) 200-5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill

midrange-l-bounces@xxxxxxxxxxxx wrote on 05/27/2009 01:31:05 PM:

Seeing as how David works for MKS, we'll mention them first. :)

Others include Aldon and Softlanding (now own by Unicom). Those are
the major players AFAIK.

I've used Aldon for a number of years, it's decent, but sometime a bit
behind the times IMHO.

Softlanding used to have a pretty good rep from what I saw, but that's
changed some since they got bought out.

If I was looking today, I'd take a hard look at MKS. Mainly because
of David and these lists.

HTH,
Charles

On Wed, May 27, 2009 at 1:12 PM, <fbocch2595@xxxxxxx> wrote:

Hi, my company has never used source code management software

and/or a change management system but wants to do so this year.?

How many vendors are there in this space...on the AS400 and if

anyone wants to share?pro's and con's that'd b/appreciated...or
things to watch out for.???

Thanks, Frank


-----Original Message-----
From: McGovern, Sean <Sean.McGovern@xxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Thu, 21 May 2009 9:27 am
Subject: RE: Source Code management - Migrating packages



Rob,

Can you expand on the difficulties you have encountered when promoting
programs that use adopted authority ?

We are aiming to 'upgrade' our current systems (where all users have
*ALLOBJ - seriously), to use a program adoption security model.

Thanks.
Sean


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: 20 May 2009 21:52
To: Midrange Systems Technical Discussion
Subject: Re: Source Code management - Migrating packages

I use the CM software very minimally.  I'm more of an administrator.

In

fact, running one program a week through CM would be busy for me.  I
have
a few people who can give you more of a reference.

Don't skimp on training.

From the 10,000' level it seems there are a substantial number of work

arounds going on.  Like difficulties promoting a program with adopted
authority and that stuff.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From:
"Christen, Duane" <Duane.Christen@xxxxxxxxxx>
To:
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Date:
05/20/2009 04:18 PM
Subject:
Source Code management - Migrating packages
Sent by:
midrange-l-bounces@xxxxxxxxxxxx



Rob;

How was the migration from Turnover to MKS?
How steep is the learning curve?

Duane Christen
--








[http://www.paetec.com/eSignature/My_PAETEC_signature_r1_c1.gif]

[http://www.paetec.com/eSignature/My_PAETEC_signature_r1_c2.gif]


[http://www.paetec.com/eSignature/My_PAETEC_signature_r2_c1.gif]<
http://www.paetec.com/>



Duane Christen
Senior Software Engineer
(319) 790-7162
Duane.Christen@xxxxxxxxxx<mailto:Duane.Christen@xxxxxxxxxx>



[http://www.paetec.com/eSignature/My_PAETEC_signature_r3_c1.gif]





--
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,
visit: http://lists.midrange.com/mailman/listinfo/
midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



--
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.