Kbase 21964: QAD Batch File Fails Using cron
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
15/04/2002 |
|
SUMMARY:
When running MFG/PRO Release eB with Progress 9.1C on a UNIX platform, the batch file, batch.dat, fails using the UNIX cron utility. The following 2 errors are output to the acctnow.out file:
**Invalid character in numeric input /. (76)
** Pipe to subprocess has been broken. (140)
A UNIX core file will be generated but no Progress protrace file is produced. Also, the batch.dat file works with no errors at the command line. Although the batch file has root permissions, it will still fail in cron. If cron is output to a log file, error 4032 is also produced:
TERM env variable is not set. Assuming an ANSI terminal. (4032)
EXPLANATION:
Although these errors might appear to be Progress related, they are instead related to the API calls that the MFG/PRO login process makes. The environment variable SHLIB_PATH, which is related to the Vertex API for root's cron, is not set, therefore causing the API to fail and core dump.
SOLUTION:
To avoid the errors, set the SHLIB_PATH to the directory where the Vertex libraries are installed for root's cron, or set it in the batch file.