File Error 93 on Vision Files

We have one client location that is having infrequent File Error 93 issues. The error has happened with two different files. Both are Vision files. They are running a small network of Windows 10 and Windows 7 computers. The files are hosted on a Windows 10 computer. They are using the extend 9.2.2 ECN-4266 runtime. The errors occur when they get busy/active. However, it doesn't always happen when they are busy. I've included the SELECT and FD for both files. One has a variable length record. The other is "normal". They are opening, reading from, writing to, and closing other files (Vision, binary, and line sequential) on the same network drive share.

**********************************

SELECT PAX-SIG-FL ASSIGN TO RANDOM "PAXSIGFL"
WITH COMPRESSION
ORGANIZATION IS INDEXED
ACCESS MODE IS DYNAMIC
RECORD KEY IS PAX-SIG-KEY.

FD PAX-SIG-FL.
01 PAX-SIG-REC.
02 PAX-SIG-KEY.
03 PAX-SIG-TRAN-NO PIC x(7).
03 PAX-SIG-TRANS-DATE pic 9(6).
03 PAX-SIG-NUM pic 9.
02 SIG-BYTES pic 9(5).
02 PAX-sig-jpg-array.
03 SIG-jpg-byte pic xx occurs 0 TO 12000 TIMES
DEPENDING ON SIG-BYTES.

**********************************

SELECT pax-vision-A ASSIGN TO RANDOM "PVDAA"
WITH COMPRESSION
ORGANIZATION IS INDEXED
ACCESS MODE IS DYNAMIC
RECORD KEY IS UNIQUE-KEY-A.

FD pax-vission-A.
01 pax-vission-rec-A.
02 Unique-KEY-A.
03 Unique-KEY-date-A pic 9(8).
03 Unique-KEY-time-A pic 9(6).
03 Unique-KEY-cntr-A pic 9.
03 Unique-KEY-reg-no-A pic xx.
02 filler pic x.
02 pax-compile-line pic x(20).
02 raw-ilogPax-data-A pic x(1000).

**********************************

We are adding a declarative to the files so we can do a sleep loop to retry accessing the files and also log when these occur. Any suggestions on things we should look for and/or include in our log?

Have you ruled out the possibility that one of their programs is opening a file with lock and this causes the 93 file status only when there is significant file activity? If the exclusive locker is in and out of the file quickly enough another process may never encounter it unless the system is under stress.

The structure of the Vision files themselves is most likely not a factor.

We have one client location that is having infrequent File Error 93 issues. The error has happened with two different files. Both are Vision files. They are running a small network of Windows 10 and Windows 7 computers. The files are hosted on a Windows 10 computer. They are using the extend 9.2.2 ECN-4266 runtime. The errors occur when they get busy/active. However, it doesn't always happen when they are busy. I've included the SELECT and FD for both files. One has a variable length record. The other is "normal". They are opening, reading from, writing to, and closing other files (Vision, binary, and line sequential) on the same network drive share.

**********************************

SELECT PAX-SIG-FL ASSIGN TO RANDOM "PAXSIGFL"
WITH COMPRESSION
ORGANIZATION IS INDEXED
ACCESS MODE IS DYNAMIC
RECORD KEY IS PAX-SIG-KEY.

FD PAX-SIG-FL.
01 PAX-SIG-REC.
02 PAX-SIG-KEY.
03 PAX-SIG-TRAN-NO PIC x(7).
03 PAX-SIG-TRANS-DATE pic 9(6).
03 PAX-SIG-NUM pic 9.
02 SIG-BYTES pic 9(5).
02 PAX-sig-jpg-array.
03 SIG-jpg-byte pic xx occurs 0 TO 12000 TIMES
DEPENDING ON SIG-BYTES.

**********************************

SELECT pax-vision-A ASSIGN TO RANDOM "PVDAA"
WITH COMPRESSION
ORGANIZATION IS INDEXED
ACCESS MODE IS DYNAMIC
RECORD KEY IS UNIQUE-KEY-A.

FD pax-vission-A.
01 pax-vission-rec-A.
02 Unique-KEY-A.
03 Unique-KEY-date-A pic 9(8).
03 Unique-KEY-time-A pic 9(6).
03 Unique-KEY-cntr-A pic 9.
03 Unique-KEY-reg-no-A pic xx.
02 filler pic x.
02 pax-compile-line pic x(20).
02 raw-ilogPax-data-A pic x(1000).

