Description: This non-persistent variable allows a user to control the present page view of the 'logRecTable'.

When 'logViewPageSize' is set at any value smaller than 'logMaxSize', the 'logRecTable' may have multiple pages, depending upon how many log records are present in the log ('logCurrentSize'), and the viewing filter 'logViewSeverityFilter'.

This variable 'logViewPageControl' allows the SNMP user to retrieve any of these pages.

For the purpose of clarity in the description below, lets assume 'logCurrentSize' is 47, and 'logViewPageSize' is 10. With this example, there would be 5 viewable pages, identified as pages 1, 2, 3, 4, and 5. Pages 1 through 4 have 10 log records each, while page 5 has only 7 records.

Setting this variable to 1 causes the first view page to be retrieved when 'logRecTable' is next read by the SNMP user. That is records 1 through 10 would be retrieved.

Setting this variable to 2 causes the records 11 through 20 to be retrieved. Setting 'logViewPageControl' to 3 causes 21 through 30; 4 causes 31 through 40; and 5 causes 41 through 47 to be retrieved the next time 'logRecTable' is read.

The viewing of a different page becomes a two step operation; first this variable 'logViewPageControl' is set with a value then the 'logRecTable' is read.

The default value is 1. Allowable values are 1 through the value which represents the last page at any specific point in time that this variable is written. If the input value is larger than the value representing the last page, then the input is ignored (no error returned), and 'logViewPageControl' is set to the last page given the current system log and viewing filter criteria ('logViewFilter'). A input value of 0 is accepted (without error) to represent the first page. Thus a 1 is written.

If at any time the current view of the system log has changed (because of the dynamic nature of the system log), such that 'logViewPageControl' is too large, then this variable will be automatically set to a new value that represents the last page. Thus the only time a 'logRecTable' is retrieve empty, is because there are no records matching the view filter criteria, not because 'logViewPageControl' indicates an invalid page.

'logViewEvents' indicates the number of system events that would be displayable on all pages of the 'logRecTable' given the view filtering criteria specified by the current value of 'logViewSeverityFilter'. Examining 'logViewEvents' may assist in choosing how a user may want to change this variable 'logViewPageControl'.

The retrieval of the 'logRecTable' is also effected by the view sorting variables 'logViewMethod', 'logViewDirection', and 'logViewAge' which provide sorting criteria. (These determine the order of the the records.)

Also note, that the system log is a dynamic history of events. Records may be deleted automatically because of replacement rules (new events overwriting older events), or through human interaction via SNMP, or possible a platform's console or configuration port interface. With such a situation, a user may retrieve the next or previous page, and see some or all of the same log events that where presented earlier. Similarly, the user may completely overlook a record that shifts from a logical position on a particular page during one retrieval and has moved to a different page when the next retrieval occurs.

This variable is automatically given the value of 1 whenever any of the other viewing variables are modified ('logViewPageSize', and these identified below).

The retrieval of the 'logRecTable' is effected by the other viewing variables, which provide sorting and filtering controls. These other variables are: 'logViewSeverityFilter', 'logViewMethod', 'logViewDirection', 'logViewAge'.