The procedure for SBOES does not really cover controlling of BSC data objects.
List of cases:
1. Persistent - Stop command: The step value should not change. Does this mean the server should send positive terminate command immediately?
2. Persistent - Higher command: This is OK. Any value change higher than current step value would trigger positive terminate command.
3. Persistent - Lower command: This is OK. Any value change lower than current step value would trigger positive terminate command.
4. Non-persistent - Stop command: The step value should not change. Does this mean the server should send positive terminate command immediately?
5. Non-persistent - Higher command: This is OK. Step value incrementing would trigger positive terminate command.
6. Non-persistent - Lower command: This is OK. Step value decrementing would trigger positive terminate command.
Proposal
Am I interpreting this correctly?
Discussion
Created
Status
According to 7-3 Ed2.1 - BSC specification - definition of persistent
If 'persistent' = true, ... and 'ctlModel' shall be set to 'direct-with-normal-security'.
SBOES does not apply to BSC data objects with persistent = true.
In case of persistent=false, the procedure exposed in the step machine will not wait for a state change "waitForChange" in case of ctlVal = stop, because the step position will not change. Most likely the ctlVal stop is of no use for BSC objects with persistent=false, because the ctlVal higher or lower will complete after one step, and there is nothing to stop.
Propose to set to NA.
21 May 24
Approval (N/A)
According to 7-3 Ed2.1 - BSC specification - definition of persistent
If 'persistent' = true, ... and 'ctlModel' shall be set to 'direct-with-normal-security'.
SBOES does not apply to BSC data objects.
Propose to set to NA.