DASD - non SMS - volser change - VSAM or Catalog Issue(s)

Dave Perrin · New User Joined: 24 Oct 2022 Posts: 2 Location: USA

I have some DASD defined in our non-SMS environment. I want to rename (change volser) of the DASD to put them into a different pool (as defined in our Esoterics in the VATLST00 member)

I easily changed the volser and it did change the characteristics on the DASD and did place in the group I expected, but......

There is a SYS1.VVDS.DASDNAME dataset on the DASD as well as a SYS1.VTOCIX.DASDNAME dataset

Two questions/issues:
1. the SYS1.VTOCIX.DASDNAME naming convention is wrong. The name
follows the old DASD volser name instead of the name volser name.
Can that be corrected?

2. A bigger issue is that there are batch jobs still referencing the DASD by
it's old volser. I can only assume that it's due to the SYS1.VVDS file
and entries. So batch runs and asks to mount the old DASD volser.
Since I change volser, batch cannot continue. How to remove
references to the old volser so it's no longer referenced when batch
(VSAM access) is requested?

Joerg.Findeisen · Posted: Tue Oct 25, 2022 12:25 pm

You have mixed up and misunderstood quite a couple of things here. In the VATLST you will never have any ESOTERICs defined. There are Volumes and their MOUNT attributes inside (PRIV/PUBL/STOR).

1) Use ICKDSF BLDIX command to purge the existing VTOCIX. Next use IEFBR14 to define a new VTOCIX according to your naming convention. Use ICKDSF BLDIX again to activate the new IX.

2) VVDS will hold information about VSAM, associated Catalogs with the Volume, and mainly DFSMS information. A new VVDS is automagically allocated with the first VSAM DSN on the volume, unless you allocate it using IDCAMS (which is the proposed way to do it).

Regarding the old volser name, use a utility of your choice to update the JCL libraries for the new volume. Since your volume is Non-SMS you have not much other choices. The only thing I can imagine is to put the old volume to an DFSMS Dummy SGRP and rely on the ESOTERICS defined in HCD. However it is not recommended to use such outdated techniques, switch to DFSMS managed volumes instead.

Dave Perrin · New User Joined: 24 Oct 2022 Posts: 2 Location: USA

Thank you very much.