Hide Forgot
Description of problem: This is RFE bug based on 3rd job identification incongruity in bug 630937 Version-Release number of selected component (if applicable): condor-qmf-7.4.5-0.7.el5 Actual results: There is QMF function GetJobAd which doesn't accept job id in form schedd_name#cluster.proc Expected results: All QMF function GetJobAd will accept job id in form schedd_name#cluster.proc
Note that GetJobAd is a method on the JobServer object associated with a Scheduler object, which is always a 1:1 association. Naming a schedd in the GetJobAd argument is superfluous - a JobServer only knows about a specified set of clusters.procs.
I know, that if you want run GetJobAd(), you need know name of the scheduler. But why there have to be any difference in job identification? I think it's confusing now. If there should be any difference in calling functions with JobId, please add it to documentation somewhere(API specification). I think it will be fine that if job doesn't belong to scheduler, it will return False, None or raise exception as in situation when ClusterId doesn't belong to scheduler.
Martin feel free to raise a doc bug if you like.