There are several ways to achieve this depending on how difficult you want to make it.
A way that I like to work is to create a couple of "reporting" jobs. One to be used at the beginning of each job (using a tPreJob component) and one to be used at the end of each job (using a tPostJob component). I have a back end database and every time a job starts or ends I use these jobs to log details about it. There is loads you can log but "job name", "start date", "end date", "status", "pid", "total rows", "success rows", "failed rows", etc, might be a nice place to start. The advantage of using the tPostJob to trigger your "end job" Job is that it will always run...even with a Java error. So you will always be able to log a status for the run. If you use the pid (process id) you can also link these results with the AMC functionality. I have written a piece on the AMC here (https://www.rilhia.com/tutorials/talend-activity-monitoring-console-amc). You may actually be able to get away with just using the AMC, but I use the above method to "hook in" to other bits and pieces.
With regard to killing the job immediately, you can either make use of the "Die on child error" functionality supplied within the tRunJob component, or you can make use of the "CHILD_RETURN_CODE" globalMap variable for the job. This can be useful in deriving your own logging logic. But essentially, the job will return a number which can be accessed using the following code....
((Integer)globalMap.get("tRunJob_1_CHILD_RETURN_CODE"))
....the number of the tRunJob changes depending on which one you are referencing. If this number is 0, everything is fine. You can set the output using the tDie component. The tDie will also end your job immediately.
The difference between OnSubJobError and OnComponentError is that the OnSubjobError is triggered by a SubJob error and the OnCOmponentError is triggered immediately by a component error. An easy scenario to describe of how these can be used differently is with an OnSubJobError you will do something on any error within the SubJob. With an OnComponentError, you can do different things per component within the SubJob that errors. To be honest though, I rarely use them. They do not work as you would expect in many cases and are certainly not uniform in how they report on errors. For example, OnComponentErrors work in very strange ways with some database components.
EDIT: I have just looked at your screenshot and feel I may have gone a little over board with my brain dump here. You may be able to solve your problem quickly using RunIf links checking the status of the child job (using the code above) and connecting to a tDie.
