RE: IN070 dumps sometimes...

IN070 has a nasty habit of failing due to record locks.  We added record
lock handling so that it retries the transaction until it is successful.

Duane Chaloupka
Hach Company

-----Original Message-----
From: Jeff_Klipa/Harvard@harvardind.com
[mailto:Jeff_Klipa/Harvard@harvardind.com]
Sent: Wednesday, September 13, 2000 7:46 AM
To: JBAUSERS-L@midrange.com
Subject: RE: IN070 dumps sometimes...


I don't know if anyone else has this problem or not...

We've been noticing occasionally that the MJ_CONTROL job will leave a dump
or two in the IPGDUMPS Outq for us to find...  If we were not looking for
them we wouldn't have found them...  And what we found gave us cause for
alarm...

The dump said that program IN070 failed because a certain record in STKBAL
was in use...

Sure enough the inventory transaction that was trying to process in IN070
simply fell on the floor and never got processed...

What job had the lock on the STKBAL record...?  Well we have narrowed it
down to two possible options...
PM010       Receipts entry
PM024       Returns And Adjustments.

What we discovered is that our Receiving person is in the habit of leaving
the receiving program open and this is what we believe caused the lock to
STKBAL and ultimately IN070 to fail...

We can educate the user to exit the program when not in use but what about
those failed inventory transactions...?
There must be many other failed transactions that have gone unnoticed in
our shop and I would suspect in yours as well...  This leaves the integrity
of our inventory levels in serious question...

We will have a hard time duplicating the problem given the way IN070 is
called from everywhere and we cannot really tell what the Inventory
transaction was that failed without more detailed analysis...  We're toying
with the idea of adding a mod to IN070 to capture the LDA info whenever it
fails due to a lock on STKBAL and this seems like the most prudent thing to
do at this point...  Exactly how we'll capture that info and what we do
with it after we've got it is another matter...

We're trying to come up with a comprehensive solution but thought I'd
mention it to the list and see if anyone else had run across this yet...
And if so, do you have a solution for picking up those lost
transactions...?

We're on V3.5.1 presently...

Thanks.


+---
| This is the JBA Software Users Mailing List!
| To submit a new message send your mail to JBAUSERS-L@midrange.com.
| To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com.
| To unsubscribe from this list send email to JBAUSERS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: doug333@aol.com.
+---
+---
| This is the JBA Software Users Mailing List!
| To submit a new message send your mail to JBAUSERS-L@midrange.com.
| To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com.
| To unsubscribe from this list send email to JBAUSERS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: doug333@aol.com.
+---