Hi, this is interesting - so something else is sent which identifies directly the executed job? something like job id? So far we had worked with various job submission services let me say - and always we got job id, the case is how to check later the job status for example? The unique pair we used always was: uri of the target system + job id got form there after job submission. In the case you mentioned there is some other information (not job id) which finally is unique and identifies submitted job in the given service? if yes then we can treat it as something like job id. Dawid Donal K. Fellows napisał(a):
dejw wrote:
I agree, this is some solution (magic names) but I have to dig into EPRs as it is good for a user to know real job id - later any debug action could be done directly between user and supervisor of the target BES service and target job management service (it was checked by us in practise). If user doesn't know the real job id then the portal admin has to be involved to get it somehow in some critical situations let's say. So finally I have to get it anyway.
I know of at least one implementation that won't tell you the job identifier, no matter how you look in the EPR. You *can't* rely on it being there.
Donal.