crontab problems with 4ge
Posted in 1994
Topics: Connectivity: ESQL/C, 4GL & Embedded SQL, Platform-Specific Issues
Only just one of a few problems of late :( ...
Platform info:
IBM RS/6000 Powerstation 350
running AIX 3.2.5
Informix 4GL ver 4.1
SE ver 5.0
We're running a 4gl Informix program to feed our class schedule
listings into our gopher site. The script used to FTP data,
load it, and generate the reports works fine when run from
a command line, but when we run it from a crontab entry:
--------------------------------------------------------------
Message 1:
From daemon Fri Jul 15 17:41:02 1994
Date: Fri, 15 Jul 1994 17:41:02 -0400
From: daemon
To: gopher
Program stopped at "schedrpt.4gl", line number 31.
SQL statement error number -408.
Invalid message type received from the sqlexec process.
*************************************************
Cron: The previous message is the standard output
and standard error of one of your cron commands.
--------------------------------------------------------------
The source statement of error is:
(schedrpt.4gl) -----------------------------------------------
SELECT UNIQUE term
INTO termid
FROM schedmast
--------------------------------------------------------------
Nothing fancy, right?
The script file called by the crontab entry is:
--------------------------------------------------------------
#! /usr/bin/ksh
echo ----- FTPing latest schedmast from AS/400
ftp as400
cd /u/gopher/schedmast
echo ----- Using SED to change \\/ to \\-
sed "y|/|-|" schedule.upload.txt > tmp
mv tmp schedule.upload.txt
chown -f gopher /u/gopher/schedmast/schedule.upload.txt
chmod -f a+rw /u/gopher/schedmast/schedule.upload.txt
echo ----- Loading schedule into database
/u/gopher/schedmast/schedload.4ge
echo ----- Generating class schedule listings
/u/gopher/schedmast/schedrpt.4ge
echo ----- Done!
--------------------------------------------------------------
The schedload.4ge runs just fine.
At one point I was struggling with what I thought was inproper
granted access to the database/tables, but all objects are now
owned/run by the gopher profile.
Any suggestions, comments, insights are pure gold to me at this point. :)