Renaming context-based resource definitions
How CICSĀ® Configuration Manager renames a context-based resource definition depends upon whether the resource definition name changes, or if only the ResGroup name changes. In either case, the rename affects only the source and target ResGroups. Other ResGroups are unaffected by the rename, and may still refer to the source resource definition that was renamed. These are the processing rules for renaming context-based resource definitions:
- If the resource definition name changes, then a resource definition is
created or updated for the target resource name and type. This is then associated
with the target ResGroup. If the target ResGroup does not already exist, it
is created.
The source resource definition is removed from the source ResGroup. If the resource definition belongs only to this ResGroup, then the resource definition is deleted, thereby eliminating orphaned resource definitions. The source ResGroup is never deleted, even if the removal of the resource definition results in an empty ResGroup.
If the source resource belongs to other ResGroups, then the resource definition is not deleted. This ensures that those other ResGroups are unaffected by the rename.
- If the resource definition name does not change and only the target ResGroup
changes, then the resource definition itself is not created, deleted, or changed.
It is associated with the target ResGroup, and the association with the source
ResGroup is removed. The source ResGroup is never deleted, even if the removal
of the resource definition results in an empty ResGroup.
If the source resource definition belongs to other ResGroups, these ResGroups are unaffected by the rename.