528   Not writing to Oper component operTm

This tissue has following status: green

Created: 24 Apr 2007

Links:

Page:

Clause: 20.3

Paragraph: Table 69

Category: Issue for edition 2 of this part

Issue: The requirement in Note 3 to "not writing to operTm" requires to use MMS AlternateAccess if we write to a single structured MMS NamedVariable "xxx.Oper" (with components ctlVal, origin, ...). In the AlternateAccess we specify the components we want to write to ... so the component operTm will not be in that "list".

The writing to "xxx.Oper" should not need to use Alternate access. The order in the list of components may vary from write to write ... this could cause a problem. We would need to define the right order!

It seems to be better to just write a zero (0) value so that the NamedVariable is completely written ... and no AlternateAccess is required for that.

Proposal: Note 3 should be changed to: "The attribute operTm shall be set to zero (0) during the operate service, if the service is not a TimeActivatedOperate or to any other positiv value in case it is a TimeActivatedOperate."

Discussion Created Status
?
Ballot until Editor
The CDV defines the TimeActivatedOperate Request as follow:
"
The operate with TimeActivation service shall be performed through the use of an MMS write to the oper attribute with the parameter OperTm present containing a valid timestamp. The value OperTm = 0 (i.e. with all octets set to 0) is equivalent to control with enhanced security (i.e. without time activation).
"
This is in line with the 7-2 CDV
11 Dec 08 green
Will update 20.3 to remove the note and update 20.7.1.3 to define that a value of (0) is defined to be all octets having a value of 0. 26 Mar 08 final proposal 26-04-2008
Clause 20.3 note 3 is unclear. Propose to change to "The attribute operTm, if present, shall be written with all octets 0, otherwise it is a TimeActivatedOperate."
Also note 4 could be clarified as "The attribute operTm shall be written with a non-zero value during the TimeActivatedOperate service, otherwise it is an Operate."
22 Feb 08 final proposal
Changed to final proposal. 15 May 07 final proposal 15-06-2007
No alternate access is required for the time-activated operate.

There are two different types for the sbow/oper/cancel structures:
- one without operTm for Control Objects that do not support the service time-activated operate - see also 7-3, the attribute operTm is AC_CO_O; and see annex E in 8-1 operTm is AC_CO_TA_E_M.

- one with operTm for Control Objects that do support the service time-activated operate - see annex E in 8-1 operTm is AC_CO_TA_E_M.

The clause 20.7.1.3 specifies furthermore:
"The operate with TimeActivation service shall be performed through the use of MMS write to the oper structure with the parameter OperTm present containing a valid time stamp.
The value OperTm = 0 is equivalent to control with enhanced security (i.e. without time activation)."

The note 3) only specifies the difference of the mapping between the services operate and time-activated operate.
14 May 07 red

 

Privacy | Contact | Disclaimer