Message SLS6684I Reports Error code CC=08 RC=120 and VTSS is at Capacity

Asset ID:	1-72-1017197.1
Update Date:	2018-04-02
Keywords:

Solution Type Problem Resolution Sure

Solution 1017197.1 : Message SLS6684I Reports Error code CC=08 RC=120 and VTSS is at Capacity

Applies to:

Sun StorageTek Virtual Tape Control Software (VTCS) - Version 6.2 and later
Sun StorageTek VSM System - Version 3.0 to 5C [Release 3.0 to 5.0]
Sun StorageTek Enterprise Library Software (ELS) - Version 7.0 and later
IBM z/OS on System z

Symptoms

VTSS buffer is at capacity.
VTSS DBU is at 100% full.
VSM box is full.
Intervention required messages on VTDs.
VTV mounts are pending.

Some of the messages that may be issued are:

SLS6684I RTD <rtd> ON VTSS <vtss_name> RETURNED ECAM ERROR CC=8 RC=120
SLS6695E VTSS STKVSM01 IS FULL
SLS5079E MOUNT OF <vtv_volser> ON <vtd> - FAILED (12) - MVC:<mvc_volser> VTSS <vtss_name> HAS REACHED ITS DATA CAPACITY
SLS6659I VTSS STKVSM01 SIM:0010100000008FE072B0000900009E1042000E8400003E4005104E00F2000000
IOS003A xxxx INTERVENTION REQUIRED, READY THE DRIVE

Cause

This occurs when the VTSS is out of back-end capacity. A similar problem can occur if the VTSS reaches the maximum number possible for resident VTVs.

Solution

Since there are multiple situations that can cause the VTSS to fill up, use the following to troubleshoot and resolve this problem:

1. Halt initiators. This will prevent new work from allocating to the box while it is full.

2. Verify that the ACS is not disconnected and that there are no messages from HSC indicating a problem with the LMU. If this is occurring, then MVC mounts will be timing out (ECAM Error CC=5 RC=112) and MVCs will be in LOST status. The ACS or LMU problem will need to be resolved.

3. Check for messages indicating migration failures. If messages are found, use the text of the message to investigate the cause of the failure. Detailed message explanations are in the ELS Messages and Codes Guide. Possible messages are:

For VTCS 6.1 and lower:

SLS6700E MIGRATION FAILED STORAGE CLASS:cccccc ACS:xx VTSS:vtss_name REASON:reason_for_failure

For VTCS 6.2 and higher:

Multi-line message:
SLS6860I ADDITIONAL INFORMATION:

Which should be preceded by one of the following:

SLS6853E MIGRATION FAILED STORAGE CLASS: SSS ACS: AA VTSS: TTT - MVCPOOL PPP IS NOT DEFINED
SLS6854E MIGRATION FAILED STORAGE CLASS: SSS ACS: AA VTSS: TTT - NO MVCS FOUND FOR SPECIFIED MEDIA
SLS6855E MIGRATION FAILED STORAGE CLASS: SSS ACS: AA VTSS: TTT - NO MVCS FOUND FOR SPECIFIED MEDIA/SC/ACS
SLS6856E MIGRATION FAILED STORAGE CLASS: SSS ACS: AA VTSS: TTT - NO USABLE MVCS FOUND FOR SPECIFIED MEDIA/SC/ACS
SLS6857E MIGRATION FAILED STORAGE CLASS: SSS ACS: AA VTSS: TTT - NO RTDS FOR REQUESTED MEDIA AND ACS
SLS6858E MIGRATION FAILED STORAGE CLASS: SSS ACS: AA VTSS: TTT - ALL RTDS FOR REQUESTED MEDIA AND ACS ARE OFFLINE

4. Verify RTDs are online to the VTSS using VTCS command D RTD. If RTDs are discovered in a state other than online, investigate the cause and work to resolve the issue.

5. Verify the MVC pool has empty (FREE) MVCs that can be used for migration by issuing VTCS command D MVCP. It may also be useful to run a MVCRPT or MVCPLRPT and check for any MVCs that should be usable but are not because they have bad statuses.

6. Verify which host is performing auto-migration by issuing VTCS command D MIGR DET.

7. Verify the host indicated as currently performing auto-migration (see previous step) is actually migrating VTVs from the VTSS in question. When a VTV is migrated, message SLS6681I is issued.

8. Verify migrate tasks are active. Issue VTCS commands D ACT DET and D Q DET. a few times over about a 5 minute time span. A task at the top of the list that isn't doing anything may have a much older task ID than most of the other listed tasks. If there is a hung task that is holding a resource needed for migration, can use VTCS command CAN ID(task_id) or can cancel by a specific task type (CAN T(task_type) or CAN T(ALL).)

9. As a last resort, HSC may need to be cycled on one or more hosts. Start with the host that is indicated to be auto-migrating.

Instructions to locate current documentation are in <Document 1014318.1>.

Attachments

This solution has no attachment