Re: New redpaper: i5/OS Program Conversion: Getting ready fori5/OSV6R1

Rich -

It is a BIG problem if you are a JDE shop that long ago dropped the overpriced Oracle support.

I know from first-hand experience - in 1992 my client (who had dropped support from JDE) was upgrading from a S/38 to an AS/400. JDE wanted 250,000.00 in back support payments to simply supply us with a set of tapes that would restore on the AS/400, since the JDE back-office programs had observability removed from them and would restore on the AS/400 (no source was supplied for these programs, since they were considered proprietary code...).

IIRC, there were some programs that had to be recompiled even though they were observable.

- Steve

----- Original Message ----- From: "Rich Loeber" <rich@xxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Monday, July 23, 2007 1:12 PM
Subject: Re: New redpaper: i5/OS Program Conversion: Getting ready fori5/OSV6R1

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.

--------------------------------------------------------------------------------

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