Very Computer

Quote:Keith A. Clay writes:

[Charset ISO-8859-1 unsupported, filtering to ASCII...]
[You can also use 'v' to view or save this part.]

Quote:> I am trying to run IQ (Intelligent Query Report Writer) scripts from
> cron so that reports can do processing at night.  The problem is that
> they bomb.  They run fine from a prompt and run fine from 'at'.  Is
> there a way to trick IQ into thinking that it is actually running on a
> terminal?

> example command line:
>   % iq3 -Q -dddmst3.dat -pparameter_file DATABASE_PROCEDURE_NAME

> where -Q - tells it it is a batch and use iqbatch.err for errors
>       -d - tells it which data dictionary
>       -p - is basically the search criteria

> Does anyone use IQ in this way, or know a way around the problem?

There is no trick at all, just use the standard Bourne shell grammar for
putting variables into the environment of a command:
        A=a_value S=something command
or in your case
        TERM=wy50 iq3 -Q -dddmst3.dat -pparameter_file DATABASE_PROCEDURE_NAME
noting that probably ANY valid value for TERM will probably work.

--

On that line, the semicolon is NOT required.

And even
        TERM=wy60 export TERM
        command
can in turn be written even more simply on one line as
        TERM=wy60 command

--

Quote:>    TERM=wy60 export TERM
>    command
>    TERM=wy60 command

Beware here.
The first example works, due to the nature of export;
The second example only sets TERM for COMMAND, for the rest of the script
TERM has its old value, which in this case is nothing.

--
--
Sam Liddicott                  |   Nothing I say is to be attributed as
Campbell Scientific Ltd.       | a company statement or representation.
14-20 Field Street, Shepshed,  *----------------------------------------