Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

How the management classes are used

&pagelevel(4)&pagelevel

A management class can be defined with the HSMS statement CREATE-MANAGEMENT-CLASS. The attribute values can be displayed with the HSMS statement SHOW-MANAGEMENT-CLASS-ATTRIBUTES and changed with MODIFY-MANAGEMENT-CLASS-ATTRIBUTES.
Nonprivileged users are only allowed to use the HSMS statement SHOW-MANAGEMENT-CLASS-ATTRIBUTES.

With SM pubsets, management classes can only be used if HSMS is started on the master host.

To control a backup with management classes, the HSMS administrator must specify the name of a management class in the HSMS statement BACKUP-FILES; for a migration the administrator must specify the name of a management class in the HSMS statement MIGRATE-FILES; for a version backup the administrator must specify the name of management class in the HSMS statement BACKUP-FILE-VERSIONS. Only the objects that have been assigned the name of that management class are selected for processing. This procedure readily allows a subsystem to be defined. By subsystem, we mean a group of objects, all of which HSMS processes in the same way.

The operands of the HSMS statement that correspond to an attribute must be set to the value *STD. This ensures that the operand values are taken from the management class.
At the appropriate time, the HSMS administrator executes the requisite HSMS statements. The operand values of these HSMS statements are then replaced by the corresponding attributes of type 1 or 2 of the respective management class.

Note that management classes created in HSMS V11.0A and lower do not contain attributes for version backups. The files assigned to such management classes are processed by BACKUP-FILE-VERSIONS as if they have NUM-OF-BACKUP-VERS equal to 0, i. e. the files are skipped if they have never been saved within the version backup archive or, in case the file has been saved within the archive, 0 is written as NUM-OF-BACKUP-VERS into the directory. It is therefore recommended to provide management classes with version attributes if they are used in the context of version backup (see MODIFY-MANAGEMENT-CLASS).

Management classes created or modified in HSMS V12.0A still can be used in lower HSMS versions without any restriction for current behavior of the lower HSMS versions.