Re: traditional AS/400 code base CMS transition

We changed from Softlanding / Turnover years ago to PTC (david at
midrange.com's day job). We did it at the time solely because Turnover
was dragging their feet on supporting a new version of IBM i. I have ZERO
tolerance for that BS.

Recently I looked at a quote to getting all the rest of our 15 lpars of
IBM i added as destinations for production code. The quote was way too
high for what little went to most of those lpars. For example our MAIL4
lpar runs mainly Domino with just a few programs in our ROUTINES library
for systems management. For what few programs would get sent on an annual
basis we felt that adding CM to that lpar was cost prohibitive. Instead we
spent that end of year capital money burning a hole in our pockets on a few
skids of laptops, monitors and other such stuff.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jay
Vaughn
Sent: Wednesday, January 15, 2020 9:46 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: traditional AS/400 code base CMS transition

CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know
the content is safe.


So, our company was just acquired by another company with deeper pockets
and SoftLanding is asking an arm and a leg now to transfer the CMS to our
new company.

So, we are exploring alternatives.

Could have up to 10-20 iseries devs working on the code base (which is
large - hundreds for files/tables and thousands of pgms)

Any suggestions?

Is there a sharp learning curve for github enterprise (pro), compared to
what we are used to now with TO?

tia

jay
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com