Highlighted
Absent Member.
Absent Member.
1441 views

[archive] filestatus 39,01 in a Citrix environment

[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
0 Likes
5 Replies
Highlighted
Absent Member.
Absent Member.

RE: [archive] filestatus 39,01 in a Citrix environment

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.
0 Likes
Highlighted
Absent Member.
Absent Member.

RE: [archive] filestatus 39,01 in a Citrix environment

Thank you Gisle, we will try your solution and let you know the results
0 Likes
Highlighted
Absent Member.
Absent Member.

RE: [archive] filestatus 39,01 in a Citrix environment

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.
0 Likes
Highlighted
Absent Member.
Absent Member.

RE: [archive] filestatus 39,01 in a Citrix environment

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.
0 Likes
Highlighted
Absent Member.
Absent Member.

RE: [archive] filestatus 39,01 in a Citrix environment

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?
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.