On Wed, 4 Feb 2015 21:33:37 -0800 retired mainframer <[email protected]> wrote:
:>Clipping implies you changed the volser. Are the components still in the :>catalog pointing to the old volser. If so, you may want to uncatalog (but :>not delete) them before trying to recatalog them. Tried that. This volume is a test case for a procedure and the data is not a big deal. >From my research, it would appear that I would need to take the manual approach of first zapping the VTOC to change the VVDS dsname and then zap the data within to show the updated volser. I wou;d have expected that there would be a simple approach to rename the VVDS and recatalog all vsam items. :>> -----Original Message----- :>> From: IBM Mainframe Discussion List [mailto:[email protected]] On :>> Behalf Of Binyamin Dissen :>> Sent: Wednesday, February 04, 2015 7:53 PM :>> To: [email protected] :>> Subject: So I CLIPed the volume that has a data and index component of a :>standard :>> VSAM cluster :>> :>> I have been trying all sorts of DEFINE RECATALOG without success. What is :>the :>> secret answer? -- Binyamin Dissen <[email protected]> http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
