RE: Any con's to getting rid of our development box and justrunn ing it as a partition?

Thanks for your insight.  Yes, we will continue to keep our development 
boxes at or above our production box.  At one time (back when the 
divisions had their own 400's) we told one division that kept postponing 
their upgrade that they were SOL.  We can't compile to them anymore.  They 
upgraded within 4 weeks.

Granted, we don't peddle to external customers.  And if we do I can't see 
how a company too cheap to upgrade from V2R3 would spend any money buying 
a new software package.  Therefore I wouldn't see any need to market to 
that crowd.  And, as I've stated before, some of the techies using your 
software would love you to stop supporting older releases of the OS. 
Therefore they would have a business case to upgrade their OS.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 





"James H. H. Lampert" <jamesl@xxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
08/19/2003 04:48 PM
Please respond to Midrange Systems Technical Discussion
 
        To:     <midrange-l@xxxxxxxxxxxx>
        cc: 
        Fax to: 
        Subject:        RE: Any con's to getting rid of our development 
box and just runn       ing it as a partition?


> "820 - Development.  Second to get new versions of OS/400."

If your development box gets new versions of OS/400 before the production
system, you've effectively negated one of the biggest advantages of having
a separate development box. Consider:

The development box we use for QuestView (tm), and for all other MI
development, is a D02, running V2R3, completely isolated from the outside
world for security reasons. Thus, even if a potential customer is still
running V2R3, he or she can still run the latest version of QV. The
development box we use for Wintouch(tm) (except for a few MI programs) and
to develop stuff for internal use, is running V4R4. The system we use for
most other commercial product development, and for re-encapsulating stuff
from the V2R3 box to run on RISC machines (and then pulling out the
observability) runs V4R2. And an old production box we now only use to
walk stuff back to V2R3 is running V3R2.

Our production box, on the other hand, runs V4R5.

Thus, our commercial products will run on a much lower release level of
OS/400 than they would be able to if we ran our development boxes on a
more current release. Of course, occasionally that will mean that I'm
coding some new QV feature completely blind, and need to transfer it to a
different box to see if it works, but as infrequent as that occurrence is,
not having to turn away people on antiquated systems is worth it.

But in your situation, if you're running your development boxes ahead of
your production boxes, I see no reason to even keep them around as
separate boxes.

--
JHHL


_______________________________________________
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.