**********************************

We are adding a declarative to the files so we can do a sleep loop to retry accessing the files and also log when these occur. Any suggestions on things we should look for and/or include in our log?

Have you ruled out the possibility that one of their programs is opening a file with lock and this causes the 93 file status only when there is significant file activity? If the exclusive locker is in and out of the file quickly enough another process may never encounter it unless the system is under stress.

The structure of the Vision files themselves is most likely not a factor.

We have one client location that is having infrequent File Error 93 issues. The error has happened with two different files. Both are Vision files. They are running a small network of Windows 10 and Windows 7 computers. The files are hosted on a Windows 10 computer. They are using the extend 9.2.2 ECN-4266 runtime. The errors occur when they get busy/active. However, it doesn't always happen when they are busy. I've included the SELECT and FD for both files. One has a variable length record. The other is "normal". They are opening, reading from, writing to, and closing other files (Vision, binary, and line sequential) on the same network drive share.

**********************************

SELECT PAX-SIG-FL ASSIGN TO RANDOM "PAXSIGFL"
WITH COMPRESSION
ORGANIZATION IS INDEXED
ACCESS MODE IS DYNAMIC
RECORD KEY IS PAX-SIG-KEY.

FD PAX-SIG-FL.
01 PAX-SIG-REC.
02 PAX-SIG-KEY.
03 PAX-SIG-TRAN-NO PIC x(7).
03 PAX-SIG-TRANS-DATE pic 9(6).
03 PAX-SIG-NUM pic 9.
02 SIG-BYTES pic 9(5).
02 PAX-sig-jpg-array.
03 SIG-jpg-byte pic xx occurs 0 TO 12000 TIMES
DEPENDING ON SIG-BYTES.

**********************************

SELECT pax-vision-A ASSIGN TO RANDOM "PVDAA"
WITH COMPRESSION
ORGANIZATION IS INDEXED
ACCESS MODE IS DYNAMIC
RECORD KEY IS UNIQUE-KEY-A.

FD pax-vission-A.
01 pax-vission-rec-A.
02 Unique-KEY-A.
03 Unique-KEY-date-A pic 9(8).
03 Unique-KEY-time-A pic 9(6).
03 Unique-KEY-cntr-A pic 9.
03 Unique-KEY-reg-no-A pic xx.
02 filler pic x.
02 pax-compile-line pic x(20).
02 raw-ilogPax-data-A pic x(1000).

**********************************

We are adding a declarative to the files so we can do a sleep loop to retry accessing the files and also log when these occur. Any suggestions on things we should look for and/or include in our log?

The program where the error always occurs does a simple "OPEN I-O" without locking, updates the record, then closes the file. The data file that this happens most often on is only referenced in one other program, and that program does an "OPEN INPUT" without locking the file, reads a record, then closes the file.

We have one client location that is having infrequent File Error 93 issues. The error has happened with two different files. Both are Vision files. They are running a small network of Windows 10 and Windows 7 computers. The files are hosted on a Windows 10 computer. They are using the extend 9.2.2 ECN-4266 runtime. The errors occur when they get busy/active. However, it doesn't always happen when they are busy. I've included the SELECT and FD for both files. One has a variable length record. The other is "normal". They are opening, reading from, writing to, and closing other files (Vision, binary, and line sequential) on the same network drive share.

**********************************

SELECT PAX-SIG-FL ASSIGN TO RANDOM "PAXSIGFL"
WITH COMPRESSION
ORGANIZATION IS INDEXED
ACCESS MODE IS DYNAMIC
RECORD KEY IS PAX-SIG-KEY.

FD PAX-SIG-FL.
01 PAX-SIG-REC.
02 PAX-SIG-KEY.
03 PAX-SIG-TRAN-NO PIC x(7).
03 PAX-SIG-TRANS-DATE pic 9(6).
03 PAX-SIG-NUM pic 9.
02 SIG-BYTES pic 9(5).
02 PAX-sig-jpg-array.
03 SIG-jpg-byte pic xx occurs 0 TO 12000 TIMES
DEPENDING ON SIG-BYTES.

**********************************

SELECT pax-vision-A ASSIGN TO RANDOM "PVDAA"
WITH COMPRESSION
ORGANIZATION IS INDEXED
ACCESS MODE IS DYNAMIC
RECORD KEY IS UNIQUE-KEY-A.

