|
|
Description:
|
dbCreateTransaction OBJECT-TYPE
SYNTAX INTEGER {normal(1), transaction(2), verify(3), done(6)}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"<Definition>This object provides transaction control for deviceconfiguration. The transaction mode changes the behavior of theagent to force buffering of database objects until all relateddatabase objects have been modified. In the normal mode, SEToperations to any database object shall either be stored in adevice's database immediately with no regard to whether otherchanges will be made or be rejected (as defined in the devicespecific
Information Profile). In the transaction mode, SEToperations to any database object shall be buffered until a verifystate performs a consistency check. When the consistency checkcompletes, the device automatically transitions to the done statewhere a normal or transaction command may be issued.
A database object is a user provided piece of setup information(or it may be defined in an information profile) that is necessaryfor the proper operation of a device. It is static in nature in
that the agent would never change it without direction from themanagement station. For example, a parameter that defines adefault mode of operation would be a database object. A parameterthat indicates the current state of the device would not be a
database object.
The states and commands are defined as:
NORMAL: SET operations behave as normal SETs and shall have animmediate effect on the value of any database objects used by thedevice if none of the objects contained in the operation requirethe use of the transaction mode (as defined in the device-specificInformation Profile). A SET operation containing any databaseobject that requires the use of transaction mode shall result in agenErr. This is the default state of this object.
The only command that may be written to dbCreateTransaction whilein this state is TRANSACTION. Any other values written to thisobject in this state shall result in an error response of'badValue'.
TRANSACTION: A SET operation of one or more database objects thatuse the same community name as used in the request for theTRANSACTION state are buffered by the agent device for laterconsistency checks and a normal response is returned. A SET
operation of one or more database objects using differentcommunity names shall result in a genErr with the index set tozero. A SET operation without a community name field (e.g., anSTMP operation) shall be buffered by the agent device for laterconsistency checks and a normal response is returned. Standard
SYNTAX checking shall take place at the time of the SET operation.
A transaction may consist of multiple SET operations over multipleframes.
A SET operation for one or more non-database objects shall beprocessed as normal even if it uses another community name, exceptfor this (i.e., the dbCreateTransaction) object.
A SET operation containing both database and non-database objectsshall be processed in full according to these two rules. Thus, ifit contains the same community name as used in the request for theTRANSACTION state, the non-database objects shall be storedimmediately while the database objects shall be buffered. If it
uses a different community name, the entire request will berejected and a genErr with an index of zero shall be returned.
GET operations on any object shall return the values of the datastored in the controller and shall ignore any values contained inthe buffer.
Any valid community name may read this (dbCreateTransaction)
object when in this state, but only the community name used tocommand the object to the transaction mode and the administratorcommunity name can set this object. A set from any other communityname shall result in a genErr with an index of zero. The onlycommands that can be written to dbCreateTransaction while in this
state are VERIFY and NORMAL. A VERIFY command will change thestate to VERIFY. If a NORMAL command is received, all buffereddata is discarded and the state is returned to NORMAL. Any othervalues written to this object when in this state shall result inan error response of 'badValue'.
VERIFY: Specific database objects are checked for consistency.
When consistency checks are complete the device will automaticallyadvance to the DONE state.
The state of dbCreateTransaction cannot be changed when in theVERIFY state. Any values written to this object in this stateshall result in an error response of 'badValue'.
The consistency check analyzes certain critical objects 'incontext' and treats them as an interrelated whole rather than
separate non-related data items. The consistency check rules arenot defined in this standard. They are device and implementationspecific. Where applicable, the consistency check rules aredefined in application specific object definition standards. A
specific implementation may add additional checks beyond thosedefined in the standards.
A SET operation containing any database objects while in the VERIFYstate shall result in a genErr with the index set to zero.
DONE: This state is entered automatically once consistency checkshave completed in the VERIFY mode. The value of dbVerifyStatusand dbVerifyError indicate whether the consistency check found anyerrors.
A SET operation containing any database objects while in the DONE stateshall result in a genErr with the index set to zero.
Any valid community name may read this (dbCreateTransaction)
object when in this state, but only the community name used tocommand the object to the transaction mode and the administratorcommunity name can set this object. A set from any other communityname shall result in a genErr with an index of zero. The onlycommands that can be written to dbCreateTransaction while in this
state are NORMAL and TRANSACTION. Any other values written tothis object in this state shall result in an error response of'badValue'.
If a NORMAL command is issued and dbVerifyStatus indicatesdoneWithNoError, the buffered data is transferred to the devicememory and the state is returned to NORMAL. If a NORMAL command
is issued and dbVerifyStatus indicates something other thandoneWithNoError then the buffered data is discarded and the state
is returned to NORMAL.
If a TRANSACTION command is issued, regardless of dbVerifyStatus,
no action takes place (the buffered data is not changed) and theTRANSACTION state is re-entered.
COMMANDED STATE (9)
transaction verify normal done
CURRENTSTATE
normal transaction (1) normal (2) normal (2) normal (2)
transaction transaction (2) verify (3) normal (4) transaction (2)
verify (7) verify (2) verify(2) verify (2) verify (2)
done (8) transaction (5) done(2) normal (6) done (2)
Operational procedures and error responses:
(1) Once a copy of all database objects is placed in abuffer the state is changed to transaction and errorresponse indicates noError. If the operation fails, thestate remains the same and error response indicates genErr.
(2) No action takes place, the state remains the same, butresponse indicates badValue.
(3) The state is changed to verify, a consistency check isstarted, and response indicates noError. Once the
consistency check is completed, the state automaticallychanges to done.
(4). The buffered copy of all database objects isdiscarded, the state is changed to normal, and responseindicates noError.
(5) The buffered copy of all database objects is notchanged or reloaded, the state is changed to transaction,
and response indicates noError.
(6) If dbVerifyStatus indicates doneWithNoError, then thecopy of all database objects is transferred to memory, thestate is changed to normal and response indicates noError.
If dbVerifyStatus indicates doneWithError then the buffereddata is discarded, the state is changed to NORMAL, andresponse indicates noError.
(7) The state will automatically change to done when theconsistency check completes.
(8) dbVerifyStatus and dbVerifyError are only valid in thisstate.
(9) All SET operations on this (dbCreateTransaction) parametershall be made using a protocol that uses a community name, orequivalent field (e.g., SNMP).
<DescriptiveName>Transaction.mode:code
<DataConceptType>Data Element"
DEFVAL {normal}
|
|
|
|
|
|
