Items we want to monitor for slCell

[riklempens]

As there are potentially to much items to retrieve (>10.000) we made a selection of the items we find valuable:

InfraSonar	Variable	Description
yes	slCellCount	Amount of storage elements in the cell table
yes	slCellStorageFreeCells	Amount of available (empty) storage cells in the library
yes	slCellStorageRestrictedFreeCells	Amount of available restricted (empty) storage cells in the library
no	slCellTable	Table of storage elements in the library
no	slCellEntry	Storage element
no	slCellIndex	Integer index into the storage cell table
yes	slCellElementID	Element ID or translated logical HLI address of the storage cell
no	slCellHostAccessible	Indication of host accessible status
yes	slCellContentStatus	Status of the cell (unknown, empty, readable, not_readable, cap_magazine_not_present, drive_not_present, drive_not_available)
no	slCellContentLabel	Label of the cartridge in the cell (zero length string if empty, '??????' if unreadable)
no	slCellContentType	Type of the cartridge in the cell (zero length string if empty) which is a text string based on enumerated domain and type values derived from the VOLSER label
yes	slCellGetRetryCount	Amount of get retries performed from this cell
yes	slCellPutRetryCount	Amount of put retries performed to this cell
no	slCellHostType	The type of cell (0=invalid/unknown cell, 1=storage slot, 2=tape drive, 3=customer access port or mail slot, 4=playground/system cell, 5=intransit/reserved or recovery cell, 6=pass thru port, 7=robotic cell)
no	slCellPhysicalAddressStr	Physical address string of storage cell
no	slCellLogicalAddressStr	Logical address string of storage cell
no	slCellPartition	Partition ID of storage cell
no	slCellPartitionType	Partition type of storage cell
no	slCellCapacityEnabled	Whether the storage cell is enabled (1) or disabled (0)
yes	slCellCapacityAllowed	The number of cells licensed for use.
yes	slCellCapacityUsed	The number of cells being used.

[joente]

Both the slTapeEntry and slCellEntry are huge tables. The current library prevents querying the top level without being able to skip nested OIDS. We need to find a solution to work with these huge data sets as the current option would result in time-outs and possible exceeding the max-rows as well.