Sun StorageTek Virtual Tape Control Software (VTCS)
 
Sun StorageTek VSM System
 

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

Applies to:

Symptoms

Message SLS5024E is received during VTCS initialization.
Message SLS6831I may also be issued regarding initialization.
If VT commands are issued before VTCS completes initialization, message SLS5022E will be issued.

SLS5024E Timeout on ECAM I/O to device nnnn

SLS6831I WAITING FOR VTSS NNNNNNNN TO COMPLETE INITIALIZATION

SLS5022E VT <command> COMMAND CAN NOT BE PROCESSED - VTCS HAS NOT INITIALIZED. REPLY IF COMMAND IS TO BE CANCELLED.

Cause

This timeout message is caused either by a path problem or possibly a problem with the VTSS.

Solution

Read the following explanation and steps that can be taken to troubleshoot, if needed.

The SLS5024E message indicates VTCS is waiting for ECAM I/O to complete for device nnnn within a one minute timer.  When the I/O does complete, the message will be automatically deleted.  If the SLS5024E message stays highlighted on the console, that may indicate a significant problem.  And VTCS will continue to wait for the I/O to complete.

Usually the SLS5024E message is preceded by MVS IOS messages indicating a path problem, but sometimes that is not the case and is actually an indication that the selected VTD device for the ECAM I/O is too busy to respond within the time limit.  VTCS selects any valid VTD device address not being used by this host to do ECAM I/O, however VTCS is unable to also validate whether the device is currently in use by another host.  Certain types of applications can tie up a VTD device so that it is unable to respond to an ECAM I/O request within the one minute timer.  Also, VTCS can use the same VTD device address to do multiple ECAM I/O requests, so it is possible to receive SLS5024E messages for the same VTD device address for each ECAM I/O request that does not get a response.

To troubleshoot this message, please do the following:

1. Check the HSC logs and SYSLOG to determine if any errors exist for the address(es) identified in the SLS5024E message(s).
2. If any IOSnnnn messages exist for the VTD address(es) in question, determine if the errors are limited to a single path.  If so, vary the affected path(s) offline.
3. If the errors appear to affect all paths, the MVS command Vary nnnn,OFFLINE,FORCE can be issued to attempt to bypass the device.
4. Once the problem has been corrected, the device can be brought back online.
• It should not be necessary to re-start HSC/VTCS once the errors have been corrected and the VTD addresses are properly online.
5. If the VTSS was taken offline, the VTCS command VT Vary VTSS(nnnnnnnn) ONline can be issued to bring the VTSS online.
6. If the I/O error(s) cannot be resolved, contact Oracle StorageTek support for assistance. 

There are commands to display MVS system configuration information about the affected drive and path which may be useful in troubleshooting this problem:

• D M=DEV(xxxx)  - where xxxx is the address of the device experiencing the I/O problem
• D M=CHP(yy)  - where yy is the channel path identifier from the previous command

Also, make certain there are no outstanding WTORs that could be affecting the drive or system.

If this was the result of a failure, or clean.

• Display VTD(s) to verify off-line or f-box.
• Vary off affected CHPid(s) offline, and back on-line to refresh the MVS mapping.

This solution has no attachment