IBM Mainframe Forum Index
Log In
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register

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

IBM Mainframe Forums -> JCL & VSAM
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
Dave Perrin

New User

Joined: 24 Oct 2022
Posts: 2
Location: USA

PostPosted: Mon Oct 24, 2022 11:49 pm
Reply with quote

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?
Back to top
View user's profile Send private message

Senior Member

Joined: 15 Aug 2015
Posts: 1269
Location: Bamberg, Germany

PostPosted: Tue Oct 25, 2022 12:25 pm
Reply with quote

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.
Back to top
View user's profile Send private message
Dave Perrin

New User

Joined: 24 Oct 2022
Posts: 2
Location: USA

PostPosted: Wed Oct 26, 2022 12:08 am
Reply with quote

Thank you very much.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> JCL & VSAM


Similar Topics
Topic Forum Replies
No new posts Binary File format getting change whi... All Other Mainframe Topics 7
No new posts SFTP Issue - destination file record ... All Other Mainframe Topics 2
No new posts Access to non cataloged VSAM file JCL & VSAM 18
No new posts Merge two VSAM KSDS files into third ... JCL & VSAM 6
No new posts 3270 personal communications. Can't c... TSO/ISPF 2
Search our Forums:

Back to Top