Status in source: mandatory.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"hpiWatchdogTimerUseExpFlags",
"OBJECT-TYPE",
"SYNTAX",
"OCTET",
"STRING",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"Set of values seperated by a delimiter. For each value set, the corresponding Timer Use Expiration Flag will be CLEARED. Generally, a program should only clear the Timer Use Expiration Flag corresponding to its own TimerUse, so that other software, which may have used the timer for another purpose in the past can still read its TimerUseExpFlag to determine whether or not the timer expired during that use. The values are: EXP_BIOS_FRB2 EXP_BIOS_POST EXP_OS_LOAD EXP_SMS_OS EXP_OEM Setting this object will NOT take effect on the Watchdog until the object SaHpiWatchdogRunning is set to true(1).\"",
"::=",
"{",
"hpiWatchdogEntry",
"7",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"OCTET STRING"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"Set of values seperated by a delimiter. For each value set, the corresponding Timer Use Expiration Flag will be CLEARED. Generally, a program should only clear the Timer Use Expiration Flag corresponding to its own TimerUse, so that other software, which may have used the timer for another purpose in the past can still read its TimerUseExpFlag to determine whether or not the timer expired during that use. The values are: EXP_BIOS_FRB2 EXP_BIOS_POST EXP_OS_LOAD EXP_SMS_OS EXP_OEM Setting this object will NOT take effect on the Watchdog until the object SaHpiWatchdogRunning is set to true(1)."
],
null,
null,
null,
null
]
}