Skip to main content

Hello,

I'm developing in an application installed in a Windows 2003 server. The users connect to the application with mapped drives from their Windows pc's. The trouble occurs when two or more users access simultaneously to the same vision file. The first one, can runs the whole file in about 2 seconds, but the second one runs the file in about 1 minute.

I'm using 8.1.3.1 version and executing cobol programs with wrun32.exe

The mapped drive seems to work fine, i can open the folder, copy files and open them with no retard.


How can I solve this?


#extend
#Windows
#COBOL

Hello,

I'm developing in an application installed in a Windows 2003 server. The users connect to the application with mapped drives from their Windows pc's. The trouble occurs when two or more users access simultaneously to the same vision file. The first one, can runs the whole file in about 2 seconds, but the second one runs the file in about 1 minute.

I'm using 8.1.3.1 version and executing cobol programs with wrun32.exe

The mapped drive seems to work fine, i can open the folder, copy files and open them with no retard.


How can I solve this?


#extend
#Windows
#COBOL

Couple of suggestions for testing:

1)  Install AcuServer and test.

2)  You didn't mention your open method but I would suggest testing with the file open input.


Hello,

I'm developing in an application installed in a Windows 2003 server. The users connect to the application with mapped drives from their Windows pc's. The trouble occurs when two or more users access simultaneously to the same vision file. The first one, can runs the whole file in about 2 seconds, but the second one runs the file in about 1 minute.

I'm using 8.1.3.1 version and executing cobol programs with wrun32.exe

The mapped drive seems to work fine, i can open the folder, copy files and open them with no retard.


How can I solve this?


#extend
#Windows
#COBOL

Hi,

First lot of thanks for the answers.

- We open files with I-O, due to that users have to make modifications on the file

- Opportunistic lock is desactivated in our installations on the server machine.

- Talking about acuserver, I'm asking if my company will have to buy a special license or just with the wrun32 license we have right to use acuserver.

Thanks again!


Hello,

I'm developing in an application installed in a Windows 2003 server. The users connect to the application with mapped drives from their Windows pc's. The trouble occurs when two or more users access simultaneously to the same vision file. The first one, can runs the whole file in about 2 seconds, but the second one runs the file in about 1 minute.

I'm using 8.1.3.1 version and executing cobol programs with wrun32.exe

The mapped drive seems to work fine, i can open the folder, copy files and open them with no retard.


How can I solve this?


#extend
#Windows
#COBOL

If you are not already using these two Runtime configuration settings then you should test them out:

NT_OPP_LOCK_STATUS FAST

V_LOCK_METHOD 1


Hello,

I'm developing in an application installed in a Windows 2003 server. The users connect to the application with mapped drives from their Windows pc's. The trouble occurs when two or more users access simultaneously to the same vision file. The first one, can runs the whole file in about 2 seconds, but the second one runs the file in about 1 minute.

I'm using 8.1.3.1 version and executing cobol programs with wrun32.exe

The mapped drive seems to work fine, i can open the folder, copy files and open them with no retard.


How can I solve this?


#extend
#Windows
#COBOL

You have to purchase a separate license for AcuServer. I have used AcuServer for years and its a great product and certainly addresses performance issues. I suggest you try out a demo license. Its easy to setup and test.


Hello,

I'm developing in an application installed in a Windows 2003 server. The users connect to the application with mapped drives from their Windows pc's. The trouble occurs when two or more users access simultaneously to the same vision file. The first one, can runs the whole file in about 2 seconds, but the second one runs the file in about 1 minute.

I'm using 8.1.3.1 version and executing cobol programs with wrun32.exe

The mapped drive seems to work fine, i can open the folder, copy files and open them with no retard.


How can I solve this?


#extend
#Windows
#COBOL

I've tested these configuration settings but they do not work. The slow speed is kept when a second user access to an open file (no matter if it is open for INPUT, I-O, or with any kind of locking)

We would like to test acuserver, but to my company it would be too expensive, due to we have lot of small customers that can't afford to buy that license, so we would have to buy these licenses for every one of them.


Hello,

I'm developing in an application installed in a Windows 2003 server. The users connect to the application with mapped drives from their Windows pc's. The trouble occurs when two or more users access simultaneously to the same vision file. The first one, can runs the whole file in about 2 seconds, but the second one runs the file in about 1 minute.

I'm using 8.1.3.1 version and executing cobol programs with wrun32.exe

The mapped drive seems to work fine, i can open the folder, copy files and open them with no retard.


How can I solve this?


#extend
#Windows
#COBOL

Now I tested with 'I$IO' routine, but the results are the same.


Hello,

I'm developing in an application installed in a Windows 2003 server. The users connect to the application with mapped drives from their Windows pc's. The trouble occurs when two or more users access simultaneously to the same vision file. The first one, can runs the whole file in about 2 seconds, but the second one runs the file in about 1 minute.

I'm using 8.1.3.1 version and executing cobol programs with wrun32.exe

The mapped drive seems to work fine, i can open the folder, copy files and open them with no retard.


How can I solve this?


#extend
#Windows
#COBOL

Just to be clear, the settings described previously for opportunistic locking, etc. need to be applied on the client machines that are running the programs and accessing the data - not on the server itself.

Your testing results with I$IO are not surprising, as it is just another programming method to access the runtime's Vision file handler. The actual file handler is exactly the same as the one used with standard COBOL I-O syntax.

The Windows networking protocol (SMB) was designed and optimized for things like browsing files, and opening/saving documents (Word, Excel, etc.). It was not designed for multi-user concurrent file access.  That is exactly what AcuServer was designed for.

Other options you might explore would be running the programs directly on the server, and have the client PCs connect to the server using either the Acu Thin Client, Windows Terminal Services, or Citrix.


Hello,

I'm developing in an application installed in a Windows 2003 server. The users connect to the application with mapped drives from their Windows pc's. The trouble occurs when two or more users access simultaneously to the same vision file. The first one, can runs the whole file in about 2 seconds, but the second one runs the file in about 1 minute.

I'm using 8.1.3.1 version and executing cobol programs with wrun32.exe

The mapped drive seems to work fine, i can open the folder, copy files and open them with no retard.


How can I solve this?


#extend
#Windows
#COBOL

hI!

can post WINVERS.DEF". i dont have library


Hello,

I'm developing in an application installed in a Windows 2003 server. The users connect to the application with mapped drives from their Windows pc's. The trouble occurs when two or more users access simultaneously to the same vision file. The first one, can runs the whole file in about 2 seconds, but the second one runs the file in about 1 minute.

I'm using 8.1.3.1 version and executing cobol programs with wrun32.exe

The mapped drive seems to work fine, i can open the folder, copy files and open them with no retard.


How can I solve this?


#extend
#Windows
#COBOL

what version are you working with and on which O/S ... the def files we provide are in the standard install AcuGT\\sample\\def directory.