The STORESAFE command is used to configure and monitor the StoreSafe feature.
Syntax
<disk site name>
The <site ID> is the user-specified disk site name. The disk site name can be up to 17 alphanumeric characters in length.
Explanation
STORESAFE + PK <number> SITENAME <site ID>
This command assigns the <site ID> to PK <number>.
STORESAFE − PK <number>
This command removes the disk site name from PK <number> only if the command does not create a StoreSafe alert condition.
STORESAFE − PK <number> FORCE
This command forces the removal of the disk site name from PK <number>. After executing the command, if the mirrored set to which PK <number> belongs has other members at the same disk site name, but none of them are accessible, the remaining members are marked as being overridden.
STORESAFE REMOVE <disk site name> FROM PK <number>
The REMOVE variant is used to eliminate the requirement that members must be present at a disk site name in a situation where none of the members at that disk site name are online to the system. For example, consider a mirrored set consisting of PK 100 and PK 200, with PK 100 having the disk site name PRIMARYSITE and PK 200 having the disk site name BACKUPSITE. If PK 200 is decommitted out of the set due to an irrecoverable I/O error, all that remains is PK 100, un-mirrored, at PRIMARYSITE, and it is in a StoreSafe alert. If the site administrator wishes to remove the requirement that there be a mirror of PK 100 at BACKUPSITE, it is not possible to do so with the STORESAFE − PK 200 command, since PK 200 is no longer an online mirror. The REMOVE variant is designed for situations such as this where the subject disk is no longer online to the system. If a volume was in a StoreSafe alert because there were no accessible members at the specified disk site name, use of this command resolves the StoreSafe alert.
STORESAFE REMOVE <disk site name>
This form of the REMOVE variant is used to eliminate the requirement that members be present at the specified disk site name for all StoreSafe volumes currently on the system. An operator acknowledgement is needed to ensure that the FROM PK xxx part of the command was not inadvertently omitted.
STORESAFE + ENFORCE
This command requests initiation of system-wide enforcement of StoreSafe alerts. System-wide enforcement also requires that a valid feature key be installed in the system keys file. When system-wide enforcement is in effect, the loss of the last online copy of data at a disk site name causes a StoreSafe alert.
STORESAFE − ENFORCE
This command requests termination of system-wide enforcement of StoreSafe alerts. If the last online copy of data at a disk site name is lost when system-wide enforcement is turned off, the alert is automatically overridden. Informational messages are provided at the ODT to reflect the automatic StoreSafe override, but I/O processing is not interrupted.
STORESAFE + OVERRIDE SITENAME <disk site name>
This command provides a way to globally override any existing StoreSafe alerts for the specified disk site name and to prevent future such alerts from occurring. If a volume is in a StoreSafe alert because it does not have an online member at the specified disk site name, overriding the alert causes I/O activity to the volume to resume without the MCP maintaining in-sync members at that disk site name.
STORESAFE − OVERRIDE SITENAME <disk site name>
This command provides a way to discontinue a global site name override request. This enables future StoreSafe alerts to take place as the result of the loss of the last member at the specified disk site name.
| Note: | Out-of-sync volumes are unaffected by this command. Simply discontinuing a global override does not cause a volume to be in-sync. |
Examples
Example 1
The following message displays after installing the STORESAFE feature, but before using it:
STORESAFE ALERTS NOT BEING ENFORCED OVERRIDDEN SITES ARE: (NONE) NO STORESAFE DISKS FOUND
System-wide enforcement of STORESAFE alerts is not in effect because the operator has not entered a STORESAFE+ENFORCE command. There are no STORESAFE named disks on the system.
Example 2
STORESAFE ALERTS BEING ENFORCED OVERRIDDEN SITES ARE: (NONE) PK STATUS FAMILY MEMBER SITE NAME STORESAFE STATUS 200B M DISK # 1 MV +RUNNING 100B M DISK # 1 TR +RUNNING
System-wide enforcement of STORESAFE alerts is in effect.
PK 100 and PK 200 are a mirrored set with PK 100 located at disk site name TR and PK 200 located at disk site name MV. The mirrored set is functioning normally.
Example 3
STORESAFE ALERTS NOT BEING ENFORCED OVERRIDDEN SITES ARE: (NONE) PK STATUS FAMILY MEMBER SITE NAME STORESAFE STATUS 200B M DISK # 1 MV -RUNNING 100B M DISK # 1 TR -RUNNING
System-wide enforcement of STORESAFE alerts is not in effect because the operator has not entered a STORESAFE+ENFORCE command.
PK 100 and PK 200 are a mirrored set with PK 100 located at disk site name TR and PK 200 located at disk site name MV. The mirrored set is functioning normally.
Example 4
STORESAFE ALERTS BEING ENFORCED OVERRIDDEN SITES ARE: (NONE) PK STATUS FAMILY MEMBER SITE NAME STORESAFE STATUS 200B M DISK # 1 MV +ALERT(AUDITING) 100B M DISK # 1 TR +SUSPENDED
System-wide enforcement of STORESAFE alerts is in effect. PK 100 and PK 200 are a mirrored set with PK 100 located at disk site name TR and PK 200 located at disk site name MV. The volume is in a STORESAFE alert because PK 200 was decommitted to auditing.
Example 5
STORESAFE ALERTS BEING ENFORCED OVERRIDDEN SITES ARE: MV PK STATUS FAMILY MEMBER SITE NAME STORESAFE STATUS 200B M DISK # 1 MV(O) +OVERRIDDEN(AUDITING) 100B M DISK # 1 TR +RUNNING
System-wide enforcement of STORESAFE alerts is in effect. PK 100 and PK 200 are a mirrored set with PK 100 located at disk site name TR and PK 200 located at disk site name MV.
A STORESAFE alert for this volume has been globally overridden after PK 200 was decommitted to auditing. I/O activity is proceeding to the volume. PK 200 is not synchronized.
Example 6
STORESAFE ALERTS BEING ENFORCED OVERRIDDEN SITES ARE: (NONE) PK STATUS FAMILY MEMBER SITE NAME STORESAFE STATUS B DISK # 1 MV +ALERT(MISSING) 100B DISK # 1 TR +SUSPENDED
System-wide enforcement of STORESAFE alerts is in effect. PK 100 and PK 200 are a mirrored set with PK 100 located at disk site name TR and PK 200 located at disk site name MV. The volume is in a STORESAFE alert because PK 200 was decommitted out of the set.
Example 7
STORESAFE ALERTS BEING ENFORCED OVERRIDDEN SITES ARE: (NONE) PK STATUS FAMILY MEMBER SITE NAME STORESAFE STATUS 300B M DISK # 1 MV +ALERT(PENDING) 100B M DISK # 1 TR +SUSPENDED
System-wide enforcement of STORESAFE alerts is in effect. PK 100 and PK 200 are a mirrored set with PK 100 located at disk site name TR and PK 200 located at disk site name MV.
The volume is in a STORESAFE alert because PK 200 was decommitted out of the set. PK 300 is being created at disk site name MV to resolve the alert, but has not yet completed.
Example 8
Following is an example of the response that you receive if you enter a STORESAFE - ENFORCE command when the mirrored set is in the state described by the preceding example.
STORESAFE ALERTS NOT BEING ENFORCED OVERRIDDEN SITES ARE: (NONE) PK STATUS FAMILY MEMBER SITE NAME STORESAFE STATUS 300B M DISK # 1 MV -OVERRIDDEN(PENDING) 100B M DISK # 1 TR -RUNNING
Example 9
STORESAFE ALERTS BEING ENFORCED OVERRIDDEN SITES ARE: (NONE) PK STATUS FAMILY MEMBER SITE NAME STORESAFE STATUS 200B M DISK # 1 MV +SUSPENDED(AUDITING) 300B M DISK # 1 MV +RUNNING 100B M DISK # 1 TR +RUNNING
System-wide enforcement of STORESAFE alerts is in effect. PK 100, PK 200, and PK 300 are a mirrored set with PK 100 located at disk site name TR and PK 200 and 300 located at disk site name MV.
Since there is still an online copy of the data at MV on PK 300, I/O activity is proceeding to the volume even though PK 200 was decommitted to auditing.
Example 10
Starting from the situation in the preceding example, PK 300 is now decommitted to auditing and is not synchronized. This causes a STORESAFE alert.
STORESAFE ALERTS BEING ENFORCED OVERRIDDEN SITES ARE: (NONE) PK STATUS FAMILY MEMBER SITE NAME STORESAFE STATUS 200B M DISK # 1 MV +ALERT(AUDITING) 300B M DISK # 1 MV +ALERT(AUDITING) 100B M DISK # 1 TR +SUSPENDED
Example 11
Starting from the situation in the preceding example, if you respond to the STORESAFE_ALERT waiting entry for disk site name MV with an AX IGNORE PK 100 command, the response is as follows.
STORESAFE ALERTS BEING ENFORCED OVERRIDDEN SITES ARE: (NONE) PK STATUS FAMILY MEMBER SITE NAME STORESAFE STATUS 200B M DISK # 1 MV +OVERRIDDEN(AUDITING) 300B M DISK # 1 MV +OVERRIDDEN(AUDITING) 100B M DISK # 1 TR +RUNNING
Example 12
Starting from the situation in Example 10, if you turn off system-wide enforcement of STORESAFE alerts with a STORESAFE-ENFORCE command, the response is as follows.
STORESAFE ALERTS NOT BEING ENFORCED OVERRIDDEN SITES ARE: (NONE) PK STATUS FAMILY MEMBER SITE NAME STORESAFE STATUS 200B M DISK # 1 MV -OVERRIDDEN(AUDITING) 300B M DISK # 1 MV -OVERRIDDEN(AUDITING) 100B M DISK # 1 TR -RUNNING
Example 13
Starting from the situation in the preceding example, both PK 200 and PK 300 have their audits applied and they both come back online.
STORESAFE ALERTS NOT BEING ENFORCED OVERRIDDEN SITES ARE: (NONE) PK STATUS FAMILY MEMBER SITE NAME STORESAFE STATUS 200B M DISK # 1 MV -RUNNING 300B M DISK # 1 MV -RUNNING 100B M DISK # 1 TR -RUNNING
Example 14
Continuing with the preceding example, PK 100 proceeds even though it is not ready. Since there is no system-wide enforcement of STORESAFE alerts, the alert is automatically overridden.
STORESAFE ALERTS NOT BEING ENFORCED OVERRIDDEN SITES ARE: (NONE) PK STATUS FAMILY MEMBER SITE NAME STORESAFE STATUS 200B M DISK # 1 MV -RUNNING 300B M DISK # 1 MV -RUNNING 100B M DISK # 1 TR -OVERRIDDEN(AUDITING)
Example 15
STORESAFE ALERTS BEING ENFORCED OVERRIDDEN SITES ARE: (NONE) PK STATUS FAMILY MEMBER SITE NAME STORESAFE STATUS 200B M DISK # 1 MV +SUSPENDED(AUDITING) B M DISK # 1 RS +ALERT(MISSING) 100B M DISK # 1 TR +SUSPENDED
System-wide enforcement of STORESAFE alerts is in effect.
PK 100, PK 200, and PK 300 are a mirrored set, with PK 100 located at disk site name TR, PK 200 at disk site name MV, and PK 300 located at disk site name RS.
PK 200 proceeds though it is not ready, causing an alert. You can override the alert with an AX IGNORE PK 100 command and I/O activity resumes.
PK 300 is decommitted out of the set, causing a new alert. I/O activity is suspended again.
Example 16
Continuing with Example 15, the operator responds with a STORESAFE REMOVE SITENAME RS FROM PK 100 command. This command resolves the alert because a copy at RV is no longer required. I/O activity resumes with the data at MV being out-of-sync.
STORESAFE ALERTS BEING ENFORCED OVERRIDDEN SITES ARE: (NONE) PK STATUS FAMILY MEMBER SITE NAME STORESAFE STATUS 200B M DISK # 1 MV +OVERRIDDEN(AUDITING) 100B M DISK # 1 TR +RUNNING
Example 17
STORESAFE ALERTS BEING ENFORCED OVERRIDDEN SITES ARE: (NONE) PK STATUS FAMILY MEMBER SITE NAME STORESAFE STATUS 200B M DISK # 1 MV -OVERRIDDEN(AUDITING 100B M DISK # 1 TR -RUNNING
System-wide enforcement of STORESAFE alerts is in effect. PK 100 and PK 200 are a mirrored set with PK 100 located at disk site name TR and PK 200 located at disk site name MV. The mirrored set is a critical family.
PK 200 proceeds even though it is not ready. There is no alert because STORESAFE handling for critical disks is bypassed (note the minus (−) signs).
Example 18
STORESAFE ALERTS BEING ENFORCED OVERRIDDEN SITES ARE: (NONE) PK STATUS FAMILY MEMBER SITE NAME STORESAFE STATUS 100B M DISK # 1 TR +RUNNING 200B M DISK # 1 +SUSPENDED(AUDITING)
System-wide enforcement of STORESAFE alerts is in effect.
PK 100 and PK 200 are a mirrored set with PK 100 located at disk site name TR; PK 200 is not STORESAFE named. PK 200 proceeds even though it is not ready. There is no alert because members that are not STORESAFE-named have no effect on STORESAFE handling.
Example 19
Continuing with the preceding example, PK 100 is decommitted out of the set. This causes a STORESAFE alert because there is a requirement for a copy of the data at disk site name TR.
STORESAFE ALERTS BEING ENFORCED OVERRIDDEN SITES ARE: (NONE) PK STATUS FAMILY MEMBER SITE NAME STORESAFE STATUS B M DISK # 1 TR +ALERT(MISSING) 200B M DISK # 1 +SUSPENDED(AUDITING)
Example 20
Following is an example of a display that includes multiple families, with multiple family members and different volume compositions.
STORESAFE ALERTS BEING ENFORCED OVERRIDDEN SITES ARE: (NONE) PK STATUS FAMILY MEMBER SITE NAME STORESAFE STATUS 100B M DISK # 1 MV +RUNNING 200B M DISK # 1 RS +RUNNING 300B M DISK # 1 TR +RUNNING 101C M DISK # 2 +RUNNING 201C M DISK # 2 MV +RUNNING 301C M DISK # 2 TR +RUNNING 102C M DISK # 3 MV +RUNNING 202C M DISK # 3 RS +RUNNING 303B PMDB # 1 TR +RUNNING 104C M PMDB # 2 MV +RUNNING 204C M PMDB # 2 RS +RUNNING 304C M PMDB # 2 TR +RUNNING 105B M ZETA # 1 MV +SUSPENDED 205B M ZETA # 1 RS +SUSPENDED 305B M ZETA # 1 TR +ALERT(AUDITING)
Considerations for Use
-
If you use the STORESAFE command to assign a disk site name to a member of the halt/load family or to another system-critical disk (for example, CATALOG, OVERLAY, JOBS, or LOG), the command is rejected with the following message:
NOT ALLOWED FOR CRITICAL UNIT
-
If you use the STORESAFE command to remove the disk site name when other members in the mirrored set to which the designated disk belongs have the same disk site name as the designated disk, and none of the other members are online mirrors, the command is rejected with the following message:
SITENAME NOT REMOVED. A NEW ALERT WOULD HAVE RESULTED. USE 'STORESAFE-PK # FORCE' TO DO THE REMOVAL, OVERRIDING ANY RESULTING ALERT.
Use the STORESAFE− PK <number> FORCE command to unconditionally remove the disk site name from the STORESAFE named pack.
-
If you use the STORESAFE command to assign a disk site name to a mirror that is being created or is having its mirror audit applied, the command is rejected with the following message:
STORESAFE COMMAND NOT ALLOWED-VOLUME IS IN USE
Reenter the STORESAFE command after completion of the MIRROR CREATE command or after audits have been applied.
-
If you use the STORESAFE command to name a member of a mirrored set that contains a member that has been marked for import using the MIRROR MARK command, the command is rejected with the following message:
STORESAFE COMMAND NOT ALLOWED-MIRRORED SET IS MARKED FOR IMPORT
Use the MIRROR MARK − PK <number> command to unmark the marked member.
-
If you use the STORESAFE REMOVE <disk site name> FROM PK <number> command when the system has visibility to a volume member at the specified disk site name, the command is rejected with the following message:
'STORESAFE REMOVE' NOT APPLICABLE TO ONLINE MEMBERS. USE 'STORESAFE-PK #' INSTEAD
Use the STORESAFE − PK <number> command instead.
