In my instance I was just writing records from MS SQL to db2/400. I could have used messy FTP, but why use unsecured FTP and a more complex process.

Darryl.

Sent from my iPad

On Aug 19, 2015, at 11:28 AM, rob@xxxxxxxxx wrote:

Ken,

I was thinking that somewhere in the back of my mind. And I got a reply
off-list from someone else who said basically the same thing.
But, basically, if you got this error you'd better notice it quick before
other users start complaining about record locks.

So, we may think that a 1 minute run of a huge batch sql statement isn't
that long and is perfectly acceptable. However if you leave record locks
out there for 1 minute you may hear much wailing and gnashing of teeth
from the users. Then, you have to balance that against running WITH NC.

Isn't there also some limit on how big a commitment chunk (?boundary?) can
be?


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Ken Sims <mdrg8066@xxxxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx
Date: 08/19/2015 11:10 AM
Subject: Re: Commitment Control Was: Writing from ms SQL to IBM i
database (Darryl Freinkel)
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Hi Rob -

On Wed, 19 Aug 2015 11:00:07 -0400,
rob@xxxxxxxxx wrote:

Now let's say someone is running some inventory transaction and it
updates
the quantity also
X 205

Huh???

I don't use commitment control, but it's my understanding that the
program doing this update can't commit it until the program that did
the change from 100 to 200 commits that change.

In fact it may be that the program doing this change can't even get a
record lock for update until the change from 100 to 200 has been
committed.

Hopefully someone who knows more about this than me can provide a more
definitive answer.

Ken
Opinions expressed are my own and do not necessarily represent the views
of my employer or anyone in their right mind.

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

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].