Conference 49.910::kav30

152.0. "KAV30 and RZ25L don't mix - but the RZ25 and RZ26L work fine" by ZYDECO::BODA (Realtime Expertise Center) Tue Jun 06 1995 23:27

Hi,

I was recently asked to do some testing of the RZ25L and RZ26L disks with
VAXELN V4.5.  Marco Olobardi was also asking about disks on the KAV30.
I was in the neighborhood, so I did some tests.  The KAV30 firmware was 
successful in seeing the RZ25 and RZ26L disks in separate tests:

>>> s 20080050

 KAV30 ROM utility to show devices on the SCSI bus & set the SCSI ID.
   This KAV30's SCSI ID = 7.

   NOTES:  A. Only SCSI TARGETS are shown in the table below.
           B. Invalid fields are replaced with asterisks, (*).
           C. If the table below seems incorrect, check that
                each SCSI ID (0-7) is used by only ONE device.

   ID  DEVICE_TYPE        PRODUCT_ID        VENDOR    REV     B1 B2 B3 B7
   --  -----------------  ----------------  --------  ----    -- -- -- --
    0  00:direct access   RZ25     (C) DEC  DEC       0900    00 02 02 90
    1  ..(open).........  ................  ........  ....    .. .. .. ..
    2  ..(open).........  ................  ........  ....    .. .. .. ..
    3  ..(open).........  ................  ........  ....    .. .. .. ..

>>> s 20080050

 KAV30 ROM utility to show devices on the SCSI bus & set the SCSI ID.
   This KAV30's SCSI ID = 7.

   NOTES:  A. Only SCSI TARGETS are shown in the table below.
           B. Invalid fields are replaced with asterisks, (*).
           C. If the table below seems incorrect, check that
                each SCSI ID (0-7) is used by only ONE device.

   ID  DEVICE_TYPE        PRODUCT_ID        VENDOR    REV     B1 B2 B3 B7
   --  -----------------  ----------------  --------  ----    -- -- -- --
    0  00:direct access   RZ26L    (C) DEC  DEC       440C    00 02 02 16
    1  ..(open).........  ................  ........  ....    .. .. .. ..
    2  ..(open).........  ................  ........  ....    .. .. .. ..
    3  ..(open).........  ................  ........  ....    .. .. .. ..
    4  ..(open).........  ................  ........  ....    .. .. .. ..
    5  ..(open).........  ................  ........  ....    .. .. .. ..
    6  ..(open).........  ................  ........  ....    .. .. .. ..
    7  =======[ This KAV30; (no INQUIRE is done to this SCSI ID).]=======

Subsequently, the KAV30 KRDRIVER worked fine at runtime with these two disks.  

However, the KAV30 ROM utility to show SCSI devices does not work with the
RZ25L.  This particular RZ25L had a SCSI ID = 4.  The utility hangs at ID=4 when
it tried to get the information about the RZ25L.  Of course, at runtime,
the KRDRIVER can't access the disk either.  This same RZ25L is visible on a 
4000-90 via ">>>SHOW DEV" as well as at runtime using VAXELN V4.5's PKCDRIVER 
(and under VMS too).

Deb Skaltsis of VAXELN engineering asked if I would bring this to the attention
of KAV30 engineering as she would like to confirm VAXELN support for the
RZ25L and RZ26L since their predecessors (RZ25 and RZ26) are no longer available.

If you have a RZ25L readily available, can you confirm this behavior?
If you confirm this, how should I submit this as a possible KAV30 SCSI bug?

Thanks,

Alan

    Hi,
    
    we don't have any RZ25L's around, so we can neither confirm nor deny
    the problem ...
    
    If VAXELN want's to see support for RZ25L on KAV30 they should contact
    the product mgr. Roland Svennberg [EICMFG::RSVENNBERG] and make  a
    request for that (thats the only way we will get a RZ25L for
    testing...).
    
    Best regards,
    
    Thomas