FD pax-vission-A.
01 pax-vission-rec-A.
02 Unique-KEY-A.
03 Unique-KEY-date-A pic 9(8).
03 Unique-KEY-time-A pic 9(6).
03 Unique-KEY-cntr-A pic 9.
03 Unique-KEY-reg-no-A pic xx.
02 filler pic x.
02 pax-compile-line pic x(20).
02 raw-ilogPax-data-A pic x(1000).

**********************************

We are adding a declarative to the files so we can do a sleep loop to retry accessing the files and also log when these occur. Any suggestions on things we should look for and/or include in our log?

The program where the error always occurs does a simple "OPEN I-O" without locking, updates the record, then closes the file. The data file that this happens most often on is only referenced in one other program, and that program does an "OPEN INPUT" without locking the file, reads a record, then closes the file.

We have one client location that is having infrequent File Error 93 issues. The error has happened with two different files. Both are Vision files. They are running a small network of Windows 10 and Windows 7 computers. The files are hosted on a Windows 10 computer. They are using the extend 9.2.2 ECN-4266 runtime. The errors occur when they get busy/active. However, it doesn't always happen when they are busy. I've included the SELECT and FD for both files. One has a variable length record. The other is "normal". They are opening, reading from, writing to, and closing other files (Vision, binary, and line sequential) on the same network drive share.

**********************************

SELECT PAX-SIG-FL ASSIGN TO RANDOM "PAXSIGFL"
WITH COMPRESSION
ORGANIZATION IS INDEXED
ACCESS MODE IS DYNAMIC
RECORD KEY IS PAX-SIG-KEY.

FD PAX-SIG-FL.
01 PAX-SIG-REC.
02 PAX-SIG-KEY.
03 PAX-SIG-TRAN-NO PIC x(7).
03 PAX-SIG-TRANS-DATE pic 9(6).
03 PAX-SIG-NUM pic 9.
02 SIG-BYTES pic 9(5).
02 PAX-sig-jpg-array.
03 SIG-jpg-byte pic xx occurs 0 TO 12000 TIMES
DEPENDING ON SIG-BYTES.

**********************************

SELECT pax-vision-A ASSIGN TO RANDOM "PVDAA"
WITH COMPRESSION
ORGANIZATION IS INDEXED
ACCESS MODE IS DYNAMIC
RECORD KEY IS UNIQUE-KEY-A.

FD pax-vission-A.
01 pax-vission-rec-A.
02 Unique-KEY-A.
03 Unique-KEY-date-A pic 9(8).
03 Unique-KEY-time-A pic 9(6).
03 Unique-KEY-cntr-A pic 9.
03 Unique-KEY-reg-no-A pic xx.
02 filler pic x.
02 pax-compile-line pic x(20).
02 raw-ilogPax-data-A pic x(1000).

**********************************

We are adding a declarative to the files so we can do a sleep loop to retry accessing the files and also log when these occur. Any suggestions on things we should look for and/or include in our log?

Tech support has experience with using Windows shares and Vision. You might check with them to see if this is anything they've seen before.

I don't know what you could log at the COBOL level to help determine the cause of this issue. If the OS is returning a spurious file locked condition then the runtime will not know the difference.

My best advice is to try to reproduce the problem with a couple of small programs that perform the same operations in order to force the issue. Once the issue can be reproduced it will be easier to examine and find the cause.

We have one client location that is having infrequent File Error 93 issues. The error has happened with two different files. Both are Vision files. They are running a small network of Windows 10 and Windows 7 computers. The files are hosted on a Windows 10 computer. They are using the extend 9.2.2 ECN-4266 runtime. The errors occur when they get busy/active. However, it doesn't always happen when they are busy. I've included the SELECT and FD for both files. One has a variable length record. The other is "normal". They are opening, reading from, writing to, and closing other files (Vision, binary, and line sequential) on the same network drive share.

**********************************

SELECT PAX-SIG-FL ASSIGN TO RANDOM "PAXSIGFL"
WITH COMPRESSION
ORGANIZATION IS INDEXED
ACCESS MODE IS DYNAMIC
RECORD KEY IS PAX-SIG-KEY.

FD PAX-SIG-FL.
01 PAX-SIG-REC.
02 PAX-SIG-KEY.
03 PAX-SIG-TRAN-NO PIC x(7).
03 PAX-SIG-TRANS-DATE pic 9(6).
03 PAX-SIG-NUM pic 9.
02 SIG-BYTES pic 9(5).
02 PAX-sig-jpg-array.
03 SIG-jpg-byte pic xx occurs 0 TO 12000 TIMES
DEPENDING ON SIG-BYTES.

