That sound about right then. If you had run the distinct like this:
select distinct eh_name,eh_otype,eh_client,eh_status from eh
Then it, would filter on the eh_name, making sure that it only return a unique (one entry of the eh_name).
So the original sql example Alex, shown would of given you all the object (jobs/jobp, script etc...) that is still out in the Activity window...
select eh_name,eh_otype,eh_client,eh_status from eh
So... this may return jobs that are ended_ok already (and waiting the parent to finished) or you might have jobp that complete but have not been deactivated..
Depending on how/what you want for the "currently running" then you can further specific back only jobs that are not in a finished status if you like...
--------------------
On my own system, if I run the sql provided by Alexander it return over 400 jobs/jobp etc... with various status... which in my case a lot of these are running, or waiting for its parent to finish or just have finished and not been deactivated... And when I change it to distinct, it would only return 60 lines, which is correct since what the distinct function does in sql.
See example of Distinct