DataFlex 3.2 DFSort running out of memory
May 23, 2019 4:07:37 GMT 1
Post by nelsonhd on May 23, 2019 4:07:37 GMT 1
Hello:
Testing vDos version 2017.08.01 on Windows Server 2016 1607.
The place where I work uses vDos to run a DataFlex database on 64-bit systems with dot-matrix printers since 2018, since using the 32-bit runtime version just prints reports badly, even with Generic-Text Only printing (Epson commands get corrupted, not real ASCII). vDos does the printing as it was on 32-bit Windows.
The database files are on a file server and it works as an ISAM database, requiring reindexing almost every night.
When running the DFSort command to reindex all the tables, the utility doesn't want to create the index files after working with at least five or so tables with at least five indices each. After that, it just reads the records but it does not reindex the files as expected and then bypasses the files completely.
When checking the DFSORT.LOG file, it enumerates the non-sorted files on different lines with an entry like this:
ABORTED Sort of file '<FILE/TABLE>' terminated. Error 10 occurred (Out of memory).
The generated index files are named as <FILE/TABLE>.k<index number from 1 to 99>
Example: FILENAME.K1, FILENAME.K10 (all files are 8.3 files).
It looks like the DFSORT utility does not release memory once the index files are remade. Not very good. Some tables have hundreds, thousands or 10000s or more records, and the biggest one has 100s of MBs.
edit: Ran DFSORT on NTVDM and memory is released once a file is sorted.
I checked the config.txt file for memory settings and I checked the comments on it, but I cannot get it right and doesn't run/runs with error.
Is it possible to increase available memory for vDos to run the DFSORT utility? How can I do that?NTVDM provides all physical memory on 32-bit systems to DFSORT. DFSORT states available memory in KBs when sorting every file, and it works correctly on 32-bit.
edit: DFFILE and others get approx. 32 MB of RAM on NTVDM, while vDOS only allocates no more than 8 MB.
While the DataFlex runtime has a Win32 option we use on systems without printers, DFSORT and other utilities can only run on a DOS environment. DFCOMP (compiler) runs fine, but DFFILE (table design utility) may not run fine when adding fields until the DFSORT memory issue is solved.
Regards,
Nelson.
Testing vDos version 2017.08.01 on Windows Server 2016 1607.
The place where I work uses vDos to run a DataFlex database on 64-bit systems with dot-matrix printers since 2018, since using the 32-bit runtime version just prints reports badly, even with Generic-Text Only printing (Epson commands get corrupted, not real ASCII). vDos does the printing as it was on 32-bit Windows.
The database files are on a file server and it works as an ISAM database, requiring reindexing almost every night.
When running the DFSort command to reindex all the tables, the utility doesn't want to create the index files after working with at least five or so tables with at least five indices each. After that, it just reads the records but it does not reindex the files as expected and then bypasses the files completely.
When checking the DFSORT.LOG file, it enumerates the non-sorted files on different lines with an entry like this:
ABORTED Sort of file '<FILE/TABLE>' terminated. Error 10 occurred (Out of memory).
The generated index files are named as <FILE/TABLE>.k<index number from 1 to 99>
Example: FILENAME.K1, FILENAME.K10 (all files are 8.3 files).
edit: Ran DFSORT on NTVDM and memory is released once a file is sorted.
I checked the config.txt file for memory settings and I checked the comments on it, but I cannot get it right and doesn't run/runs with error.
Is it possible to increase available memory for vDos to run the DFSORT utility? How can I do that?
edit: DFFILE and others get approx. 32 MB of RAM on NTVDM, while vDOS only allocates no more than 8 MB.
While the DataFlex runtime has a Win32 option we use on systems without printers, DFSORT and other utilities can only run on a DOS environment. DFCOMP (compiler) runs fine, but DFFILE (table design utility) may not run fine when adding fields until the DFSORT memory issue is solved.
Regards,
Nelson.