Sun StorageTek Enterprise Library Software (ELS)
 
Sun StorageTek VSM System
 
Sun StorageTek Virtual Tape Control Software (VTCS)
 

PLA-Support>Sun Systems>TAPE>Library Software>SN-TP: MAINSW VTCS
 

Applies to:

Goal

How to drain a VTSS to zero.
How to migrate a VSM to zero.
How to empty the VTSS of VTVs.

Solution

To migrate a VTSS to zero:

1. Ensure tape allocations are directed to another VTSS if you have been specifically directing data to VTSS you want to quiesce.
If necessary, redirect allocations by changing TAPEREQ statements or by changing esoterics in JCL.

2. Display active processes:  D ACT DET VTSS(vtssname)
Either allow outstanding processes to complete before continuing or enter the VTCS CANCEL command to stop all active and queued processes as follows:

CANCEL ID(process-id)
-or-
CANCEL TYPE(ALL)

3. Enter an MVS VARY command to vary the VTDs offline:

For example:
   VARY 840-87F,OFFLINE
Varies 64 VTDs offline beginning with address 840.

4. Optionally, increase the number of RTDs used for migration.  If desired, enter the VTCS SET MIGOPT command to increase the value for maximum number of RTDs that can be used during migration to allow migration to run faster.

SET MIGOPT MAXMIG(n)

5. Migrate the VTSS to zero VTVs.  Note that when there are 0 VTVs in the buffer, the DBU can still be higher than 0%.

MIGRATE VTSS(vtssname) THRESHLD(0)

6. Run a VTCS AUDIT to verify the VTSS is migrated to zero.

AUDIT VTSS(vtssname)

7. Run VTV and MVC detail reports.

• VTVRPT
• MVCRPT DET

8. Review the VTV report output to ensure that all VTVs were migrated:

• Migrated VTVs show as M in the MIGR column.
• VTVs not migrated and still resident in the VTSS show up on the VTV report in the SIZE column as one of the following conditions:
• MOUNT - The VTV is in mounted state. Do the following:

• If the VTV is in mounted state and the VTV report shows that a copy of the VTV is already migrated to an MVC, then review the MVC report to determine if the MVC contains the most recent copy of the VTV by referencing the timestamps. If the most current copy of the VTV resides on an MVC, you do not need to migrated the VTV.
If a VTV is in Mounted status and it is not already on an MVC, then do either of the following:
• Use the MVS UNLOAD command to dismount the VTV.
• Use the MVS VARY OFFLINE command to vary offline the VTD where the VTV is mounted, which will also dismount the VTV.
Then either migrate the VTSS to zero again or migrate the specific VTV:   MIGRATE VTV(volser)

• FENCED - The VTV is fenced. If the VTV is in fenced state and the VTV report shows that a copy of the VTV is already migrated to an MVC, then review the MVC report to determine if the MVC contains the most recent copy of the VTV by referencing the timestamps.

If the most current copy of the VTV resides on an MVC, then unfence the VTV as follows:

1. Migrate the VTV and delete it from the VTSS:
     MIGRATE VTV(volser) DELETE(YES)
2. Recall the most recent VTV copy from the MVC:
     RECALL VTV(volser) VTSS(vtssname)
3. Audit the VTSS with the SWSADMIN utility:
    AUDIT VTSS(vtssname)
4. Reenter VTCS RECALL command to recall and unfence the VTV:
    RECALL VTV(volser) VTSS(vtssname)

If the VTV is in Fenced status and there is no good copy on an MVC, you do not need to migrate the VTV. When the VTSS is back online, do the following unfence the VTV:

1. Scratch the VTV in your TMS.
2. Update the HSC CDS to specify that the VTV is scratch.
3. Allow the VTV to be selected again by normal scratch mount processing.
4. When the VTV is naturally selected by VTCS, the VTV will be created as a new scratch volume and will now no longer show Fenced.

9. Vary RTDs offline:

V RTD(rtd-id or rtd-range) OFFLINE

10. Vary the VTSS offline:

V VTSS(vtssname) OFFLINE

11. Display the state of the VTSS:

Q VTSS(vtssname)
When the STATE column shows OFFLINE, the operation is complete.

12. Enter the MVS VARY command to vary VTD paths offline:

For example:
   VARY PATH(840,FE),OFFLINE
Varies CHPID FE path offline to device address 840.

For more information regarding the VTCS commands and utilities referenced above, see the ELS Command, Control Statement, and Utility Reference.  Instructions for downloading current maintenance are available in <Document 1016459.1>.

Use this procedure in the following situations:

• Maintenance to clean the VTSS.
• Maintenance to load new microcode in the VTSS.
• To swap out the VTSS.
• To remove the VTSS from service.

This solution has no attachment