[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference cookie::mru

Title:MRU Internal Bug Reports
Moderator:COOKIE::STMARTIN
Created:Wed Sep 20 1995
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:346
Total number of notes:1175

339.0. "TL800 Failure on MRU T1.2." by SUBSYS::TRAN (Straight <Left> Hitter..) Wed May 07 1997 12:19

    
    Running TL800 on T1.2 (5) on VMS 7.1..
    
    1. MRU fails when device reports UNIT ATTENTION, 28-00 (Media may have
       changed).
    
    2. Xrobot hangs when use FIND with Wildcard, search hangs, then MRU
       hangs.
    
    T.
T.RTitleUserPersonal
Name
DateLines
339.1Find is known and fixed here. Unit Attention is an error.NABETH::alanDr. File System's Home for Wayward Inodes.Wed May 07 1997 15:2430
	re: Find.

	Fixed that months ago...  As I recall it was a stupid error
	on the part of person that did the GUI find implementation.
	I would pound his head against the wall for it, but my head
	still hurts from when I did that yesterday for another stupid
	bug...(*)  Look through the closed problems for the full description.
	I think you can get it not to hang by defining MRU_WAIT to a
	small value.

	re: Wildcards.

	Don't support them.  I'll mention this to our technical writer.
	Bear in mind that the MRD Find support doesn't use Send Volume
	Tag/Request Volume Element Address, which is the part that does
	support wildcards.  When the TL820 firmware is fixed, we'll
	think about it.

	re: Unit Attention.

	Okay.  If the robot is going to report back errors when we do
	commands it seems incumbant upon us to pass the error back
	to the user.  MRU has a simple error reporting mechanism;
	It work or It Didn't Work.  Thus, we take a very narrow view
	of something which works; no error AT ALL.  For us, the Unit
	Attention was an error.  The IOD on the TL820 does the same
	thing.

	(*) This is a joke I made yesterday by pounding my own head
	against the wall.  You had to be there...
339.2Need new version, I guess..SUBSYS::TRANStraight <Left> Hitter..Thu May 08 1997 08:2412
    
    Thanks, Alan..
    
    I'll get new T1.2 and try it.
    
    RE: Unit Attenion.
    This is a SEP SCSI requirement for robot to report 6-28-00 when
    external media changes has occured, ie. insert magazine. It's OK
    if MRU will report any failure, just want consistency here. As a
    user I can deal with that.
    
    T.
339.3SSDEVO::ROLLOWDr. File System's Home for Wayward Inodes.Thu May 08 1997 08:454
	Unless you want to pick up the current build piece by piece
	there isn't a more current OpenVMS kit.  If you don't mind
	a piece-meal build, let me know via mail and we can work
	something out.
339.4SSDEVO::ROLLOWDr. File System's Home for Wayward Inodes.Thu May 08 1997 08:508
	re: Check Condition

	We are consistent.  If an underlying SCSI command completes in
	such a way that we feel compelled to do a Request Sense, we
	treat that command as having failed.  If a Digital UNIX I/O
	control fails with EIO set, we do Request Sense.  If an OpenVMS
	$QIO fails with SS$DRVERR or the GK driver tells us there was
	a SCSI error we do a Request Sense.