vDos stalls while processing job...sometimes

[billgrantford]

I have a job that runs once a day, currently we are seeing it run 50% of the time. The closest consistent item is if one of the files is larger the program stalls and we have to use the task manager to kill the session. Here is some information:


use f:\invoice\combat\packslip exclu

@ 9,5 SAY "CONSOLIDATING FILES ......."



copy to f:\invoice\combat\474file.txt sdf

??"copied"

delete for trim(carton) = " NOTE:"

pack

go top



locate for junk5 = " ISSE REF"

do

if found()

SKIP 2

REPLACE JUNK4 WITH "KEEPER" while val(onhand) > 0 .and. val(cornum) > 0

endif

continue

??"keeper"

until eof()

?reccount()

DELETE FOR JUNK4 # "KEEPER"

PACK



?"deleted nonkeepers"

?reccount()



if reccount() > 0

do f:\invoice\combat\packview

This is not the entire job, but the program fails showing "delete nonkeepers'. Again some days it runs perfect other days it does not I have noticed one of the reports is larger than normal. I've searched the message boards for an answer and I haven't found this situation.

[Jos]

Sorry(?) to say, but I’m actually no DOS user/programmer myself for many years.

You would use FoxPro(X). Could have a look at Windows Task Manager. I guess vDos CPU usage drops to (nearly) 0% in absence of user/disk/network activity for some time. The program wouldn’t really stall, just take an extremely long time to complete its task.

Ensure you use the latest vDos 2021.05.01 version, its CPU usage is more adaptive. Else add something like QUICKIDLE = off, or IDLELOW = 100000 to config.txt.

Mind, that shouldn’t be required for 2021 (and later) versions.

Jos

[billgrantford]

Update, I've updated to the current version of vDos. One of the troubled programs now has a startup response of "Illegal opcode FF at 2020:0107" the only modification is ADMIN = ON.

[billgrantford]

Is it too late to say never mind on the open error...my bad. I will continue testing.