Do not lose track of the fact that VSSLTAPE is an application/TMS interface, not-VTAPE-system code/TMS. You might be able to create a tape pool that includes the potential volumes in your VTAPE library. That is only the easy piece. If you look at the sample VSSLTAPE, you will see that it is not trivial. It was designed to be used by two very specific applications. Those applications intercept the I/O interrupts occurring on specific real tape drives and all OPEN and CLOSE macros and call VSSLTAPE as required, simply to get real tapes mounted. What you are asking is the complimentary action. You want something that monitors for VTAPE requests and handles them for the Hidro-Dynam/T environment. I doubt that Hidro has such exits.
Also, do not forget about the need for logical backup of the VTAPE library. If you use Hidro to do a physical backup while the library is closed, you will not be able to restore a single VTAPE, you will have to restore the entire library. You could, of course, create a second library, restore to it, then copy the tape in question to your real (pun intended) VTAPE library. Regards, Richard Schuh > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:ib...@listserv.uark.edu] On Behalf Of Phil Smith III > Sent: Friday, May 08, 2009 2:55 AM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: Virtual Software Systems Inc. VTAPE product > > "Shiminsky, Gary" wrote: > >We use the other VMBACKUP product - HiDRO which does have an > interface > >with Dynam/T/VM. HiDRO does a good job of backing up our CMS & SFS > >material except for Byte File System (BFS) directories in SFS. > > It's been a while, but I remember that DYNAM/T wasn't that > hard to interface with. It did have a nasty habit of losing > threads (per the then-DYNAM/T dev team), but hopefully that's > been fixed by now. > > ...phsiii >
