A few days ago about 10% of our production sites started experiencing rbase
"hangs" during our nightly unattended batch database update process. These
are NT 4.0 servers running a batch file that we invoke from our file
transfer product. When the batch is invoked it is within a "cmd.exe" DOS
environment (vs. "command.com"). We are using rbase 4.5. I believe that
recent changes in our batch update process require more resources than what
the default DOS environment provide.
I have saved e-mails from this list that recommend setting files and buffers
to 60 and increasing the environment space if long paths or setting
environment variables. Since I'm not invoking this with a .pif, I've
updated \winnt\system32\config.NT with these enhancements. However, the
settings are not recognized and I get the default environment. Microsoft
TechNet states that since cmd.exe is not 16-bit, it does not use config.NT
nor autoexec.NT. Only if I use 16-bit command.com as the DOS environment
will these files be used. Is there a way to increase files, buffers, and
environment space when using cmd.exe? In which DOS environment should the
dos4gw/rbase runtime be running (cmd.exe or command.com)? Also, I'm not
using any command line switches other than "-r" on the runtime.
Thanks for your invaluable assistance!