**********************************

SELECT pax-vision-A ASSIGN TO RANDOM "PVDAA"
WITH COMPRESSION
ORGANIZATION IS INDEXED
ACCESS MODE IS DYNAMIC
RECORD KEY IS UNIQUE-KEY-A.

FD pax-vission-A.
01 pax-vission-rec-A.
02 Unique-KEY-A.
03 Unique-KEY-date-A pic 9(8).
03 Unique-KEY-time-A pic 9(6).
03 Unique-KEY-cntr-A pic 9.
03 Unique-KEY-reg-no-A pic xx.
02 filler pic x.
02 pax-compile-line pic x(20).
02 raw-ilogPax-data-A pic x(1000).

**********************************

We are adding a declarative to the files so we can do a sleep loop to retry accessing the files and also log when these occur. Any suggestions on things we should look for and/or include in our log?

We'll keep chipping away at it. It happens so infrequently (once every week or two), it may take a while to track down. Thanks!

We have one client location that is having infrequent File Error 93 issues. The error has happened with two different files. Both are Vision files. They are running a small network of Windows 10 and Windows 7 computers. The files are hosted on a Windows 10 computer. They are using the extend 9.2.2 ECN-4266 runtime. The errors occur when they get busy/active. However, it doesn't always happen when they are busy. I've included the SELECT and FD for both files. One has a variable length record. The other is "normal". They are opening, reading from, writing to, and closing other files (Vision, binary, and line sequential) on the same network drive share.

**********************************

SELECT PAX-SIG-FL ASSIGN TO RANDOM "PAXSIGFL"
WITH COMPRESSION
ORGANIZATION IS INDEXED
ACCESS MODE IS DYNAMIC
RECORD KEY IS PAX-SIG-KEY.

FD PAX-SIG-FL.
01 PAX-SIG-REC.
02 PAX-SIG-KEY.
03 PAX-SIG-TRAN-NO PIC x(7).
03 PAX-SIG-TRANS-DATE pic 9(6).
03 PAX-SIG-NUM pic 9.
02 SIG-BYTES pic 9(5).
02 PAX-sig-jpg-array.
03 SIG-jpg-byte pic xx occurs 0 TO 12000 TIMES
DEPENDING ON SIG-BYTES.

**********************************

SELECT pax-vision-A ASSIGN TO RANDOM "PVDAA"
WITH COMPRESSION
ORGANIZATION IS INDEXED
ACCESS MODE IS DYNAMIC
RECORD KEY IS UNIQUE-KEY-A.

FD pax-vission-A.
01 pax-vission-rec-A.
02 Unique-KEY-A.
03 Unique-KEY-date-A pic 9(8).
03 Unique-KEY-time-A pic 9(6).
03 Unique-KEY-cntr-A pic 9.
03 Unique-KEY-reg-no-A pic xx.
02 filler pic x.
02 pax-compile-line pic x(20).
02 raw-ilogPax-data-A pic x(1000).

**********************************

We are adding a declarative to the files so we can do a sleep loop to retry accessing the files and also log when these occur. Any suggestions on things we should look for and/or include in our log?

Seeing the files are in a shared directory, my best guess is that Windows Opportunistic Locking is involved. Disabling OpLocks may provide relief, but the declarative should work around the issue.

We have one client location that is having infrequent File Error 93 issues. The error has happened with two different files. Both are Vision files. They are running a small network of Windows 10 and Windows 7 computers. The files are hosted on a Windows 10 computer. They are using the extend 9.2.2 ECN-4266 runtime. The errors occur when they get busy/active. However, it doesn't always happen when they are busy. I've included the SELECT and FD for both files. One has a variable length record. The other is "normal". They are opening, reading from, writing to, and closing other files (Vision, binary, and line sequential) on the same network drive share.

**********************************

SELECT PAX-SIG-FL ASSIGN TO RANDOM "PAXSIGFL"
WITH COMPRESSION
ORGANIZATION IS INDEXED
ACCESS MODE IS DYNAMIC
RECORD KEY IS PAX-SIG-KEY.

