Corrupt Index FILE STATUS

[Nagrom]

I am working in Microfocus NetExpress 3.0 and I am getting a file status of 9:41 (binary status-key-2 is the 41), which means "corrupt index file" according to the documentation, but I know the index file is good because I am accessing it from other programs. Anyone have ideas as to the cause? I am accessing it with:

ASSIGN TO DYNAMIC WS-FILE-LOCATION
ORGANIZATION IS INDEXED
ACCESS MODE IS DYNAMIC
LOCK MODE IS MANUAL
RECORD KEY IS <FILE KEY FiELD>
ALTERNATE RECORD KEY IS <ALTERNATE FILE KEY>
WITH DUPLICATES
FILE STATUS IS WS-FILE-STATUS.

I get the error on OPEN INPUT.

 

[MKuiper]

I think this happens if two or more programs have the file open at the same time. If this is the case, there are some things you can try:

1. In the past we have noticed corrupt index problems on some (not all) systems, if at the same time a program opened a file I-O and another program opened the same file INPUT. Opening the file I-O in all programs, even those with the intention of only reading the file, solved the problem.

2. The latest 3.0 fixpack (this is some time ago, current release is 3.1) from Micro Focus solved a lot of corrupt index problems, especially if &quot;READSEMA=OFF&quot; was specified in extfh.cfg. You may try on

http://www.microfocus.com

(and NOT

http://www.merant.com,

because Micro Focus has become an independant company again.)

3. Change settings in extfh.cfg. What is it contents?

4. The most radical solution which will solve 99% of the corrupt index problems is using file-share, but in most cases this also causes loss of performance.

Marcel

 

[Nagrom]

I've tried opening it I-O and that didn't solve the problem. I do know that no other program is accessing the file because I have it on a development server that only I am using. I am not familiar with the READSEMA=OFF thing you mention above (or the extfh.cfg, for that matter) - can you give me more information on what exactly that is and how you use it? Also, I am unfamiliar with what you are talking about when you say file-share. Are you refering to the LOCK statement?

Thanks for your help. If nothing else I've got some other places to look now. I think I have the latest fixpack, but I'll double check to make sure.

 

[MKuiper]

Nagrom,

I have seen many corrupt indexes, but never when a program accesses a file alone, so I have no experience with that. The only reason I can think of, is the index is really corrupt. Did you try the rebuild utility to rebuild the index file?

File-share is a server program which is packaged with the Net Express installation. If you use it, all I-O statements are redirected to file-share, which opens the files in exclusive mode. The online documentation contains a complete manual about it, called File-share Users Guide.

extfh.cfg is a file, which may or may not exist. It configures the behaviour of the Net Express I-O routine EXTFH. You can search in the online documentation for it, it would cost me several days to describe all the options here.

Marcel

 

[Nagrom]

Yep, I tried rebuilding the index and that didn't work either, though since other programs can access it I really did not think that was the case anyway. I'll check the doc on extfh to see if I can find something to help.

I appreciate your suggestions. Thanks for the help.

 

[MKuiper]

What is the difference between the program having trouble and the program having no trouble? Marcel

 

[Nagrom]

One of them is using an absolute path for the ASSIGN TO statement, while the other is using ASSIGN TO DYNAMIC. I am using that same method to access all the files in the program in question, though, and the other files all work just fine.

 

[MKuiper]

Sorry Nagrom, I'm out of this one. But I would like to know if you found a solution how you did that.
Marcel