Sun StorageTek Enterprise Library Software (ELS)
 
Sun StorageTek Virtual Tape Control Software (VTCS)
 
StorageTek Virtual Storage Manager System 6 (VSM6)
 

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

In this Document

Goal

Solution

Created from <SR 3-10810757970>

Applies to:

Goal

What do the statuses ECAM ERROR and ECAM INIT ERROR in Display VTD output indicate?
What does the status ECAM I/O ERROR in the Display VTD output indicate?
What does the status ECAM INIT ERROR in the Display VTD output indicate?
 

Solution

Both of the following statuses indicate that an ECAM I/O occurred for the specified VTD:

  ECAM I/O ERROR
  ECAM INIT ERROR

The difference between the two is with the timing of the ECAM I/O error.  When the ECAM I/O occurs during initialization of the VTSS (such as during HSC/VTCS startup or when using the Vary VTSS command), then the status will be ECAM INIT ERROR (ECAM ERROR during VTCS INITialization).

For all other ECAM I/O errors, the status ECAM I/O ERROR will be displayed for the VTD that incurred the ECAM I/O error.

When the ECAM I/O error happens during VTSS initialization, the SLS6698I ECAM I/O ERROR ON VTD dddd is likely to be followed by message SLS6675E.  There are a numbers of possible causes for this type of ECAM I/O error including:

• VTCS Configuration mismatches
• VTSS subsystem name mismatches
• HCD/switch misconfiguration
• Cabling errors
• VTSS disconnected or powered off, etc 

The Return Code and other info in the SLS6675E message text will give additional about the nature of the error.  For example:

If the ECAM I/O error occurs after successful VTSS initialization, then that normally indicates a good configuration (or at least an initial good configuration). 

When the ECAM I/O occurs after VTSS initialization, the problem is normally related to connectivity.  Check cables, devices, CHPid/paths, switches, the VTSS itself, etc. 

In either case (ECAM I/O ERROR and ECAM INIT ERROR), the initial ECAM I/O error will be reported (in HSCLOG/SYSLOG) at the time of the error.  This knowledge document is related to the ECAM I/O ERROR and ECAM INIT ERROR statuses in the Display VTD output.  That status is only displayed with the user/customer issues the Display VTD command.  The ECAM ERROR status will remain as long as that VTD has not yet been used for subsequent ECAM I/O.

VTCS will use and reuse the same VTD as long as there are no errors with it.  If there is connectivity between VTCS and a VTSS, there is at least one usable path for at least one VTD associated with that VTSS.  VTCS will only attempt to reuse a previously failed VTD if there are no other VTDs available.

So in my example above, ECAM I/O errors occurred for VTDs 1000, 1001, and 1002.  VTCS will go down the list of VTDs and use the next one (such as 1003) for ECAM I/O.  The Display VTD output will show ECAM INIT ERROR for 1000-1002; for example:

 The initial ECAM I/O may have occurred much earlier, and the cause of the error may have been corrected.  The ECAM INIT ERROR status won't prevent the VTD from being used for host I/O (as long as the VTD is online to MVS).  But that VTD won't be used for ECAM I/O.  Nothing really needs to be done here; the ECAM INIT ERROR status is not a current problem.

The ECAM INIT ERROR status will be cleared the next time the VTSS is varied offline/online (or when HSC/VTCS is restarted) - assuming that the VTDs paths are OK and the VTSS is OK and available.

This solution has no attachment