XEROX-SERVICE-MONITORING-MIB Table View

A table of general counters and capabilities for ease of use
of the XCMI Service Monitoring MIB on this host system.
          
Usage:  The ONLY valid row in the 'xcmSvcMonGeneralTable'
SHALL have an 'xcmSvcMonGeneralIndex' of one ('1').

A table of the external job queues supported and (possibly)
active, for some 'physical', 'logical', or 'logicalAndPhysical'
device on this host system.
          
          
Usage:  These externally visible job queues MAY actually be
configured on external print/file servers (remote) or on the
managed system itself (local).
          
Usage:  For example, a 'logical printer' might support one or
more external (network) job queues.
          
Note:   The 'xcmJobGenBasicTable' in the XCMI Job Monitoring MIB
(indexed by 'hrDeviceIndex' from the IETF Host Resources MIB)
displays the unordered union of all jobs present in the (one or
more) 'local' queues supported by each 'physical', 'logical', or
'logicalAndPhysical' device on this host system.
          
Note:   The XCMI Comms Engine MIB is indexed by devices of type
'CPU', while the 'xcmSvcMonQueueTable' is indexed by application
devices of type 'printer', 'fax', etc.
          
Usage:  Throughout this specification, the term 'stable storage'
refers to storage which is reliable over long durations (years)
and is NOT destroyed by host system reboot (eg, battery-backed
DRAM is 'stable storage' - while simple DRAM is NOT 'stable
storage').  Examples of valid 'stable storage' include:  NVRAM,
hard disk, EEPROM, etc.
          
Usage:  Conforming implementations SHALL preserve active
queue table objects across management agent power cycles,
and SHALL implement one of the following two methods:
1)  The agent SHALL store queue table objects directly in
    'stable storage'; or
2)  The agent SHALL automatically checkpoint all active queue
    table objects to 'stable storage' with reasonable frequency
    (either due to a write to some queue table object, or upon
    expiration of a product-specific timeout).
          
Usage:  Conforming implementations MAY (optionally) support
one of the following two 'checkpoint protocols':
1)  A client sends a 'Set' of 'xcmSvcMonQueueRowStatus' to
    'active(1)', to request that a 'checkpoint' be performed;
2a) An agent which supports 'rapid checkpoint',
    completes the checkpoint to 'stable storage', and
    sends a 'SetResponse' with 'noError(0)';
    <or>
2b) An agent which supports 'delayed checkpoint',
    changes 'xcmSvcMonQueueRowStatus' to 'notInService(2)',
    sends a 'SetResponse' with 'noError(0)',
    completes the checkpoint to 'stable storage', and
    changes 'xcmSvcMonQueueRowStatus' back to 'active(1)'.

A table which augments 'xcmSvcMonQueueTable', with dynamic
queue routing (forwarding), state, conditions, fault info,
create date, lifetime jobs, and last connect date and jobs.
          
Usage:  Conforming implementations SHALL preserve active
queue table objects across management agent power cycles,
and SHALL implement one of the following two methods:
1)  The agent SHALL store queue table objects directly in
    'stable storage'; or
2)  The agent SHALL automatically checkpoint all active queue
    table objects to 'stable storage' with reasonable frequency
    (either due to a write to some queue table object, or upon
    expiration of a product-specific timeout).

A table of the system and/or end-user services supported and
(possibly) ready on this host system, and (possibly) associated
with one or more 'physical', 'logical', or 'logicalAndPhysical'
devices on this host system presenting job services and one or
more external devices (for security, accounting, etc), attached
to this host system.

A 'sparse' table containing service detail information for
installed and (possibly) active services on this host system,
augmenting the basic entries in the 'xcmSvcMonServiceTable'
of the XCMI Service Monitoring MIB.
          
Usage:  UNLIKE the 'xcmGenOptionTable' in the XCMI General MIB
(which is a unique exception), this table of 'dictionary-based'
service details is used with DIRECT create/update operations.

A table containing service management requests for control
of system and/or end-user services on this host system.