This links to a previous thread I started on here about notification actions and events in COM

http://www.softtreetech.com/cgi_bin/config.cgi?read=4699

which you helped me to sort out, and I've now come up against something else.
I have the 2 jobs set up and Job 1 will run Job 2 if Job 1 is scheduled to start.
However if I start it using the RunJob command in COM only job 1 will run.
Can you help? Am I doing something wrong?

Thanks
Duncan

Where are you calling RunNow? In the job script (VBScript) or in the notification action(JALScript)?

: This links to a previous thread I started on here about notification actions
: and events in COM

: http://www.softtreetech.com/cgi_bin/config.cgi?read=4699

: which you helped me to sort out, and I've now come up against something else.
: I have the 2 jobs set up and Job 1 will run Job 2 if Job 1 is scheduled to
: start.
: However if I start it using the RunJob command in COM only job 1 will run.
: Can you help? Am I doing something wrong?

: Thanks
: Duncan

RunNow is called from our interface (which contains a list of scheduled jobs)
There is a tool bar button that enables the user to run the selected job (much the same as in your GUI)

: Where are you calling RunNow? In the job script (VBScript) or in the
: notification action(JALScript)?

I think I now understand what you are doing. There is no RunNow API function. You probably mean the RunJob function, right?

The RunJob function doesn't trigger a job. Instead it grabs the job definition (without triggers and notifications) and runs it as if it was a dynamic job.
The solution to linked job run in this case is to use RunShellCommand instead of RunJob as below

RetCode = com_obj.RunShellCommand("24x7 /JOB id_of_job_to_run", "", True, 0)

: RunNow is called from our interface (which contains a list of scheduled jobs)
: There is a tool bar button that enables the user to run the selected job
: (much the same as in your GUI)