RE: V5R1 question - CPF4238 & SQL7008

[Dennis Munro <DMunro@xxxxxxxxxxxxxxxxxxxx>]

Clare,

Well, it seems as though I have a little egg on my face.  I was trying to
get the INV903 process automated for my month-end to run via a CL program &
had recompiled the program w/o the COMMIT set to *NONE on my test box.  So,
I had forgotten all about doing that about 6 weeks ago & when I ran
month-end on the test box Monday to see what gotchas V5R1M0 would bring, the
error occurred.  Just like shooting yourself in the foot.  I had called SSA
help line & they were able to help me get it resolved fairly quickly - at
least what the problem was.  According to them, ALL programs should be
compiled with the COMMIT set to *NONE because that is the way they ship
BPCS.


Thanks - Dennis.

Dennis Munro

"I love deadlines.  I especially like the whooshing sound they make as they
go flying by."  Dilbert's Words Of Wisdom:

Badger Mining Corporation
www.badgerminingcorp.com
dmunro@badgerminingcorp.com
(920) 361-2388

-----Original Message-----
From: Dennis Munro [mailto:DMunro@badgerminingcorp.com]
Sent: Monday, September 30, 2002 12:15 PM
To: 'midrange-l@midrange.com'
Subject: RE: V5R1 question - CPF4238 & SQL7008

Clare,

<snip>
We got this error msg too, and it looked as though the default for COMMIT
has changed on the CRTSQLRPG cmd. It needs to be *None for BPCS.
<snip>

When no programs have been changed, how can that be a factor or I don't
understand something?.  I'm running 6.0.02 full client server so all my
source is in ASSET which is something I try to make as few modifications as
possible.

Thanks - Dennis.

Dennis Munro

"I love deadlines.  I especially like the whooshing sound they make as they
go flying by."  Dilbert's Words Of Wisdom:

Badger Mining Corporation
www.badgerminingcorp.com
dmunro@badgerminingcorp.com
(920) 361-2388

-----Original Message-----
From: Clare Holtham [mailto:Clare.Holtham@btinternet.com]
Sent: Monday, September 30, 2002 11:33 AM
To: midrange-l@midrange.com
Subject: Re: V5R1 question - CPF4238 & SQL7008

Hi Dennis,
We got this error msg too, and it looked as though the default for COMMIT
has changed on the CRTSQLRPG cmd. It needs to be *None for BPCS.
cheers,
Clare