Re: CPF5035 used to be ignored, now causes SQL to fail

Hi Joe
based upon the contents of this thread, did you apply the release update(s)
directly to your production box?

I am pushing to upgrade to 6.1, so it looks like I will also have to push
to upgrade our development box first and run on there for a while before
applying the release update to the production box
We normally do the development box first anyway, but I just want to make
sure that the same process is followed

Alan Shore
Programmer/Analyst, Direct Response
E:AShore@xxxxxxxx
P:(631) 200-5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill



Joe Pluta
<joepluta@plutabr
others.com> To
Sent by: Midrange Systems Technical
midrange-l-bounce Discussion
s@xxxxxxxxxxxx<midrange-l@xxxxxxxxxxxx>
cc

01/19/2011 03:18 Subject
PM Re: CPF5035 used to be ignored, now
causes SQL to fail

Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>






On 1/19/2011 1:38 PM, Nathan Andelin wrote:

I've run out of ideas.

That's hard to believe. You're usually a fountain of ideas ;-)

When some of our code broke, moving to V6R1, it annoyed me at first. Then

I

realized that I was in no position to complain about it. If you can't

count on

having numeric data in a numeric field, should you change it to

character?

Something like that?

-Nathan

I just wish there had been a compatibility switch in QAQQINI.
DECIMAL_ERRORS with options of *IGNORE, *REPORT and *ERROR. We could
turn on *REPORT and errors would be logged and we could fix the programs
as they occurred. I fear the month-end and year-end job streams...

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