Correct UWS interpretation

[Andre Schaaff]

Hello,

Also in the execution status field : in the current version, we can 
have a COMPLETED or an ERROR status.
In other job managers you can find something more explicite  like 
COMPLETED, COMPLETED with errors,  COMPLETED with warnings, ...
For workflows it could be useful to have a most important granularity.
And in any case it will be possible to use only COMPLETED and ERROR if 
it is enough for some implementations.

regards

André


On 25/05/11 08:40, Paul Harrison wrote:
> I think that reaching the PENDING state does imply that  the UWS has checked the job details for trivial validation errors - however it is clear that in some cases the full validity of a job cannot be discovered until an attempt is made to EXECUTE, so a client should not assume just because a job has reached the PENDING state that there will be no errors on EXECUTING - it is unlikely to make this assumption anyway, as there is always the possibility of run-time errors.
>
> So the effect of the above statements is that it is really up to the UWS as to how much validation it does before reaching the PENDING state.
>
> Cheers,
> 	Paul.
> On 2011-05 -24, at 20:12, Matthew Graham wrote:
>
>> Hi,
>>
>> We would like some clarification about what is meant to happen when a job is submitted to a UWS service. Does setting the status as "PENDING" mean that the service has checked the job details posted to it and validated the job as valid? Or does it mean that there is a job waiting and checking will only happen when execution is attempted?
>>
>> 	Cheers,
>>
>> 	Matthew
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: andre_schaaff.vcf
Type: text/x-vcard
Size: 321 bytes
Desc: not available
URL: <http://www.ivoa.net/pipermail/grid/attachments/20110525/d0cb88d4/attachment.vcf>