Bradley,
   CISC to RISC was not a big deal provided you a) never removed
   observability from your *PGM objects and b) didn't use very much DFU. 
   Observability is the big issue.  If you, for any reason, have removed
   observability from your compiled programs, then they need to get
   recompiled again.  On the surface, that's not a hard thing unless you
   can't find the source code at the right level for the *PGM object you need
   to recompile.
   In earlier days, removing observability was a not-to-uncommon way to
   conserve on disc space.
   Rich Loeber
   Kisco Information Systems
   
http://www.kisco.com
   --------------------------------------------------------------------------
   "Bradley V. Stone" wrote:
     I seem to recall CISC to RISC wasn't much of a pain.  restore it on a
     new
     machine, and the first time it ran it did the conversion.  Am I
     forgetting
     something? :)
     In the past, my software was V3R2..  no problems up to V5R4.  Recently I
     upped it to V4R5 and yes, I still get asked if I versions for previous
     OS
     releases to V4R5.
     So, I guess my question is, what did I forget about (probably
     convenietly)
     that made CISC to RISC so bad, and if I compile for V4R5 won't these
     just
     autocovert on V6R1 like CISC to RISC did?
     What I see the issue being for ISVs is needing at least 2 partitions for
     support.. V6x and V5x.  Ugh...
     Bradley V. Stone
     BVSTools - www.bvstools.com
     eRPG SDK - www.erpgsdk.com
     > -----Original Message-----
     > From: midrange-l-bounces@xxxxxxxxxxxx
     > [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of David Gibbs
     > Sent: Monday, July 23, 2007 12:38 PM
     > To: Midrange Systems Technical Discussion
     > Subject: Re: New redpaper: i5/OS Program Conversion: Getting ready for
     > i5/OSV6R1
     >
     >
     > Rich Loeber wrote:
     > >    If you went through the CISC to RISC conversion, this will
     > be about the
     > >    same level of pain.
     >
     > For those ISV's out there that support releases earlier than V6R1, the
     > pain will be even more ... because we'll have to (effectively)
     maintain
     > two versions of software (assuming we don't want to make our customers
     > go through the regeneration process during install) ... one for V5R4 &
     > lower, another for V6R1 & higher.
     >
     > david
     >
     > --
     > System i ... for when you can't afford to be out of business
     > --
     > 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.
As an Amazon Associate we earn from qualifying purchases.