Reference Guide › Command Reference › CHGVOLNM Command

CHGVOLNM Command

Use the CHGVOLNM command to change the volser (and all references to it) of any DASD volume controlled by CA VM:Director.

CHGVOLNM oldvolser newvolser {LABEL | NOLABEL}

When issuing the CHGVOLNM command, CA VM:Director must have OPTION D84NOPAS in its directory entry if the directory has any user IDs that have the special password of LBYONLY. Failing to have this authorization can result in errors and the command outcome can be unpredictable.

When CHVOLNM detects when more than one volume is online with the same volser, the command will exit with return code 100 and issue message 811E. To avoid this, do the following:

1. Use the CP VARY OFFLINE rdev command to vary any volumes offline, that has the same volser of the volume, you want to change. This also applies to the volumes defined as Parallel Access Volumes (PAV). rdev specifies the real device address of the volume.

   The volume specified by rdev is VARIED OFFLINE.

2. Use the CP VARY OFFLINE rdev for each PAV alias volume to make sure that only one definition of the volume is available online, so that each volser is unique.

   Each PAV alias volume specified by rdev is VARIED OFFLINE.

3. Execute the CHGVOLNM command to change the volser of the volume.

   The volser of the volume changes.

Definitions

oldvolser newvolser

Identifies the current volser for the volume and specifies the new volser to replace it.

LABEL | NOLABEL

Changes (LABEL) or does not change (NOLABEL) the physical volser in the volume label.

If you use LABEL, CA VM:Director detaches the volume from the system and reattaches it using the new volser. To use LABEL, the service virtual machine must have CP privilege class B or the equivalent CP authorization. No user can have an actual link to any minidisk on the volume if you run CHGVOLNM with LABEL. You cannot change the volser of a CP‑owned volume.

You may use NOLABEL if the physical volser has already been changed using a separate procedure. You may also use NOLABEL if the volume is not physically available; however, since CHGVOLNM will update user directory entries to reference the new volser, users will not be able to link to their minidisks on the volume until the physical volser is renamed. You can run CHGVOLNM with NOLABEL even if users have links to minidisks on the volume.

Description

Note: The CHGVOLNM command requires a CP formatted disk label. Do not use the CHGVOLNM command against CMS‑formatted minidisks.

The CHGVOLNM command allows you to change the volser of any DASD volume controlled by CA VM:Director, and to have it update all references to the volume by its new volser, including the reference in the physical label of the DASD.

CA VM:Director changes references to the old volser in the following:

• The VOLUME record in the DASD CONFIG file that identifies the volume to CA VM:Director
• All MDISK statements in all source directory entries that define minidisks on the target volume, including both minidisks CA VM:Director controls and minidisks it does not control
• Authorizations in all GRANT and WITHHOLD records to use the COMPRESS volser and MAP volser commands
• CA VM:Director control blocks, directory source files, and the object directory

Important! CHGVOLNM does not change the volser parameter on the DIRECT record in the PRODUCT CONFIG file. If you change the volser of the object directory volume, you must change that record manually; otherwise CA VM:Director will not initialize.

At its completion, CHGVOLNM sends a file called CHGVOLNM UPDATE to your A‑disk. This file lists the user ID and virtual address of each MDISK statement that was updated and indicates the original volser and the new volser. If a file with this name already exists, CHGVOLNM appends the new information to the existing information in the file and indicates the date and time the changes occurred.

To prevent the CHGVOLNM command from having to wait for a lock, CA VM:Director acquires a private lock against the entire DRCT (source) disk during execution of the command. This lock prevents other directory management tasks from starting and may cause currently running tasks to wait until the command completes.

Note: If a system failure occurs while CHGVOLNM is running, the volser change may be only partially complete. You may have to manually change references to the volser that CHGVOLNM did not change before the system failure.

Examples

• To change the physical volser for a DASD volume from XA0001 to ESA001 and to update all appropriate MDISK statements, GRANT and WITHHOLD records, and internal objects to refer to the new volser, enter:

  vmdirect chgvolnm xa0001 esa001 label
  

• To change all references to the volume without changing the physical volser, enter:

  vmdirect chgvolnm xa0001 esa001 nolabel