Re: output on batch systems

I forgot to mention that I am redirecting the script output to a file
and my actual question became unclear, sorry.
I usually submit a job like this:

qsub ncl < job.ncl 1>out 2>err

And my problem is that this "out" file with all the output is only
produced when the script ends and not when it's actually running like
when we run a fortran program. The interactive mode would actually
help if I could keep my terminal window open for a week which is not
the case. Since I am running long scripts it would be very helpful to
follow how the script is doing while it's running. I usually do it
with a

tail -f out

if "out" is produced by a regular fortran code. This doesn't seem to
work with NCL scripts, for some reason.

Cheers,
João

2012/2/7 Robert Schuster <rxschuster@googlemail.com>:
> Hello João,
>
> read the man page of the qsub command (TORQUE). You can run jobs interactively with the -I parameter.
> That has nothing to do with NCL!
>
> Robert
>
> Am 07.02.2012 um 11:56 schrieb João Martins:
>
>> I am running NCL scripts using batch systems and a problem that
>> frequently run into is that I can't follow how the script is running.
>> When running in interactive mode, my scripts send information to the
>> screen like the iteration number on a loop, or a date. When I submit
>> them to a batch queue system, the output is only produced when the
>> script ends, so I can't really see how it is doing. Is there a way to
>> get around this? I've noticed this behavior both in a SLURM and in a
>> TORQUE system.
>>
>> Any help would be great!
>>
>> --
>> João Martins
>> _______________________________________________
>> ncl-talk mailing list
>> List instructions, subscriber options, unsubscribe:
>> http://mailman.ucar.edu/mailman/listinfo/ncl-talk
>

-- 
João Martins
_______________________________________________
ncl-talk mailing list
List instructions, subscriber options, unsubscribe:
http://mailman.ucar.edu/mailman/listinfo/ncl-talk