FD PAX-SIG-FL.
01 PAX-SIG-REC.
02 PAX-SIG-KEY.
03 PAX-SIG-TRAN-NO PIC x(7).
03 PAX-SIG-TRANS-DATE pic 9(6).
03 PAX-SIG-NUM pic 9.
02 SIG-BYTES pic 9(5).
02 PAX-sig-jpg-array.
03 SIG-jpg-byte pic xx occurs 0 TO 12000 TIMES
DEPENDING ON SIG-BYTES.

**********************************

SELECT pax-vision-A ASSIGN TO RANDOM "PVDAA"
WITH COMPRESSION
ORGANIZATION IS INDEXED
ACCESS MODE IS DYNAMIC
RECORD KEY IS UNIQUE-KEY-A.

FD pax-vission-A.
01 pax-vission-rec-A.
02 Unique-KEY-A.
03 Unique-KEY-date-A pic 9(8).
03 Unique-KEY-time-A pic 9(6).
03 Unique-KEY-cntr-A pic 9.
03 Unique-KEY-reg-no-A pic xx.
02 filler pic x.
02 pax-compile-line pic x(20).
02 raw-ilogPax-data-A pic x(1000).

**********************************

We are adding a declarative to the files so we can do a sleep loop to retry accessing the files and also log when these occur. Any suggestions on things we should look for and/or include in our log?

We have had this problem on Windows, where the culprit was anti-virus software, especially when the mode to actively scan files as they are changed, is active. As expected, the files that are most often accessed are those most affected; it seems frequent access "triggers" the anti-virus software to "check" the file, which results in a file error 93 in Cobol.

We have one client location that is having infrequent File Error 93 issues. The error has happened with two different files. Both are Vision files. They are running a small network of Windows 10 and Windows 7 computers. The files are hosted on a Windows 10 computer. They are using the extend 9.2.2 ECN-4266 runtime. The errors occur when they get busy/active. However, it doesn't always happen when they are busy. I've included the SELECT and FD for both files. One has a variable length record. The other is "normal". They are opening, reading from, writing to, and closing other files (Vision, binary, and line sequential) on the same network drive share.

**********************************

SELECT PAX-SIG-FL ASSIGN TO RANDOM "PAXSIGFL"
WITH COMPRESSION
ORGANIZATION IS INDEXED
ACCESS MODE IS DYNAMIC
RECORD KEY IS PAX-SIG-KEY.

FD PAX-SIG-FL.
01 PAX-SIG-REC.
02 PAX-SIG-KEY.
03 PAX-SIG-TRAN-NO PIC x(7).
03 PAX-SIG-TRANS-DATE pic 9(6).
03 PAX-SIG-NUM pic 9.
02 SIG-BYTES pic 9(5).
02 PAX-sig-jpg-array.
03 SIG-jpg-byte pic xx occurs 0 TO 12000 TIMES
DEPENDING ON SIG-BYTES.

**********************************

SELECT pax-vision-A ASSIGN TO RANDOM "PVDAA"
WITH COMPRESSION
ORGANIZATION IS INDEXED
ACCESS MODE IS DYNAMIC
RECORD KEY IS UNIQUE-KEY-A.

FD pax-vission-A.
01 pax-vission-rec-A.
02 Unique-KEY-A.
03 Unique-KEY-date-A pic 9(8).
03 Unique-KEY-time-A pic 9(6).
03 Unique-KEY-cntr-A pic 9.
03 Unique-KEY-reg-no-A pic xx.
02 filler pic x.
02 pax-compile-line pic x(20).
02 raw-ilogPax-data-A pic x(1000).

**********************************

We are adding a declarative to the files so we can do a sleep loop to retry accessing the files and also log when these occur. Any suggestions on things we should look for and/or include in our log?

We ran into issues with Opportunistic File Locking when Windows 2000 came out. Whenever our program starts, it checks the registry for this setting. If not already disabled, it automatically updates the registry to disable this feature.

Also, since version 5.2.1 of the runtime, we've automatically updated the registry to change the runtime's file access mode from the default "fast" setting to "safe".

We have one client location that is having infrequent File Error 93 issues. The error has happened with two different files. Both are Vision files. They are running a small network of Windows 10 and Windows 7 computers. The files are hosted on a Windows 10 computer. They are using the extend 9.2.2 ECN-4266 runtime. The errors occur when they get busy/active. However, it doesn't always happen when they are busy. I've included the SELECT and FD for both files. One has a variable length record. The other is "normal". They are opening, reading from, writing to, and closing other files (Vision, binary, and line sequential) on the same network drive share.

