Solved cobol under novell netware 6.5, windows 7 file lock

April 9, 2012 at 02:21:38
Specs: novell netware 6.5 OS file server, intel core 3.30ghz Ram 2.00gb
Novel netware 6.5
Client 2 sp2
cobol acucorp extend9 software
IE 9
Windows 7

See More: cobol under novell netware 6.5, windows 7 file lock

Report •


✔ Best Answer
April 11, 2012 at 05:47:58
Seems to be more likely an issue between Windows 7 and Cobol and has nothing todo with Novell Netware.
I suggest to contact the manufactorer of Cobol on this problem.



#1
April 9, 2012 at 07:54:51
What is your exact problem?
What error message did you get?

Report •

#2
April 9, 2012 at 08:21:53
Hi thank you, We are getting error code 99 "file locked by another users" when accessing the same file as read only while it was open as an input only.

Report •

#3
April 9, 2012 at 10:31:55
Check the following settings at the netware server console:
SET LEVEL 2 OPLOCKS ENABLED
SET CLIENT FILE CACHING ENABLED
(This settings can be made in STARTUP.NCF so that its also set on server restart)

You may want to try setting
SET LEVEL 2 OPLOCKS ENABLE=ON
and
SET CLIENT FILE CACHING ENABLED=ON

In this case, client locks the file it intends to use, downloads the whole file to the workstation memory where the application works on it, but permits other clients, to access the same file in read only mode. When work is done by client 1, it writes back the files onto the server and clears the lock of the file.

On client computer, you have to make sure, that FILE CACHING is set to OFF.
This only disables Level 1 OpLocks, which works as described above, but do not grant read only rights for other clients. Level 2 OpLocks is always switched on and can not switched off and is absolutely set, to what you need.

You will find FILE CACHING in the settings of the Novell Client by rightclicking the red N in the systray, choose Novell Client Properties, Advanced Settings, File Caching.

Keep us posted.


Report •

Related Solutions

#4
April 10, 2012 at 02:44:58
Thank you again, actually we have already tested all these setting even in different combination like of the following:
Sever :
Set of OpLock on/off
Clients :
File Caching on/off
File Commit on/off
SMB on/off
SMB1 on/off
SMB2 on/off
Compatabilities :
Windows Server 2008 (Service Pack 1)
Windows Vista
Windows Vista (Service Pack 1)
Windows Vista (Service Pack 2)
Windows 7

That testing took us 384 setting combinations but still its end up with the same result (error code 99).


With my best regards,


Report •

#5
April 10, 2012 at 09:13:53
As far as I could figure out, error code 99 means "Record locked by another user".
Record locking is quite ok and it's a must.
http://www.cse.ohio-state.edu/~sgom...

Have you also tried to set "File commit" to on in the Novell Client Settings?


Report •

#6
April 10, 2012 at 09:47:13
It is depend on a program, our program are reading a record with no lock. Even though the instruction was not to lock the record, the client who got the first reading of the record lock the whole file instead.

following are the instruction inside the program:

Form1-Pb-1-Ex-Cmd-Clicked.
|DISPLAY MESSAGE BOX CHRTMAST-FILE
OPEN Input CHRTMAST
IF CHRTMAST-SW > '00'
DISPLAY MESSAGE BOX "OPENING CHRTMAST-SW: " CHRTMAST-SW
END-IF

MOVE LOW-VALUE TO CHRTMAST-ACNO
START CHRTMAST KEY IS NOT < CHRTMAST-ACNO
INVALID KEY
CLOSE CHRTMAST
EXIT PARAGRAPH
END-START
PERFORM READ-CHRTMAST-NOW
CLOSE CHRTMAST
.
READ-CHRTMAST-NOW.
READ CHRTMAST NEXT RECORD WITH NO LOCK
AT END
EXIT PARAGRAPH
END-READ
IF CHRTMAST-SW > '00'
DISPLAY MESSAGE BOX "READING CHRTMAST"
H"0A" "CHRTMAST-SW: " CHRTMAST-SW
END-IF
MODIFY FORM1-EF-1 VALUE CHRTMAST-ACNO

GO TO READ-CHRTMAST-NOW .

With my best regards


Report •

#7
April 10, 2012 at 15:17:49
If the program itself locks the whole file, there are no settings at the server, to circumvent file locking.
This brings me to the question:
Were you ever able to use this program on several clients at the same time?
If so, what kind of server operating system was used on that server, or was there installed any additional software or module installed, to make it running, as desired?

Report •

#8
April 10, 2012 at 23:47:47
We have been using AcuCobol since year 2000 and we developed varieties of application that are multi-users. We never had any problem concerning file handling even though we have a lot of users connecting to our server.

All our application softwares are all running very well under the following environment:
AcuCobol Extend 8.1
Novell Netware 6.5
Client 2 SP2
Windows XP
IE 8
File Chaching = of
File Commint = on

Our problem started only when we used Windows 7 and I.E 8. But luckily because Windows 95 compatabilities are still on the selection our application work at it is.

Currently we are still running smoothly under the following set up:
AcuCobol Extend 9.0
Novell netware 6.5
Client 2 SP2
Windows 7
I.E 8
Compatabilities = Windows 95
File caching = off
File commit = on

But since there was no more Windows 95 compatablility in the release of AcuCobol Extend9.1 our problem started there.

With my best regards,


Report •

#9
April 11, 2012 at 05:47:58
✔ Best Answer
Seems to be more likely an issue between Windows 7 and Cobol and has nothing todo with Novell Netware.
I suggest to contact the manufactorer of Cobol on this problem.


Report •

#10
April 11, 2012 at 06:42:03
thank you very much, for the concerned. I will appreciate wholeheartedly any solution you might suggest us to do and I will keep visiting this forum not only to get help but to give solution also to other.

With my best regards


Report •

#11
April 11, 2012 at 06:47:59
You are welcome.

Report •

#12
January 11, 2013 at 08:29:54
Were you by any chance able to solve this problem by contacting Microfocus? We are having similar problems with the 9.1.1 runtime and are wondering if you had any luck.

Report •


Ask Question