VTV Migrates and Recalls time out - SLS6684I with ECAM ERROR CC=5 RC=112

Asset ID:	1-72-1016751.1
Update Date:	2017-09-29
Keywords:

Solution Type Problem Resolution Sure

Solution 1016751.1 : VTV Migrates and Recalls time out - SLS6684I with ECAM ERROR CC=5 RC=112

Applies to:

Sun StorageTek Virtual Tape Control Software (VTCS) - Version 6.2 and later
Sun StorageTek Host Software Component (HSC) - Version 6.2 and later
Sun StorageTek VSM System - Version 4 and later
Sun StorageTek Enterprise Library Software (ELS) - Version 7.0 and later
Sun StorageTek VSM5 System
IBM z/OS on System z

Symptoms

MVC gets mounted but the VTV does not migrate.
Migration fails.
VTCS does not recognize the MVC has been mounted.
MVC gets mounted but the VTV does not recall.
MVC mount times out.
VTVs aren't being recalled.
Error messages received.

SLS6628E RTD rtd_ddd ON VTSS vtss_name FAILED TO MOUNT MVC volser
IEF234E K dddd,volser,PVT,VTSS1 ,SWSRDERR
SLS6667I REQUEST PURGED:MIGRATE MVC:volser VTV:volser MVC COULD NOT BE MOUNTED
SLS6685I RTD rtd_ddd MOUNT OF mvc_volser TIMED OUT
SLS6684I RTD rtd_ddd ON VTSS VTSS1 RETURNED ECAM ERROR CC=5 RC=112

Additional Information
RTDs show online.
HSC Display DRives indicates the MVC is mounted.
HSC Display Volume shows the volume is mounted on the correct RTD.
VT D RTD shows 'mount in process' with an asterisk next to the MVC.

Changes

Added a VTSS and/or new RTDs to an existing HSC/VTCS configuration.

Cause

This problem would generally occur during an initial install or when RTDs are being added or moved.

HSC was mounting the MVC on the RTD but the cables were not connected correctly between RTD and the VTSS. Therefore, the RTD was unable to tell the VTSS that the MVC was mounted and ready for use. The MVC just sat on the drive waiting to be used.

The following is an example from VT D RTD output which shows mount in process:

RTD   STATUS       MOUNT    ALLOC   HOST  VTSS

05A0  MIGRATE VTV  304000*  304000  TECH  VTSS1

The asterisk * indicates the mount is in progress and waiting for completion.

If the MVC does not mount, the following are known reasons for the RC=112:

An MVC is in use on another RTD.
An outstanding message is on the console.
A PTP is blocked due to an LSM in path offline.
A drive targeting the problem or a bad cable may exist in an LSM.
An LSM door is open.
The HSC COMMPATH is CDS rather than LMU or VTAM.

Solution

If the MVC did mount but was not recognized by HSC or VTCS as mounted, please have the field engineer review the hardware cable/datapath between RTD and VTSS. The field engineer can do a path validate from the VTSS to the RTD. The path validate should return the serial number of the RTD which can then be cross-checked against the serial number on the physical drive. If the two do not match, they are not cabled correctly. The serial number of the physical drive can be obtained from an HSC drive display. For details, please review <Document 1020161.1>.

If the MVC did not mount, review the possible causes listed in the 'Cause' section above.

Attachments

This solution has no attachment