Hi!
One of my customer is using Fileshare under Windows 7 and Windows 2012 Server and have big Problems with the fileshare System..
Under Windows XP and Windows 2003 there where no Speed Problems...
The Compiler Directives that he is using was:
FILESHARE CALLFH "EXTFH"
In the cobopt.cfg is standing:
set environment_mapper=TRUE
Have anyone a hint for me to bring up the Speed for the programs?
Here an select Cobol sample:
SELECT TITEL
ASSIGN external TITELX
ACCESS DYNAMIC
RECORD KEY TI00
ALTERNATE RECORD KEY ti900 duplicates
ORGANIZATION INDEXED
LOCK MODE MANUAL
FILE STATUS STTITEL.
...
And the FD:
FD TITEL
DATA RECORD RTITEL.
*
01 RTITEL.
02 TI00.
* * MASTER KEY
05 TI000 PIC 999.
I hope anyone can help me and my customer!?
Best Regards
Bernd
It will be difficult to provide any assistance without at least basic information. What product is the customer using? What is the Fileshare / FHREDIR configuration?
It would be best to open a Support Incident to track the issue.
Hi!
One of my customer is using Fileshare under Windows 7 and Windows 2012 Server and have big Problems with the fileshare System..
Under Windows XP and Windows 2003 there where no Speed Problems...
The Compiler Directives that he is using was:
FILESHARE CALLFH "EXTFH"
In the cobopt.cfg is standing:
set environment_mapper=TRUE
Have anyone a hint for me to bring up the Speed for the programs?
Here an select Cobol sample:
SELECT TITEL
ASSIGN external TITELX
ACCESS DYNAMIC
RECORD KEY TI00
ALTERNATE RECORD KEY ti900 duplicates
ORGANIZATION INDEXED
LOCK MODE MANUAL
FILE STATUS STTITEL.
...
And the FD:
FD TITEL
DATA RECORD RTITEL.
*
01 RTITEL.
02 TI00.
* * MASTER KEY
05 TI000 PIC 999.
I hope anyone can help me and my customer!?
Best Regards
Bernd
I will note that, for Fileshare on Windows, the two simplest ways to improve performance are to:
1. Configure the Fileshare server for synchronous communications mode (using the /sc switch in the Fileshare server configuration file). See the topic "Fileshare Server Configuration Options" in the product documentation.
2. Since this is Windows, if the client and server are running on the same machine, configure the server and client to use CCISM (Shared Memory). Again, refer to the documentation for configuring Fileshare.
Hi!
One of my customer is using Fileshare under Windows 7 and Windows 2012 Server and have big Problems with the fileshare System..
Under Windows XP and Windows 2003 there where no Speed Problems...
The Compiler Directives that he is using was:
FILESHARE CALLFH "EXTFH"
In the cobopt.cfg is standing:
set environment_mapper=TRUE
Have anyone a hint for me to bring up the Speed for the programs?
Here an select Cobol sample:
SELECT TITEL
ASSIGN external TITELX
ACCESS DYNAMIC
RECORD KEY TI00
ALTERNATE RECORD KEY ti900 duplicates
ORGANIZATION INDEXED
LOCK MODE MANUAL
FILE STATUS STTITEL.
...
And the FD:
FD TITEL
DATA RECORD RTITEL.
*
01 RTITEL.
02 TI00.
* * MASTER KEY
05 TI000 PIC 999.
I hope anyone can help me and my customer!?
Best Regards
Bernd
I can send you the "cobopt.cfg" and the "MFEXTMAP.DAT"...
COBOPT:
set environment_mapper=TRUE
MFEXTMAP:
...
ankox K:\\TestK\\Data\\anko.dat
...
Hi!
One of my customer is using Fileshare under Windows 7 and Windows 2012 Server and have big Problems with the fileshare System..
Under Windows XP and Windows 2003 there where no Speed Problems...
The Compiler Directives that he is using was:
FILESHARE CALLFH "EXTFH"
In the cobopt.cfg is standing:
set environment_mapper=TRUE
Have anyone a hint for me to bring up the Speed for the programs?
Here an select Cobol sample:
SELECT TITEL
ASSIGN external TITELX
ACCESS DYNAMIC
RECORD KEY TI00
ALTERNATE RECORD KEY ti900 duplicates
ORGANIZATION INDEXED
LOCK MODE MANUAL
FILE STATUS STTITEL.
...
And the FD:
FD TITEL
DATA RECORD RTITEL.
*
01 RTITEL.
02 TI00.
* * MASTER KEY
05 TI000 PIC 999.
I hope anyone can help me and my customer!?
Best Regards
Bernd
Hi Bernd,
I think that you have your terminologies confused here. Fileshare is a server based version of the file handler which runs as a separate process on a network server machine. Your program running on a client machine will redirect its file I-O across the network to the fileshare server where the I-O will actually be done.
This is turned on with the directive CALLFH"FHREDIR".
You are specifying CALLFH"EXTFH" which is the default to use the local file handler. The FILESHARE directive that you are using has nothing to do with the fileshare server technology to which Michael is referring but instead simply causes the file handler to treat the files as though AUTOMATIC locking was turned on.
So you are running the program locally and trying to share files on a network drive. The normal cause of performance problems in this environment is caused by the opportunistic locking done by Windows between a client OS and a Server OS.
There is an article from a 3rd party vendor here which although doesn't reference COBOL specifically does explain the problem. If you must share files on a network drive then you should turn off the local caching and oplocks.
In this situation it is often recommended that you do use the Fileshare technology mentioned above to avoid this problem altogether.
Thanks
