Ive seen various discussions so far on this as well as one

that I posted a long time ago.

But no one has yet to post a solution as to how to

CLEAR THE FILE HANDLES.

My problem is similar to others

I have a pdisk in my program which is talked about and I also

have a suspend (THE PROGRAM BREAKS ON THE SUSPEND)

saying that I have too many file handles open - cant redirect

printer output. This is an IDX_SETS error.

Im running novel 3.12 arev 3.111 with arev nlm dos 6.22.

All help will be appreciated.

Terry,

If you are running out of file handles, it is possible that your program might simply require more handles. In this case, you can just raise the value of the FILES=??? parameter in your CONFIG.SYS.

Of course, it's also possible that your settings are adequate, but your program isn't closing files. In this case, you would just have to make certain that files are closed after they are used. If you think that your pdisk redirections might be the culprit, be sure to use PRINTER OFF to terminate the print session (and close the file handle). I'm pretty sure there are no functions to close all the file handles, because if there were, it would close all of your file handles, regardless if they should be closed or not since it has no way of telling when is intentionally open versus what is superfluous. If all your file handles were suddenly closed, your program would probably go on the fritz pretty fast.

Hope this helps a little

-Scott

Revelation

If you are using VLM.EXE, try setting in your NET.CFG

FILES=100

and in your config.sys

files=100

buffers=40

This will share the available handles between

network-related files and local files. Then

reduce the numbers a little to regain memory.

Is it some quirk in 3.111?

Is it due to a series of pdisks in succession?

I have rarely seen too many files errors with

Novell 3.12. It's like your network shell is

corrupt, and not redirecting closes to handles,

or the TSR is not working OK. What version of

VLM.EXE is it? I recall that 1.20, 1.20B and

1.21 were OK, 1.02 was bad, and several others

were problematic.

What happens if you revert to the AREV Advanced

Netware network driver - does the problem disappear?

Steve

Hmmmm. I thought that AREV minimizes the number of

open handles at all times, and only opens (then

ASAP closes) most of its LH files while in use.

In any case, a SUSPEND EXIT most probably would

release all but the file handle for the ROLLOUT.SUS

file.

Its behaviour suggests AREV is extremely

conservative in its opening of files. On a Netware

server you can often see only a dozen or less files

in use. Isn't this a good way to tell what sort of

demand exists for the 250 odd free file handles?

Steve

The SUSPEND should close the file handles, but Terry might try doing a GARBAGECOLLECT, FLUSH prior to the SUSPEND. I seem to remember running across this problem back with 2.0x.

Seems like that would work for network file handles but not for local file handles.

It mentioned Novell 3.12.

100 handles should be enough for most pure-DOS sessions.

Any more and something is weird.

Steve

ive set the buffers up to 40

cant find a vlm.exe anywhere

ive already tried setting file handles in net.cfg

and in config.sys does not help.

Right now I use 200 files in config.sys and

the computer manages to run for the whole day.

I reduce the number to 2 and it runs for 2 cycles.

The program running is a cycle based on the indexing

which does 1 pdisk alot of suspends and runs an

SNA gateway through dos.

I should also mention this same problem is occuring at

3 client sites. Therefore it probably is not the config.sys

file as each one has a different config setup.

But I will check each one just in case.

PDISK was also mentioned, which normally would use up local file handles.

Terry:

   If you do find a solution, would you please post it.  We have experienced the same problem on an NT server with Windows 95.  Got a good number of suggestions, but none have worked so far.  We have:

1) Upped the number of file handles in our config files

2) Upped the number of files in our revparams files

3) Tried to manually close a pdisk file with an OsClose command

4) Tried to close files with the Suspend command

   This issue has appeared several times in this discussion group.  I haven't seen a solution yet.

Well Dan the only solution I have found at the moment is this

If i put my files in config sys to the normal amount for AREV which

is about 60 then it breaks with an error about 2-3 times a day.

If I put the files through the roof at 200 we dont usually see the

error at all unless we leave the computer on long enough

for it to happen. NOT REALLY FIXED JUST MASKED THE PROB

So as you said (I AGREE) this problem has been posted here before

with no solution as of yet, sure hope someone finds one :)

View this thread on the forum...