Record Locks in Macola - entering Production 1

[bruggles]

We are using Progression 7.6.400 and MS SQL 2000 SP3A. We seem to continue to encounter alot of Record Locks when our production users are entering production. I have noted one issue with a Record Lock seems to be tied when our Materials Manager is using a module in the IM applet and it seems to leave a hook open into the item even after he closes that module, I then note that once a Record lock is encountered that if I log him off of Macola it clears.

Does anyone else run into record locks while entering production? I was wondering if anyone had any input on why these occur and thought the using MS SQL we would not encounter them.

Lastly I was wondering if there is anyway to see which users are locked on the same record? Is there any Query you could run that would show you which 2 users have locked?

TIA

 

[dgillz]

What does "a module in the IM applet" mean? Can you be more specific?

Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports

http://www.gainfocus.biz

"If you have a big enough dictionary, just about everything is a word"
--Dave Barry

 

[kstickler]

We have that problem sometimes during SF activity Transaction entry as well. Also, quite frequently when we are trying to release shop orders. We are on progression 7.6.300c - MS SQL.

It also crops up in WMS, on the SF transactions too.

 

[bruggles]

The module used by our Materials Manager that we find keeps things open after it is closed and causes a record lock is IM\Maintain\Item Master. As stated many times we need to have him log completely out of Macola and then it releases the record lock.

TIA

 

[jdblank]

I'm not a sql server guy, so I don't know if this is standard setup, but our locks are located in msllockdb.dbo.MACLOCKS. Do 'select * from msllockdb.dbo.MACLOCKS'; find the locked record and delete it from that table. it beats logging in and out. If you don't have that table, those locks should be stored somewhere so you can delete them - of course I would use caution when deleting from tables.

 

[dgillz]

Brent,

What is the module you are talking about? What menu options is he/she taking to open this "module"?

Is this a Macola menu option, or an application that someone developed?

Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports

http://www.gainfocus.biz

"If you have a big enough dictionary, just about everything is a word"
--Dave Barry

 

[JayTheGeek]

We are on Macola, not Progression. But we are SQL 2000 and do encounter these record locks in Inventory Mangement.

The feedback from jdblank is the official advice. It is documented on Exact's web site and that is the advice that my Reseller passed along. I am a SQL guy, and my understanding is that record locks are there for a reason; to protect data integrity. I just don't like the idea of deleting these records.

That said, it does sound like you have something fishy in your IM module. Is it the standard code, or are there modifications? I can't offer much help with your IM Module if it is getting hung while exiting. But I can offer help with the SQL side.

I do two things to manage record locks in my environment:

First I have a view set up on the MSLLockDB table:

SELECT TOP 100 PERCENT *
FROM dbo.MacLocks
ORDER BY SessionID, DBName, TableName, RowID

This just sorts the table into a clean look. I will usually size this into the right 1/3 of the Enterprize Manager screen.

Next in Enterprize manager open; Management, Current Activity, Process Info.

You should be able to relate a record lock's 'SessionID' to Current Activity's 'Process ID'. The MacLocks table will give you some information on the database table and row that is locked. Linking that info to the process will give you the username.

Keep in mind both of these windows will require a refresh when you encounter an issue. Rerun the query on the MacLocks table. Right Click on "Current Activity" and select refresh.

By using this method I am able to contact users and modify user habits (not leaving data entry screens open for a prolonged period) and have users exit screens or log off to clear record locks. This works 95% of the time to resolve record lock issues.

Another note here. We use Macola in a terminal server environment. When a session encouters the 'record lock in way' message, it can consume 25% of the server CPU until it is resolved. Left unresolved I often see a cascade affect; a second and third session locked. I can quickly have 75% CPU tied up in record locks. So training users and responding quickly to these issues is important.

 

[dgillz]

Jay,

Exact has 2 Macola products, Progression and ES. Which one are you using?

Other than that detail, great post.

Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports

http://www.gainfocus.biz

"If you have a big enough dictionary, just about everything is a word"
--Dave Barry

 

[JayTheGeek]

Oops,

Macola ES Release 360 v4.0.0.323