[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ptp-dev] protocol on job submission
|
Thanks. Now the NEW JOB event works as expected.
Feiyii
Greg Watson wrote:
Yes, you'll need to use the transaction ID of the START_EVENTS command
for any of the model element events.
Greg
On Nov 1, 2007, at 4:49 PM, Feiyi Wang wrote:
I see ... from Spec, this was not (clear) the case.
Does that mean I need to keep track the previous START_EVENT
transaction ID, even when I am dealing with a different command now,
right?
Thanks
Feiyi
Greg Watson wrote:
For SUBMIT_JOB, you should send OK (with the SUBMIT_JOB transaction
ID) as soon as you have successfully queued (or whatever) the job.
It is meant to acknowledge that the submission was successful.
NEW_JOB is not a valid response for SUBMIT_JOB, only for
START_EVENTS, so it should be sent with the transaction ID of the
START_EVENTS command when the job exists (is in a queue for example).
Greg
On Nov 1, 2007, at 3:38 PM, Feiyi Wang wrote:
hi -
when front submits a job - SUBMIT_JOB command is sent over along
with jobSubId. Now, the Spec says proxy agent must send NEW_JOB
event along with that attribute. Two questions: (1) do I need to
send an OK event first? as orte proxy did that. I tried that, but
there is an error message about illegal state; (2) do I have to
begin with JOB_STATE_INIT and progress to JOB_STATE_RUNNING?
thanks
Feiyi
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
