U41117-J-Z125-7-76
175
GXCC
Function bar
“DELETE” button:
Appears only if a line is selected and the selected LVG has not yet been made known
to the system. This is typically the case if you have just created an LVG and have not
yet selected “Distribute and Activate”. Not to be confused with the “Delete LVGs”
function (for details see “Input areas”
➟
“To Be Deleted”).
Deletes the selected LVG.
An LVG entry can only be removed with “Delete” if the configuration has not yet been
activated with “Distribute and Activate”. “Delete” is consequently not offered for groups
that have been activated in the system, but “To Be Deleted” instead (an explanation is
provided below).
Input areas
To Be Deleted
You use this button to change the setting of “NO” (= default = LVG is not to be deleted)
to “YES” (= LVG is to be deleted). This enables an LVG to be deleted which has already
been made known to the system with “Distribute and Activate”.
To permit this function to be used a few conditions must be met:
–
The LVG concerned may not be linked to any PVG.
–
No LVs may be contained in the LVG.
If the condition “no LVs in LVG” is not satisfied the request to delete the LVG is
rejected with a corresponding error message. This condition is checked twice,
once when you click on “OK” in this window and once when “Distribute and
Activate” is used. In both cases the action is rejected.
The condition “LVG may not be linked to PVG” does not lead to the action being
rejected if it is not met. but an attempt is made to perform an unlink automati-
cally. If this proves unsuccessful this leads to the LVG being marked as
“intended for deletion”.
While PVs still exist which contain a reference to the LVG to be deleted, the
action will be rejected. This case can occur if, for example, you have assigned
LVs from the LVG to be deleted to another LVG using “Change Volume Group”.
Until these LVs have been saved again under the new LVG, they are still entered
in the PLM data maintenance system with their previous LVG name.
If an LVG is marked for deletion and if this configuration data has been activated
in the system, no further actions (add LV, create new link) at all are permitted on
this LVG. If a “Distribute and Activate” is performed again at any time, the
condition is automatically checked again. If it is then satisfied, this LVG is
deleted once and for all. These procedures are fully automatic; the user need
i
Summary of Contents for CentricStor V3.1D
Page 1: ...Edition July 2007 CentricStor V3 1D User Guide...
Page 22: ...Eine Dokuschablone von Frank Flachenecker by f f 1992...
Page 60: ...Eine Dokuschablone von Frank Flachenecker by f f 1992...
Page 236: ...Eine Dokuschablone von Frank Flachenecker by f f 1992...
Page 311: ...U41117 J Z125 7 76 311 Global Status History diagrams Example for V3 1D...
Page 321: ...U41117 J Z125 7 76 321 Global Status History diagrams 4 Open history file...
Page 322: ...322 U41117 J Z125 7 76 History diagrams Global Status 5 Confirm you wish to open it...
Page 324: ...Eine Dokuschablone von Frank Flachenecker by f f 1992...
Page 544: ...Eine Dokuschablone von Frank Flachenecker by f f 1992...
Page 546: ...Eine Dokuschablone von Frank Flachenecker by f f 1992...
