Noam,

I've used the simple technique of building a dummy file at the beginning of a
job.  If the job finnishes successfully the file is then purged.  The next job
looks for this file, at the beginning, if found the job either runs in a loop or
terminates.
Hope this helps?

Larry B.

Noam Koren wrote:

> Hello all.
>
> I would like to know if there is a way to be informed when a Job starts or
> ends NOT to the console but to another application (i.e. a way to ask the OS
> to invoke something when the job starts or ends).
>
> I currently use a command that I insert into the Job itselt at the beggining
> and the end of the job file.
> But - I have a problem when something in the job goes wrong and the Job is
> Flushed - the last command is not invoked so that I dont get a notice.
>
> Example:
> !job jjj,us.ac
> !jobmsg.bin.acc                      <-- send message through tcp/ip
> !
> ! other commands
>
> oops - ERROR - Job flushed
> !
> ! other commands
> !
> !jobmsg.bin.acc                      <-- send message through tcp/ip actualy
> !EOJ                                     not invoked
>
> Is there a solution for this?
> TIA for any idea.
>
> Noam