During initialization, RMS does a demount to each drive it can access. However now that I think about this, there is a different error that comes back which RMS intercepts indicating there is no volume mounted. An error that is not reflected like this sense is. I recently worked on a similar problem, which turned out to be the drive somehow had been assigned as an autoloader for a particular scratch tape. Did the query you previously showed indicate the device was assigned category SCRATCH0? Do you have any tapes in this category?
Best Regards, Les Geer IBM z/VM and Linux Development >Yeah, I suppose doing a demount before mounting the tape probably >doesn't make any sense. > >First, I restarted the RMSMASTR machine. Here's what it said after the >PROFILE EXEC ran: > >FSMBBV3053I All DFSMS local APPC/VM resources initialized >FSMRMBLC==> Diag 254 is available >TAPE 4116 ATTACHED TO RMSMASTR 4116 >FSMBAC2006E Library I/O error; reason code = 3800, request identifier = >0, devic >e = 4116, library = >FSMBAC2019E Sense Data = >804004272030202364C443000040404040404034001213902004E82 >05D8F2011 >TAPE 4116 DETACHED BY RMSMASTR >FSMBBD2241W Device 4116 could not be initialized > >Then I tried to mount a tape from the DFSMS machine: > >dfsmsrm mount vol vm0000 >DGTUIR2026I DFSMS request 12 accepted for processing >Ready; T=0.01/0.01 15:26:16 > 15:26:17 * MSG FROM RMSMASTR: FSMBAD2006E Library I/O error; reason >code = > 3800, request identifier = 12, device = 4116, library = TLLIB01 > >The line about "Sense Data" make no "sense" to me... >
