After producing the list of VAULTRETRIEVE tapes, move them to COURIERRETRIEVE instead of ONSITERETRIEVE. When the courier returns with the tapes, move them to ONSITERETREIVE.
Laura -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU] On Behalf Of Matt Simpson Sent: Friday, October 25, 2002 9:17 AM To: [EMAIL PROTECTED] Subject: Re: drm operator scripts At 9:37 AM -0500 10/25/02, Mark Stapleton wrote: > UPDATE STG <stgpool_name> REUSEDELAY=<number_of_days> > >Tape volumes in the storage pool will now go to PENDING status when >they are moved to ONSITERETRIEVE status. You won't be able to check >them in as scratch tapes until the reusedelay period of time expires. That's not exactly the problem I'm trying to solve. I want to check them in as scratch tapes. I just don't want them to disappear out of the database before that happens. Example. We generate a list of all tapes in VAULTRETRIEVE status, and give that to a human and tell him to bring all those tapes back from the vault. We move all the tapes on the list to ONSITERETRIEVE status. Human brings tapes back from the vault. We load them into the bulk entry door and issue the CHECKIN command to check them in as scratch. All is OK if human retrieves all the right tapes. But if one doesn't get retrieved for some reason, there is no longer any record that the tape exists and isn't where it belongs. I'd like to have it left in the database in some status, VAULTRETRIEVE or COURIERRETRIEVE or anything that would indicate that it exists and needs to be returned to the library. -- Matt Simpson -- OS/390 Support 219 McVey Hall -- (859) 257-2900 x300 University Of Kentucky, Lexington, KY 40506 <mailto:msimpson@;uky.edu> mainframe -- An obsolete device still used by thousands of obsolete companies serving billions of obsolete customers and making huge obsolete profits for their obsolete shareholders. And this year's run twice as fast as last year's.
