Owner manual

T0634 -- OSM Console Tools -- Start menu shortcuts and default home pages for easy access
to the OSM Service Connection and OSM Event Viewer (browser-based OSM applications
that are not installed on the system console).
Caution: Only system consoles provided by HP are supported for use with the OSM
applications. To preserve the integrity of software running on system consoles,
do not install any software applications on your system consoles other than the
preinstalled software. Compromising the software on a system console might
leave you unable to communicate with the server when it is down.
What's New and Changed for This Version
The OSM Service Connection (now part of T0682AAA) has been updated for G06.25 to add
support for:
New Virtual Tape devices.
Actions and attributes under the System object in the OSM Service Connection to support
both manual and automatic data collection for failed system resources. Automatic data
collection is now enabled and disabled through Enable Automatic Data Collection and
Disable Automatic Data Collection actions rather than through a parameter in the
OSMCONF file. The Collect Diagnostic Data action performs manual data collection.
The volume in which the diagnostic data is collected (both automatic and manual) is set
through the Set Data Collection Volume action rather than through a parameter in
OSMCONF file. The collected (PAK) files remain in that volume for 30 days before
being automatically deleted (the default of 30 days can be changed through the
RETAINDAYS parameter in your OSMCONF file).
Data Collection attributes under the System object indicate the specified volume and
whether automatic data collection is enabled or disabled.
The OSM Service Connection has a new method for indicating subcomponent problems
for parent objects in the tree pane.
Instead of displaying a Subcomponent State attribute in the Attributes tab of the details
pane, a yellow arrow is displayed over a system, group, module, or parent object in the
tree pane to indicate that one or more subcomponents require service or operational
intervention.
Starting with G06.25, all OSM server-based components, including the OSM Service