xcmGenClientDataRowStatus 1.3.6.1.4.1.253.8.51.11.2.1.2

This object manages the row status of this conceptual row in the 'xcmGenClientDataTable'. Usage: Conforming implementations which support static rows SHALL support 'active' and 'notInService' writes to this 'xcmGenClientDataRowStatus' row status object; and SHALL clear the 'xcmGenClientDataGroup' bit in 'xcmGenBaseGroupCreateSupport' in the 'xcmGenBaseTable'. Usage: Conforming implementations which support dynamic rows SHALL support 'createAndGo' and 'destroy' writes to this 'xcmGenClientDataRowStatus' row status object; and SHALL set the 'xcmGenClientDataGroup' bit in 'xcmGenBaseGroupCreateSupport' in the 'xcmGenBaseTable'. Usage: Conforming implementations NEED NOT support dynamic row creation (via 'createAndGo(4)') nor dynamic row deletion (via 'destroy(6)'). Usage: Conforming implementations MAY support a single, static conceptual row, but SHALL allocate that row with an 'xcmGenClientDataIndex' value of one ('1'). Usage: Conforming management stations, when they first create or activate rows in this table, SHALL set 'xcmGenClientDataRowStatus' to 'active(1)' (for static rows) or 'createAndGo(4)' (for dynamic rows), 'xcmGenClientDataRequestID' (to a suitable client global ID), 'xcmGenClientDataProductID' (to a suitable client product ID), 'xcmGenClientDataLength' (to a suitable client data length) SIMULTANEOUSLY (in the same SNMP Set-Request PDU). Usage: Conforming management agents SHALL NOT accept sets to 'xcmGenClientDataRequestID', 'xcmGenClientDataProductID', or 'xcmGenClientDataLength' AFTER row creation (these objects are 'write-once'). Usage: To explicitly release this conceptual row, the client data owner SHALL set 'xcmGenClientDataRowStatus' to 'notInService(2)' (for static rows) or 'destroy(6)' (for dynamic rows). Usage: See section 3.4 'Secure Modes of Operation' and section 3.5 'Secure SNMP Get/Set Requests' in XCMI Security TC, for details of secure modes of access to this row status object.