Kbase P14511: Error 379 when using OS-COMMAND
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
17/02/2010 |
|
Status: Verified
SYMPTOM(s):
Error 379 when using OS-COMMAND
** OS command too long. (379)
OS-COMMAND fails because the command line is too long.
OS-COMMAND can also fail with no error at all. The DOS command prompt is started, but there is nothing else echoed to the screen.
FACT(s) (Environment):
On MS-Windows the actual limit is 80+/- characters
The limit with 9.1C on Windows 98 is 122 characters
The limit with 9.1D or later, 10.0A or later, 10.0B or later on Windows 32 bit is 200 - 230 characters.
Progress 9.x
OpenEdge 10.x
Windows
CAUSE:
Bug# 20041210-001
CAUSE:
There is a limit on the length of the command prompt, this is due to a redirection issue in Microsoft that forces Progress to use %COMSPEC% /C and this is set to a low value on Windows 98.
FIX:
Upgrade to 10.1A. The limit was increased to 2048.
If the upgrade is not possible, the following can be used as a workaround:
1) Build the os-command in an output file and then use OS-COMMAND to run the generated batch file.
Customers trying to use quoter and hitting this limit could (should) also be introduced to the IMPORT UNFORMATTED 4GL statement that allows them to completely eliminate the usage of QUOTER with the downside of some additional 4GL coding.
2) Use OS COMMAND NO-WAIT to avoid this limit. Note that the NO-WAIT option may be subject to different limitations based on exact OS version and configuration.
3) Use CreateProcess function from the Kernel32 library (kernel32.dll).