[Migrated content. Thread originally posted on 25 June 2003]
In a citrix environment with 3 citrix-servers (80 users) and 2 windows-2000(sp3) dataservers(master and slave) without acuserve, we have the following problem: cobol file-status 39,01 ; mismatch found but exact cause unknown.
Until now this file-status happens only when users start an application. This file-status happens about 1 to 10 times a day. Users restart the program and no file-status occurs.
I there somebody who has a solution for our problem?
greetings Ties van Valen, Leeuwarden, The Netherlands
[Migrated content. Thread originally posted on 25 June 2003]
In a citrix environment with 3 citrix-servers (80 users) and 2 windows-2000(sp3) dataservers(master and slave) without acuserve, we have the following problem: cobol file-status 39,01 ; mismatch found but exact cause unknown.
Until now this file-status happens only when users start an application. This file-status happens about 1 to 10 times a day. Users restart the program and no file-status occurs.
I there somebody who has a solution for our problem?
greetings Ties van Valen, Leeuwarden, The Netherlands
If you have a chance to experiment with it, try using unc naming rather than disk drives, e.g.: \\\\myserver\\mydirectory\\myfile instead of for instance c:\\mydirectory\\myfile.
I know this has been a successful change elsewhere.
[Migrated content. Thread originally posted on 25 June 2003]
In a citrix environment with 3 citrix-servers (80 users) and 2 windows-2000(sp3) dataservers(master and slave) without acuserve, we have the following problem: cobol file-status 39,01 ; mismatch found but exact cause unknown.
Until now this file-status happens only when users start an application. This file-status happens about 1 to 10 times a day. Users restart the program and no file-status occurs.
I there somebody who has a solution for our problem?
greetings Ties van Valen, Leeuwarden, The Netherlands
If you have a chance to experiment with it, try using unc naming rather than disk drives, e.g.: \\\\myserver\\mydirectory\\myfile instead of for instance c:\\mydirectory\\myfile.
I know this has been a successful change elsewhere.
[Migrated content. Thread originally posted on 25 June 2003]
In a citrix environment with 3 citrix-servers (80 users) and 2 windows-2000(sp3) dataservers(master and slave) without acuserve, we have the following problem: cobol file-status 39,01 ; mismatch found but exact cause unknown.
Until now this file-status happens only when users start an application. This file-status happens about 1 to 10 times a day. Users restart the program and no file-status occurs.
I there somebody who has a solution for our problem?
greetings Ties van Valen, Leeuwarden, The Netherlands
If you have a chance to experiment with it, try using unc naming rather than disk drives, e.g.: \\\\myserver\\mydirectory\\myfile instead of for instance c:\\mydirectory\\myfile.
I know this has been a successful change elsewhere.
[Migrated content. Thread originally posted on 25 June 2003]
In a citrix environment with 3 citrix-servers (80 users) and 2 windows-2000(sp3) dataservers(master and slave) without acuserve, we have the following problem: cobol file-status 39,01 ; mismatch found but exact cause unknown.
Until now this file-status happens only when users start an application. This file-status happens about 1 to 10 times a day. Users restart the program and no file-status occurs.
I there somebody who has a solution for our problem?
greetings Ties van Valen, Leeuwarden, The Netherlands
Thank you Gisle, we will try your solution and let you know the results
[Migrated content. Thread originally posted on 25 June 2003]
In a citrix environment with 3 citrix-servers (80 users) and 2 windows-2000(sp3) dataservers(master and slave) without acuserve, we have the following problem: cobol file-status 39,01 ; mismatch found but exact cause unknown.
Until now this file-status happens only when users start an application. This file-status happens about 1 to 10 times a day. Users restart the program and no file-status occurs.
I there somebody who has a solution for our problem?
greetings Ties van Valen, Leeuwarden, The Netherlands
Using unc naming works, but now something else goes wrong.
After using unc naming, the direct printing to LPT1 in the cobol application under citrix does not work anymore.
[Migrated content. Thread originally posted on 25 June 2003]
In a citrix environment with 3 citrix-servers (80 users) and 2 windows-2000(sp3) dataservers(master and slave) without acuserve, we have the following problem: cobol file-status 39,01 ; mismatch found but exact cause unknown.
Until now this file-status happens only when users start an application. This file-status happens about 1 to 10 times a day. Users restart the program and no file-status occurs.
I there somebody who has a solution for our problem?
greetings Ties van Valen, Leeuwarden, The Netherlands
Using unc naming works, but now something else goes wrong.
After using unc naming, the direct printing to LPT1 in the cobol application under citrix does not work anymore.
[Migrated content. Thread originally posted on 25 June 2003]
In a citrix environment with 3 citrix-servers (80 users) and 2 windows-2000(sp3) dataservers(master and slave) without acuserve, we have the following problem: cobol file-status 39,01 ; mismatch found but exact cause unknown.
Until now this file-status happens only when users start an application. This file-status happens about 1 to 10 times a day. Users restart the program and no file-status occurs.
I there somebody who has a solution for our problem?
greetings Ties van Valen, Leeuwarden, The Netherlands
Using unc naming works, but now something else goes wrong.
After using unc naming, the direct printing to LPT1 in the cobol application under citrix does not work anymore.
[Migrated content. Thread originally posted on 25 June 2003]
In a citrix environment with 3 citrix-servers (80 users) and 2 windows-2000(sp3) dataservers(master and slave) without acuserve, we have the following problem: cobol file-status 39,01 ; mismatch found but exact cause unknown.
Until now this file-status happens only when users start an application. This file-status happens about 1 to 10 times a day. Users restart the program and no file-status occurs.
I there somebody who has a solution for our problem?
greetings Ties van Valen, Leeuwarden, The Netherlands
Which version are you using? There used to be an issue with printing and unc, but that was addressed.
However, you don't get 3901 on LPT1, do you? Keep using LPT1 and only use unc for filenames.
[Migrated content. Thread originally posted on 25 June 2003]
In a citrix environment with 3 citrix-servers (80 users) and 2 windows-2000(sp3) dataservers(master and slave) without acuserve, we have the following problem: cobol file-status 39,01 ; mismatch found but exact cause unknown.
Until now this file-status happens only when users start an application. This file-status happens about 1 to 10 times a day. Users restart the program and no file-status occurs.
I there somebody who has a solution for our problem?
greetings Ties van Valen, Leeuwarden, The Netherlands
Which version are you using? There used to be an issue with printing and unc, but that was addressed.
However, you don't get 3901 on LPT1, do you? Keep using LPT1 and only use unc for filenames.
[Migrated content. Thread originally posted on 25 June 2003]
In a citrix environment with 3 citrix-servers (80 users) and 2 windows-2000(sp3) dataservers(master and slave) without acuserve, we have the following problem: cobol file-status 39,01 ; mismatch found but exact cause unknown.
Until now this file-status happens only when users start an application. This file-status happens about 1 to 10 times a day. Users restart the program and no file-status occurs.
I there somebody who has a solution for our problem?
greetings Ties van Valen, Leeuwarden, The Netherlands
Which version are you using? There used to be an issue with printing and unc, but that was addressed.
However, you don't get 3901 on LPT1, do you? Keep using LPT1 and only use unc for filenames.
[Migrated content. Thread originally posted on 25 June 2003]
In a citrix environment with 3 citrix-servers (80 users) and 2 windows-2000(sp3) dataservers(master and slave) without acuserve, we have the following problem: cobol file-status 39,01 ; mismatch found but exact cause unknown.
Until now this file-status happens only when users start an application. This file-status happens about 1 to 10 times a day. Users restart the program and no file-status occurs.
I there somebody who has a solution for our problem?
greetings Ties van Valen, Leeuwarden, The Netherlands
Unc naming was not the answer to our problem.
We heard from another developer with Citrix experience that AcuServe could be the solution (He had the same experience).
We now installed AcuServe and since we installed AcuServe, status 39,01 has not occured anymore!
Why did Acucorp not advice AcuServe to us?
