[Css-csts] RE: #4 SCDP question ('unable to process')

[Ray, Timothy J. (GSFC-5830)]

After further review, there does not seem to be any problem.   When the Provider's production status becomes 'halted', the Provider enters the 'active.locked' substate.  Before the User can successfully transfer any more data to be processed, it is necessary to either "STOP and START" or invoke an EXECUTE-DIRECTIVE operation requesting a 'reset'.  Either way, the User specifies the value of the data-sequence-counter to be used in the next PROCESS-DATA.  So, no problem.

Best regards,
Tim

From: css-csts-bounces at mailman.ccsds.org [mailto:css-csts-bounces at mailman.ccsds.org] On Behalf Of Ray, Timothy J. (GSFC-5830)
Sent: Monday, April 15, 2013 4:11 PM
To: css-csts at mailman.ccsds.org
Subject: [Css-csts] #4 SCDP question ('unable to process')

Hi,

Suppose the following sequence occurs:

User:  START-invocation  first-data-sequence-counter = 0
Provider:  START-return  positive return

User:  PROCESS-DATA-invocation  data-sequence-counter = 0
Provider:  PROCESS-DATA-return  positive return

User:  PROCESS-DATA-invocation  data-sequence-counter = 1
Provider:  PROCESS-DATA-return  positive return

At this point, the Provider's production status becomes 'halted'.

User:  PROCESS-DATA-invocation  data-sequence-counter = 2
Provider:  PROCESS-DATA-return  negative return 'unable to process'



Can we assume that, due to being halted, the Provider will not accept any further PROCESS-DATA invocations during this service instance (actually, to be more specific, until after the current instance of the SCDP procedure goes away and is replaced by a new instance)?

If the answer is 'no', then a follow-up question:

What is the appropriate data-sequence-counter to use for the next PROCESS-DATA-invocation?

Best regards,
Tim

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ccsds.org/pipermail/css-csts/attachments/20130415/cea553bf/attachment.html