Filter
Top Products
This window allows you to manage the HPSS global configuration record. Only one such record is
permitted per HPSS installation. To open the window, on the Health and Status window select the
Configure menu, and from there the Global menu item.
Field Descriptions
System Name. An ASCII text string representing the name for this HPSS system.
Root Core Server. The name of the Core Server which manages the root fileset (“/”) in the HPSS
namespace.
Advice - The root Core Server should be selected with care. Once it is chosen it cannot be changed as
long as the chosen server exists. If the root Core Server must be changed, the current root Core Server
will have to be deleted before SSM will allow another root Core Server to be selected.
Default Class of Service. The name of the default Class of Service (COS). Core Servers will store new
files in this COS when the HPSS client does not specify a COS or provide hints on the creation request.
This default can be overridden by each storage subsystem.
Advice - If the COS chosen for the Default Class of Service is deleted, be sure to change the Default
Class of Service before deleting the COS.
If disk is used as the Default COS, it should be defined so that a large range of files sizes can be handled For this
reason it may be reasonable to set the default COS to a tape COS.
Default Logging Policy. The name of the default logging policy. This policy will be used for all servers
that do not have a specific log policy configured.
Advice - Care should be taken to choose a descriptive name (such as “DEFAULT LOG POLICY”) which
is unlikely to conflict with the name of a real HPSS server. Once this new policy is created, it may be
selected as the Default Log Policy.
Alternately, you may skip this step until after one or more server specific log policies are created. Then a
Default Log Policy can be chosen from one of the server specific log policies.
Metadata Space Warning Threshold. Provides a default value for the metadata warning threshold.
When the space used in any DB2 tablespace exceeds this percentage, the Core Server will issue a
periodic warning message. This value can be overridden for each storage class on a storage subsystem
basis (see Section 4.2.1: Subsystems List Window on page 74 for more information).
Metadata Space Critical Threshold. Provides a default value for the metadata critical threshold. When
the space used in any DB2 tablespace exceeds this percentage, the Core Server will issue a periodic
critical alarm. This value can be overridden for each storage class on a storage subsystem basis (see
Section 4.2.1: Subsystems List Window on page 74 for more information).
Metadata Space Monitor Interval. The Core Server will check metadata usage statistics at the
indicated interval, specified in seconds. The minimum value for this field is 1800 seconds (30 minutes).
A value of 0 will turn off metadata space monitoring. This field may be overridden on the Storage
Subsystem configuration.
DB Log Monitor Interval. The Core Server will check consistency of Database Logs and Backup Logs
at the indicated interval, specified in seconds. The logs are consistent if both primary and backup log
directories exist and contain log files with the same names. The minimum value for this field is 300
seconds (5 minutes). A value of 0 will turn off DB Log monitoring. This field may be overridden on the
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 73