On Thursday, October 4, 2012 4:43:12 AM UTC-5, Michael Wood wrote: > Mike, I dont have a means to test each of these, but, working from memory > about the design and implementation in rmm.... - If the TCDB entries still > existed, you could simply add the NOEJECT operand to the DV commands - so > that no attempt is made to go to the library. However, since you have no TCDB > (and this is the reason the volumes dont go to scratch as well), you will > have to follow the guidelines from the G&R about situations when a > library/tcdb is not available..... See the CV FORCE operand description items > 2 & 3. - Issue RMM CV volser LOCATION(SHELF) FORCE or - RMM CV volser EJECT > FORCE or - Issue RMM CV volser LOCATION(SHELF) FORCE TYPE(PHYSICAL) See the > requirements in the book about authorization. (ie CONTROL and FORCE > authority) Once the volume is not known to be system managed by rmm, you can > use the DV volser FORCE commands to get rid of them from CDS. Mike Wood > ---------------------------------------------------------------------- For > IBM-MAIN subscribe / signoff / archive access instructions, send email to > lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Hello Mike all 3 CV cmds: Issue RMM CV volser LOCATION(SHELF) FORCE or - RMM CV volser EJECT FORCE or - Issue RMM CV volser LOCATION(SHELF) FORCE TYPE(PHYSICAL) Resulted in the same cc12 reason code 401 However DELETEVOLUME volser FORCE NOEJECT did in fact seem to work...I tried same on one of the volsers that was pending-release and it ended in cc0 and that vol no longer shows in my RMM Searchvolume results thank you!!! ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
