RE: V5R1

The application could have errors also.  Like the bloke earlier who had the
problem because he was hardcoding his offsets in his trigger programs.  Not
really a V5R1 bug.

Rob Berendt

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



                    David.X.Kahn@gsk.co
                    m                         To:     midrange-l@midrange.com
                    Sent by:                  cc:
                    midrange-l-admin@mi       Fax to:
                    drange.com                Subject:     RE: V5R1


                    11/13/2001 12:06 PM
                    Please respond to
                    midrange-l






Dan said,

> If you are purchasing a package to run on the new box,
> make sure that the package is compatible with V5R1.

That's correct, and I know it needs to be done. However, I always have a
little trouble getting my head round this. Assuming the package is not
using hacks, which most of them don't nowadays if they can run at security
levels 40 and 50, there ought to be nothing in a new release that will
break it (other than relying on some dropped feature such as OV). And if
they are using hacks we're back into the territory of Ed Fishel's warnings
about what IBM are happy to support us on...

Dave...

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