We are running an application in ARev 3.12 on an NT Server.  We are experiencing a problem with a report that creates a large number of DOS files through PDisk.  The program hits a wall after we have created about 190 PDisk'ed files.  The error message is 'W578'; 'Printer output cannot be redirected to a file (not enough file handles)'.

 My config.sys has files=192; and our revparams is:

                    SERVERONLY=1

                    MaximumOpenDosFiles=255

                    MaximumOpenLHFiles=192

  I have two basic questions:

1) Is there any way to configure our system to allow unlimited Pdisk'ing? (Since only one PDisk file can be open at any one time, why does the PDisk appear to be eating up a file handle each time it is invoked? Shouldn't PDisk be releasing the file handle when it is done?)

2) Are MaximumOpenDosFiles and MaximumOpenLHFiles valid switched in Revparams? They don't appear to be documented and the documentation we can find suggests that they are invalid.

I am also experienceing the exact same error message.

I am suspending to dos to run a SNA gateway and after

the computer has run for a long period I recieve the same

error message. My files is set to 200 but I still get it.

How do I close and retreive these file handles.

Dan, some questions:

What OS are you using on the workstation?

What are you trying to do with these pdisks?

Have you tried PDISK PRN betweeen each invocation?

Are you patched on NT server to SP3 or SP4?

Does this occur when you PDISK to short file names

instead of long ones, eg PDISK FILE001 to PDISK FILE255 ?

Have you tried a FLUSH statement between each PDISK?

Sounds like NT more than AREV. I'd be looking

through the known NT 4.0 server registry setting info at

http://support.microsoft.com/

first of all to see if its a known NT problem.

The other technique would be to OSOPEN, OSBWRITE

and OSCLOSE rather than PDISK + PRINT and see if

this works.

Steve

I had this problem before but don't any longer. Here is a test program that I just ran to see how many pdisk files I could open.

save_stack=@tcl.stack

for a=1 to 500

   perform 'pdisk c:\DATA\TXT\pdisk':a:'.txt (os'

   printer on

   print a

   printer off

   call statup(2,3,a)

   @tcl.stack=save_stack

next

When I first ran this program, I directed the pdisk files to my root directory. The root directory is limited in the number of entries, so I maxed out this program at 258 iterations (max entries - #current files in the root). When I changed to a subdirectory, the problem was resolved.

View this thread on the forum...