The standard resource property Type_version stores the RT_Version property of a resource's type. This property does not appear in the RTR file. The system administrator edits it using the following command:
scrgadm -c -j <resource> -y Type_version=<new version> |
Its tunability is derived from:
The current version of the resource type
The #$upgrade_from directives in the RTR file
Use the following tunability values in the #$upgrade_from directives:
If there are no restrictions on when the resource can be upgraded; the resource can be fully online.
If the new resource type version's Update, Stop, Monitor_check, and Postnet_stop methods are known to be compatible with older resource type version's starting methods (Prenet_stop and Start), and if the new resource type version's Fini method is known to be compatible with the Init method of older versions. This scenario requires only that the resource monitor program be stopped before the upgrade
If the new resource type version's Update, Stop, Monitor_check, or Postnet_stop methods are known not to be compatible with older resource type version's starting methods (Prenet_stop and Start) but are known to be compatible with the Init method of older versions, the resource must be offline when the type upgrade is applied to it.
Similar to When_offline; however, it imposes the stronger condition that the resource be disabled.
If the new resource type version's Fini method is known not to be compatible with the Init method of older versions; this requires the existing resource group to be switched to the unmanaged state prior to upgrading the resource.
If resources are not upgradable to the new resource type version; only new resources of the new version can be created.
The tunability of At_creation means that the resource type developer can prohibit the migration of an existing resource to the new type. In this case, the system administrator must delete and recreate the resource. This is equivalent to declaring that the resource's version can only be set at creation time.