Re: SQLRPG/*DFTACTGRP Problem

We loaded v5r1 about a month ago, but we've had some nagging issues --
mostly involving print queues and communications with Domino -- so our
systems guy has been applying ptfs periodically. He says he put some on
over the weekend (commitment control didn't ring any bells with him, but
he's going to pass on the release notes for me to look at), but I checked
with the users and the programs that broke worked fine on Monday and
Tuesday. When I get a chance, I'll check out the log for Tuesday night,
but I may have to chalk it up to "just one of those things" . . . .

Thanks for your help!

midrange-l@midrange.com writes:
>There's some autocommit stuff in v5r1, probably some
>other differences in the CRT commands. Have you had an
>upgrade since the OPM was built?
>> Okay, I've got some more information -- after doing some tests, I found
>> that the problem seems to be with commitment control -- when I added a
>> "set option commit=*none" statement to my OPM program, the problem went
>> away. But I still wonder what was going on here, since the SQL statement
>> was a simple select, and I had even declared the cursor as "read only"
>for
>> performance reasons. Why do I also have to turn off commitment control,
>> but only in OPM?
>>
>> I guess if nobody answers that means everyone else is as baffled as I
>am.
>> . . . :-)
>>
>> Thanks very much,


Mike Naughton
Senior Programmer/Analyst
Judd Wire, Inc.
124 Turnpike Road
Turners Falls, MA  01376
413-863-4357 x444
mnaughton@juddwire.com