dmsActivateMessage

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dmsActivateMessage",
    "OBJECT-TYPE",
    "SYNTAX",
    "MessageActivationCode",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "\"<Definition> A code indicating the active message. The value of this object may be SET by a management station or modified by logic internal to the DMS (e.g., activation of the end duration message, etc.). When modified by internal logic with a reference to a message ID code, the duration indicates 65535 (infinite), the activate priority indicates 255, and the source address indicates an address of 127.0.0.1. If a GET is performed on this object, the DMS shall respond with the value for the last message that was successfully activated. The dmsActivateMsgError object shall be updated appropriately upon any attempt to update the value of this object, whether from an internal or external source. If a message activation error occurs (e.g., dmsActivateMsgError is updated to a value other than 'none'), the new message shall not be activated and, if the activation request originated from a SET request, a genErr shall be returned. A management station should then GET the dmsActivateMsgError object as soon as possible to minimize the chance of additional activation attempts from overwriting the dmsActivateMsgError. If a message is attempted to be activated via the scheduler or any internal message (e.g., end duration message, etc.) and the message to be activated contains an error, than the following objects shall be set to the appropriate values (as defined within these objects): - dmsActivateMsgError, - dmsActivateErrorMsgCode, - dmsMultiSyntaxError, - dmsMultiSyntaxErrorPosition (if supported), - dmsMultiOtherErrorDescription (if supported), - dmsDrumStatus (if supported) A 'criticalTemperature' alarm shall have no effect on the 'activation' of a message, it will only affect the display of the active message. Thus, a message activation may occur during a 'criticalTemperature' alarm and the sign controller will behave as if the message is displayed. However, the shortErrorStatus will indicate a criticalTemperature alarm and the sign face illumination will be off. As soon as the DMS determines that the 'criticalTemperature' alarm is no longer present, the DMS shall display the message stored in the currentBuffer. <Superseded by> dmsActivateMessageV4 <Informative> This object was deprecated in NTCIP 1203 v04 in favor of MessageActivationCodeV4, which is designed to support IPv6 and to more securely record the source of the request. <Parameter Type> Control <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.6.3\"",
    "::=",
    "{",
    "signControl",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "MessageActivationCode"
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "<Definition> A code indicating the active message. The value of this object may be SET by a management station or modified by logic internal to the DMS (e.g., activation of the end duration message, etc.). When modified by internal logic with a reference to a message ID code, the duration indicates 65535 (infinite), the activate priority indicates 255, and the source address indicates an address of 127.0.0.1. If a GET is performed on this object, the DMS shall respond with the value for the last message that was successfully activated. The dmsActivateMsgError object shall be updated appropriately upon any attempt to update the value of this object, whether from an internal or external source. If a message activation error occurs (e.g., dmsActivateMsgError is updated to a value other than 'none'), the new message shall not be activated and, if the activation request originated from a SET request, a genErr shall be returned. A management station should then GET the dmsActivateMsgError object as soon as possible to minimize the chance of additional activation attempts from overwriting the dmsActivateMsgError. If a message is attempted to be activated via the scheduler or any internal message (e.g., end duration message, etc.) and the message to be activated contains an error, than the following objects shall be set to the appropriate values (as defined within these objects): - dmsActivateMsgError, - dmsActivateErrorMsgCode, - dmsMultiSyntaxError, - dmsMultiSyntaxErrorPosition (if supported), - dmsMultiOtherErrorDescription (if supported), - dmsDrumStatus (if supported) A 'criticalTemperature' alarm shall have no effect on the 'activation' of a message, it will only affect the display of the active message. Thus, a message activation may occur during a 'criticalTemperature' alarm and the sign controller will behave as if the message is displayed. However, the shortErrorStatus will indicate a criticalTemperature alarm and the sign face illumination will be off. As soon as the DMS determines that the 'criticalTemperature' alarm is no longer present, the DMS shall display the message stored in the currentBuffer. <Superseded by> dmsActivateMessageV4 <Informative> This object was deprecated in NTCIP 1203 v04 in favor of MessageActivationCodeV4, which is designed to support IPv6 and to more securely record the source of the request. <Parameter Type> Control <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.6.3"
    ],
    null,
    null,
    null,
    null
  ]
}