This object specifies the status of the subscriber session
job. The following columns must be valid before activating a
subscriber session job:
- csubJobStorage
- csubJobType
- csubJobControl
However, these objects specify a default value. Thus, it is
possible to use create-and-go semantics without setting any
additional columns.
An implementation must allow the EMS/NMS to modify any column
when this column is 'active', including columns defined in
tables that have a one-to-one or sparse dependent relationship
on this table.
This object specifies the status of the subscriber session
job. The following columns must be valid before activating a
subscriber session job:
- csubJobStorage
- csubJobType
- csubJobControl
However, these objects specify a default value. Thus, it is
possible to use create-and-go semantics without setting any
additional columns.
An implementation must allow the EMS/NMS to modify any column
when this column is 'active', including columns defined in
tables that have a one-to-one or sparse dependent relationship
on this table.
csubJobStatus OBJECT-TYPE SYNTAX RowStatus ACCESS read-write STATUS mandatory DESCRIPTION "This object specifies the status of the subscriber session job. The following columns must be valid before activating a subscriber session job: - csubJobStorage - csubJobType - csubJobControl However, these objects specify a default value. Thus, it is possible to use create-and-go semantics without setting any additional columns. An implementation must allow the EMS/NMS to modify any column when this column is 'active', including columns defined in tables that have a one-to-one or sparse dependent relationship on this table." ::= { csubJobEntry 2 }
csubJobStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object specifies the status of the subscriber session job. The following columns must be valid before activating a subscriber session job: - csubJobStorage - csubJobType - csubJobControl However, these objects specify a default value. Thus, it is possible to use create-and-go semantics without setting any additional columns. An implementation must allow the EMS/NMS to modify any column when this column is 'active', including columns defined in tables that have a one-to-one or sparse dependent relationship on this table." ::= { csubJobEntry 2 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.786.1.3.7.1.1 | csubJobId | 0 | 0 | This object indicates an arbitrary, positive integer-value uniquely identifying the subscriber session job. |
| 1.3.6.1.4.1.9.9.786.1.3.7.1.3 | csubJobStorage | 0 | 0 | This object specifies what happens to the subscriber session job upon restart. |
| 1.3.6.1.4.1.9.9.786.1.3.7.1.4 | csubJobType | 0 | 0 | This object specifies the type of subscriber session job: 'noop' This type of job does nothing and simply serves as a convenient d… |
| 1.3.6.1.4.1.9.9.786.1.3.7.1.5 | csubJobControl | 0 | 0 | This object specifies an action relating to the subscriber session job: 'noop' This action does nothing. 'start' If the correspondin… |
| 1.3.6.1.4.1.9.9.786.1.3.7.1.6 | csubJobState | 0 | 0 | This object indicates the current state of the subscriber session job: 'idle' This state indicates that the system has not execute… |
| 1.3.6.1.4.1.9.9.786.1.3.7.1.7 | csubJobStartedTime | 0 | 0 | This object indicates the value of sysUpTime when the system started executing the subscriber session job. This value will be '0… |
| 1.3.6.1.4.1.9.9.786.1.3.7.1.8 | csubJobFinishedTime | 0 | 0 | This object indicates the value of sysUpTime when the system finished executing the subscriber session job, for whatever reason. … |
| 1.3.6.1.4.1.9.9.786.1.3.7.1.9 | csubJobFinishedReason | 0 | 0 | This object indicates the reason why the system finished executing the subscriber session job: 'invalid' Indicates that the corres… |