Re: Synchronizing VTL VOLCAT and TMS
Thanks, I was hoping for a simpler way. But that, combined with CTTSYNC utility seems to have fixed the problem. I hope. Gadi -Original Message- From: IBM Mainframe Discussion List On Behalf Of Brian Fraser Sent: Tuesday, September 8, 2020 2:17 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Synchronizing VTL VOLCAT and TMS IDCAMS CREATE VOLENT(NAME(Vvolser) LOC(library) MTYPE(mediatype) LIBNAME(libname) UATTR(scratch/private) On Tue, 8 Sep 2020 at 17:15, Gadi Ben-Avi wrote: > Hi, > We have the following situation: > Virtual volumes exist in the VTL (TS7760) using the correct category > for a specific LPAR. > Some are in category 008F and some in 0082 The same volumes are > defined in the TMS (Control-M/Tape in this case). > The volumes are not defined in the VOLCAT. > How can I either: > Delete the volumes from the VTL. Attempting this resulted in a message > that said: > No volumes were deleted because the volumes in the range do not meet > one or more of the following criteria: > > The deletion can only be issued for an unused logical volume, which is > defined as a volume in the insert category that has not been mounted > by a host or a volume in the insert category that has had its > category, constructs, or attributes changed by a host. Certain volumes > can be moved back to the insert category by the host or through damaged token > recovery. > > Or > Do something so that the VOLCAT is updated correctly. > > Thanks > > Gadi > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Email secured by Check Point -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Synchronizing VTL VOLCAT and TMS
IDCAMS CREATE VOLENT(NAME(Vvolser) LOC(library) MTYPE(mediatype) LIBNAME(libname) UATTR(scratch/private) On Tue, 8 Sep 2020 at 17:15, Gadi Ben-Avi wrote: > Hi, > We have the following situation: > Virtual volumes exist in the VTL (TS7760) using the correct category for a > specific LPAR. > Some are in category 008F and some in 0082 > The same volumes are defined in the TMS (Control-M/Tape in this case). > The volumes are not defined in the VOLCAT. > How can I either: > Delete the volumes from the VTL. Attempting this resulted in a message > that said: > No volumes were deleted because the volumes in the range do not meet one > or more of the following criteria: > > The deletion can only be issued for an unused logical volume, which is > defined as a volume in the insert category that has not been mounted by a > host or a volume in the insert category that has had its category, > constructs, or attributes changed by a host. Certain volumes can be moved > back to the insert category by the host or through damaged token recovery. > > Or > Do something so that the VOLCAT is updated correctly. > > Thanks > > Gadi > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Synchronizing VTL VOLCAT and TMS
Hi, We have the following situation: Virtual volumes exist in the VTL (TS7760) using the correct category for a specific LPAR. Some are in category 008F and some in 0082 The same volumes are defined in the TMS (Control-M/Tape in this case). The volumes are not defined in the VOLCAT. How can I either: Delete the volumes from the VTL. Attempting this resulted in a message that said: No volumes were deleted because the volumes in the range do not meet one or more of the following criteria: The deletion can only be issued for an unused logical volume, which is defined as a volume in the insert category that has not been mounted by a host or a volume in the insert category that has had its category, constructs, or attributes changed by a host. Certain volumes can be moved back to the insert category by the host or through damaged token recovery. Or Do something so that the VOLCAT is updated correctly. Thanks Gadi -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
