Novell Locking Files

[CLR]

I have a Novell 4.11 server that has a DOS Clipper database running on it. I have 3 remote sites linking through frame relay or fiber connections. Users will occationally lock the database when they should be in sharing mode. They will get a lock error (telling me what process is locked out) from within the clipper program - they can then hit esc to get out of the error and then they will go on.

Other times users will lock into a critical rights file and continue to work fine- while others can't access their rights and get continous lock errors until the the user locking files are cleared. It appears this type of locking may be related to the PC running low on resources.

Has anyone else had these issues or have any suggestions on how to stop this?

Cindy Reed
cinthia_reed@ohiogascompany.com

 

[TheLad]

Stupid question - are the files on the server flagged as shareable?

 

[CLR]

Yes - they are...

 

[TheLad]

Are your users accessing this DOS database via DOS or is it via a DOS session in Win95/98/NT/2000?

If Windows, try increasing the swap file size. Although Microsoft recommends the size of the physical memory + 11mb, this (in my opinion) sometimes appears to be insufficient.

 

[CLR]

I'm accessing the DOS database via Windows 95 DOS session.

I did some error tracking and have found that almost every instance of the "locking" error is when two or more users are trying to access Service Order program at the same time. And then, 90% of the errors occur when users over our WAN (frame relay) is one working in S/O system. If two users are trying to work in S/O at the same time they can take several minutes to complete over the WAN connection. (If only one person is working in the S/O system it takes about 35 seconds to complete a S/O over the WAN.)The remote locations rarely get errors. They grab files and lock the local site out. The users working on the local server get the errors.

The programmer who wrote the Clipper program has told me that he has no other sites using this product over a WAN or frame relay connection. So I think I'm at the heart of the issue, but the only resolution I have is with in a year we should be able to connect through a fiber line that will be run to these locations... Any ideas/suggestions?!@#?

 

[rjs]

I used to do a fair amount of Clipper programming, so I have a few ideas which may or may not help.

First, Clipper programs often create temporary working files ($something). If these are being created at all and they are being created on the server, instead of the PCs local hard drive, this could cause performance issues over a WAN. I think, but can't remember, there were DOS environment variables that could control the location of these temp files. Hopefully your programmer knows.

Two, I seem to remember that certain Clipper libraries for NetWare required DOS share to be run at the workstation. If the programs are using old 3rd party NetWare libraries, updating and recompiling might help.

Finally, this may be impracticle, but you could look at the traffic on your routers to see if that provides any more insite into the delays.