To elaborate on James' suggestion with a bit more detail
(but this requires either a) you can rename the official jobs
and create job wrappers with the original name, or b) you have
freedom to directly stream a job by a different name than the
"official" job names):

  Job wrapper:
     !job j,u.a,g;... # wrapper for official job with similar name
                      # The official name could be derived from this
                      # job "card"
     !stream !hpjobname.!hpgroup.!hpaccount  # the "official" job
     !pause job=!hplastjob;wait
     !# now we know that the official job is executing
     !# ...do tcp notification of job start
     !pause job=!hplastjob
     !# ...do tcp notification of job termination
     !eoj

Also, as James mentioned, if your official job streams jobs
from inside then you may want to consider a STREAM UDC that
performs something similar to the above.

HTH,
Jeff Vance, CSY

> If all your jobs are started from a scheduler or command
> prompt and idea
> would be for you to write a job wrapper. Given job name as a
> parameter, this
> script would log on as a job then stream the actual job you
> are interested
> in. Get the job# from the new CIVARS and do a wait for that
> job to finish.
> When your actual job logs off then wait is satisfied and you
> can then send
> your messages from wrapper job.
> If your jobs are imbedded within other jobs then this option fails the
> restriction of not allowing job modification.
>
> James