[Migrated content. Thread originally posted on 20 November 2002]

Unfortunately, the article referred to is not useful in Acuserver scenarios as it will only tell you the same, that is, Acuserver is locking the files.
If one were using files directly, e.g. via mapped drives accessing the vision files, the article software will provide you with the answers.

Here's another challenge:

Most of our customers are running on SCO platform. Since there is more and more need voor graphical (GUI) solutions, more and more development is done using AcuCobol GT (5.x).

For the new (GUI) modules we use AcuServer on the SCO system for the SCO based customers and normal Windows network functionality for customers on Microsoft/NT platforms.

Some of the models require a lot of realtime record-io (with locking), and in larger organisations, people sometimes forget to sign out when having a lunch break etc. This mean other wil get a record-lock every now and then. To prevent them from running around all offices to see what's going on, our declaratives include a message system telling them who (and where) has locked the record.

Now the questions:

With AcuServer we can no longer tell who is locking the record. We can see who is using what file, but not who is locking whick record. That is, we can see that acuserver but thats all.

On a windows network, there doesn't seem to be a way to determin who is lockin what..

Any suggestions?

---

[Migrated content. Thread originally posted on 20 November 2002]

Unfortunately, the article referred to is not useful in Acuserver scenarios as it will only tell you the same, that is, Acuserver is locking the files.
If one were using files directly, e.g. via mapped drives accessing the vision files, the article software will provide you with the answers.

Here's another challenge:

Most of our customers are running on SCO platform. Since there is more and more need voor graphical (GUI) solutions, more and more development is done using AcuCobol GT (5.x).

For the new (GUI) modules we use AcuServer on the SCO system for the SCO based customers and normal Windows network functionality for customers on Microsoft/NT platforms.

Some of the models require a lot of realtime record-io (with locking), and in larger organisations, people sometimes forget to sign out when having a lunch break etc. This mean other wil get a record-lock every now and then. To prevent them from running around all offices to see what's going on, our declaratives include a message system telling them who (and where) has locked the record.

Now the questions:

With AcuServer we can no longer tell who is locking the record. We can see who is using what file, but not who is locking whick record. That is, we can see that acuserver but thats all.

On a windows network, there doesn't seem to be a way to determin who is lockin what..

Any suggestions?

---

[Migrated content. Thread originally posted on 20 November 2002]

Unfortunately, the article referred to is not useful in Acuserver scenarios as it will only tell you the same, that is, Acuserver is locking the files.
If one were using files directly, e.g. via mapped drives accessing the vision files, the article software will provide you with the answers.

Hello FSS

Unfortunately I haven't got any help for you.

In win2000 and with acuserver we have the same problem. I am looking forward to find out if there is any solutions for us.

Regards

Steen

---

[Migrated content. Thread originally posted on 20 November 2002]

Unfortunately, the article referred to is not useful in Acuserver scenarios as it will only tell you the same, that is, Acuserver is locking the files.
If one were using files directly, e.g. via mapped drives accessing the vision files, the article software will provide you with the answers.

Hi Everyone,

You can also read that newsletter online at:
http://www.acucorp.com/company/newsletter/

Thanks,
Jay

---