povf keeps giving smaller and smaller results, seems to be related to
the number of accesses to files in the format dos: . it 's almost
as if the dos file access leave something behind. in r83 i used to do a
link-ws command to free it up.

Pick can't handle anything that isn't Pick.

When you open a file from OSFI such as dos:drive:\path must first be brought
into VME to be processed.

If you're openning a file several MB or GB, it eats up overflow quickly.

I believe this information is cached for a while in case you open the file a
second time.

Does the overflow come back if you logoff the user?

Mark Brown


<EMERY_BILL (AT) HOTMAIL (DOT) COM> wrote

some of it seems to mark, here is an example, we use a osfi file that
is picked up by pccharge for processing our online credit cards. i
build a .in file and then wait for an .out file .......
after processing i loose about 10 frames as if some of it isnt coming
back

Bill,

We do the exact same thing. Our CC processing, both character and gui, post
the request into a DOS folder where a VB project picks it up and processes
it. We loop for a while waiting until the OUT record is ready which
contains the auth code and authorized amount. But since the individual
users typically won't logoff until end-of-day, the overflow doesn't comeback
right away.

I just tested on my 7.3.1. I had 110074 when I logged on; 110016 after
running a program that opens a dos file and writes a simple record. After
logoff and log back on, I had 110074 again.

Mark

<EMERY_BILL (AT) HOTMAIL (DOT) COM> wrote

we are using 7.1.4 and it doesnt return all the overflow, guess i
need to upgrade.



Mark Brown wrote:

FWIW we just changed some routine in Visage to use c%function calls
rather than OSFI for a similar reason (actually worse, as we could
generate system aborts - action item 31570 - I/O through OSFI to the
NTFS file system can abort into a system exception when run on multiple
lines.)

This has been an "issue" with NT with every release - sometimes better,
sometimes worse. When they address this action item, should be "nice"
thereafter - meanwhile use the C functions if possible, as these appear
to work AOK

(BTW, 7.3.x prior to 7.3.6 had LOTS of "issues" IMHO, so I'd fix that
if possible too!)