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... Dave -----Original Message----- From: Les Geer (607-429-3580) <[EMAIL PROTECTED]> Reply-To: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> To: IBMVM@LISTSERV.UARK.EDU Subject: DFSMSRM Errors in RMSMASTR Date: Tue, 11 Dec 2007 17:09:57 -0500 Well, you queried the drive, and the response was no tape mounted. Next you issued a demount to the drive which received the I/O error, probably because there was nothing to demount. Try mounting a tape then see if the demount is successful. BTW, if you order latest DFSMS service, which removes the need by RMS to attach the drive to issue the query drive command, there is corresponding CP service required. Best Regards, Les Geer IBM z/VM and Linux Development >Yesterday I was getting pretty excited because I actually got VM talking >to our tape library. I was able to see the volumes that were assigned to >me and assign them to a scratch category. I even mounted a tape, invoked >DDR and dumped a MOD3 and a MOD9 to the tape. Then, later that day, I >started having problems. Now when I start up the RMSMASTR machine, I get >errors about not being able to talk to the drive. I've tried varying off >and on the chpid, path and device address, but that didn't seem to help. >The IBM technician said that the drive looks fine. >This morning I tried going through the DFSMS/VM Customization manual and >testing the RMSMASTR. Here's what I'm getting: > >dfsmsrm q lib dev 4116 >RMSMASTR: FSMEIF1211I DFSMS RM QUERY LIBRARY with NOWAIT received from >user DFSM >S, request identifier = 15 >DGTUIR2026I DFSMS request 15 accepted for processing >Ready; T=0.01/0.01 12:17:18 >RMSMASTR: TAPE 4116 ATTACHED TO RMSMASTR 4116 >RMSMASTR: TAPE 4116 DETACHED BY RMSMASTR > 12:17:18 * MSG FROM RMSMASTR: FSMBCI2200I Device 4116: Device Type >= 3592, > Library Name = TLLIB01, VLABEL = N/A, Mounted Category = NONE, >Assigned Category = SCRATCH0 >dfsmsrm demount rdev 4116 >RMSMASTR: FSMEIF1211I DFSMS RM DEMOUNT with NOWAIT received from user >DFSMS, request identifier = 18 >DGTUIR2026I DFSMS request 18 accepted for processing >Ready; T=0.01/0.01 12:17:47 >RMSMASTR: TAPE 4116 ATTACHED TO RMSMASTR 4116 >RMSMASTR: TAPE 4116 DETACHED BY RMSMASTR >RMSMASTR: FSMBAC2006E Library I/O error; reason code = 3800, request >identifier= 18, device = 4116, library = TLLIB01 >RMSMASTR: FSMBAC2019E Sense Data = >804004272030202364C443000040404040404034001213902004E8205D8F2011 > 12:17:47 * MSG FROM RMSMASTR: FSMBAD2006E Library I/O error; reason >code = 3800, request identifier = 18, device = 4116, library = TLLIB01 > >Has anyone seen this before or have any insight as to what might be >going on? Dave Keeton Systems Programmer Enterprise Systems Oregon State Data Center (503) 373-0832 email: [EMAIL PROTECTED]
