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? Thanks in advance, Dave
