An entry in the adGenCSMMonitorSessionTable. An entry in this table is used to model a data collection interval that has specific levels of scope. Depending upon the capabilities of the particular CSM, only a limited number of Monitoring Sessions (table rows) may be active at any given time. Typically there can be many more rows defined in the table if they are not active. This will allow the administrator to store sessions when they are not needed but may be needed in the future. Step-wise Procedures to set up a Monitoring Session (1) The manager obtains a unique adGenCSMMonitorSessionId by reading the adGenCSMMonitorSessionIndexNext object. (2) Next, the manager creates a row in the Monitor Session Table. Each row is indexed by the adGenCSMMonigorSessionId obtained in step 1 of this procedure. The row can be created in this type by setting the adGenCSMMonitorSessionRowStatus to createAndWait(5). Row creation fails if: - A row already exists with the specified index. - Insufficient memory resources exist within the CSM. (3) The manager sets any column values, besides the rowStatus to specify the scope and duration of the monitor session. The adGenCSMMonitorSessionRowStatus can be monitored to determine if the row has valid parameters. When the rowStatus is notReady(3), one or more parameters are invalid for the scope level specified. When the rowStatus is notInService(2), all columns are valid and the row is ready to be made active(1). (4) The manager sets the adGenCSMMonitorSessionRowStatus object to active(1). This will initiate the monitoring session and it will continue until the maximum number of intervals, specified by adGenCSMMonitorSessionMaxIntervals, is reached. If adGenCSMMonitorSessionMaxIntervals is zero, the monitor session will continue to run until the manager sets the adGenCSMMonitorSessionRowStatus object to notInService(2) or destroy(6). If a power cycle/reset occurs, the monitoring session will begin again at the first interval upon restart of the CSM. If the maximum number of active monitoring sessions has already been reached, the setting of the adGenCSMMonitorSessionRowStatus object to active(1) will fail. *** It should be noted that data collected during a monitoring session is not preserved across protection switches at this time.