**********************************

SELECT PAX-SIG-FL ASSIGN TO RANDOM "PAXSIGFL"
WITH COMPRESSION
ORGANIZATION IS INDEXED
ACCESS MODE IS DYNAMIC
RECORD KEY IS PAX-SIG-KEY.

FD PAX-SIG-FL.
01 PAX-SIG-REC.
02 PAX-SIG-KEY.
03 PAX-SIG-TRAN-NO PIC x(7).
03 PAX-SIG-TRANS-DATE pic 9(6).
03 PAX-SIG-NUM pic 9.
02 SIG-BYTES pic 9(5).
02 PAX-sig-jpg-array.
03 SIG-jpg-byte pic xx occurs 0 TO 12000 TIMES
DEPENDING ON SIG-BYTES.

**********************************

SELECT pax-vision-A ASSIGN TO RANDOM "PVDAA"
WITH COMPRESSION
ORGANIZATION IS INDEXED
ACCESS MODE IS DYNAMIC
RECORD KEY IS UNIQUE-KEY-A.

FD pax-vission-A.
01 pax-vission-rec-A.
02 Unique-KEY-A.
03 Unique-KEY-date-A pic 9(8).
03 Unique-KEY-time-A pic 9(6).
03 Unique-KEY-cntr-A pic 9.
03 Unique-KEY-reg-no-A pic xx.
02 filler pic x.
02 pax-compile-line pic x(20).
02 raw-ilogPax-data-A pic x(1000).

**********************************

We are adding a declarative to the files so we can do a sleep loop to retry accessing the files and also log when these occur. Any suggestions on things we should look for and/or include in our log?

We ran into issues with Opportunistic File Locking when Windows 2000 came out. Whenever our program starts, it checks the registry for this setting. If not already disabled, it automatically updates the registry to disable this feature.

Also, since version 5.2.1 of the runtime, we've automatically updated the registry to change the runtime's file access mode from the default "fast" setting to "safe".

We have one client location that is having infrequent File Error 93 issues. The error has happened with two different files. Both are Vision files. They are running a small network of Windows 10 and Windows 7 computers. The files are hosted on a Windows 10 computer. They are using the extend 9.2.2 ECN-4266 runtime. The errors occur when they get busy/active. However, it doesn't always happen when they are busy. I've included the SELECT and FD for both files. One has a variable length record. The other is "normal". They are opening, reading from, writing to, and closing other files (Vision, binary, and line sequential) on the same network drive share.

**********************************

SELECT PAX-SIG-FL ASSIGN TO RANDOM "PAXSIGFL"
WITH COMPRESSION
ORGANIZATION IS INDEXED
ACCESS MODE IS DYNAMIC
RECORD KEY IS PAX-SIG-KEY.

FD PAX-SIG-FL.
01 PAX-SIG-REC.
02 PAX-SIG-KEY.
03 PAX-SIG-TRAN-NO PIC x(7).
03 PAX-SIG-TRANS-DATE pic 9(6).
03 PAX-SIG-NUM pic 9.
02 SIG-BYTES pic 9(5).
02 PAX-sig-jpg-array.
03 SIG-jpg-byte pic xx occurs 0 TO 12000 TIMES
DEPENDING ON SIG-BYTES.

**********************************

SELECT pax-vision-A ASSIGN TO RANDOM "PVDAA"
WITH COMPRESSION
ORGANIZATION IS INDEXED
ACCESS MODE IS DYNAMIC
RECORD KEY IS UNIQUE-KEY-A.

FD pax-vission-A.
01 pax-vission-rec-A.
02 Unique-KEY-A.
03 Unique-KEY-date-A pic 9(8).
03 Unique-KEY-time-A pic 9(6).
03 Unique-KEY-cntr-A pic 9.
03 Unique-KEY-reg-no-A pic xx.
02 filler pic x.
02 pax-compile-line pic x(20).
02 raw-ilogPax-data-A pic x(1000).

**********************************

We are adding a declarative to the files so we can do a sleep loop to retry accessing the files and also log when these occur. Any suggestions on things we should look for and/or include in our log?

Duh! Why didn't we think of that?

I'm adding both the data file and .vix to the file exclusion list on that computer's anti-virus settings.

Thanks, Tony!

Sign up

Please log in or register:

Welcome to the Rocket Forum!

Please log in or register:

Scanning file for viruses.

This file cannot be downloaded