That's correct. When the job is submited (think of this as tested) from the Remote Control, only the job definition is send to the Master, or Agent, not the command to execute the selected job. The job processing consists of 4 parts: *----------*....*-------------*....*---------*....*-------------------------* |..schedule.|.....|..job pre-run..|.....|..job run..|......|..post-run notify & error..| |...logic......|-->|....logic..........|-->|....logic....|-->|..handling logic.................| *----------*....*-------------*....*---------*....*-------------------------* Only the third part is executed by the remote component. When you use the Remote Control to run remote job, you basically tell it to send the job definition and run the sent job definition. This is not exactly the same as say "run remote job ABC". : While I can execute the jobs locally without a problem the issue I have with : that is the fact that the jobs while they execute do not appear in the : scheduler log only in the job log of the Remote Control Agent. So if you : go and look at the status report that is generated on the Master Scheduler : or even the Log viewer in the Remote Control it looks as if the job was : never executed. : I have no problem doing local executions if there is some way to syncronise : the logs.
|