Updating the User Directory

Updating the user directory requires you to:

  • Define required minidisks
  • Bring up CMS in your virtual machine
  • Change, if necessary, the directory source file
  • Use the DIRECTXA command
  • Restore normal system operation.
  1. Define the required minidisks.
    Using the information contained in the printed copy of the directory entries you obtained earlier, define:
    • The minidisk containing the CMS system disk
    • The minidisk containing the directory source file
    • The minidisk containing the system configuration file (this is where the new directory is placed).
    Note: If you have problems defining any of the minidisks, go back to step 5.
    To define the minidisk containing the CMS system disk, enter:
    define mdisk as 190 start count volid
    where start is the decimal number that defines the cylinder or block on the real disk that corresponds to the first cylinder or block of the CMS system minidisk; count is a decimal number that specifies the number of cylinders or blocks that make up the minidisk; and volid is the volume identifier of the real DASD volume on which the minidisk resides. (Your copy of the directory entry for the CMS system disk indicates the values you must specify for start, count, and volid.)
    To define the minidisk containing the directory source file, enter:
    define mdisk as 191 start count volid
    where start is the decimal number that specifies the cylinder or block on the real disk that corresponds to the first cylinder or block of the minidisk containing the directory source file; count is a decimal number that specifies the number of cylinders or blocks that make up this minidisk; and volid is the volume identifier of the real DASD volume on which the minidisk resides. (The directory entry for the minidisk containing the CMS file for updating the directory indicates the values you must specify for start, count, and volid.)
    To define the minidisk containing the user directory, enter the following command:
    define mdisk as vdev start count volid
    where vdev is the virtual device number that is assigned the DASD pack on which the directory resides; start is the decimal number that defines the cylinder or block on the DASD that is to be considered cylinder/block 0 for this minidisk. count is the total number of cylinders or blocks this pack contains; and volid is the volume identifier of this pack. (The values you specify for both vdev and volid must match the device number and volume identifier specified on the DIRECTORY statement in the directory.)
  2. Bring up CMS in your virtual machine.
    After you have defined all three minidisks, enter the following command to bring up CMS in your virtual machine:
    ipl 190
  3. Change, if necessary, the directory source file.

    If you think there is a problem with the CMS files containing the directory source statements, use the CMS XEDIT command to update this source file. For information about changing the directory source statement files, see the z/VM: CP Planning and Administration.

    If you think the directory was somehow destroyed and only needs to be recreated, go directly to the next step.

  4. Use the DIRECTXA command.
    When you are satisfied that the directory source file is correct, enter:
    directxa filename
    where filename is the name of the CMS file containing the source statements for the directory. This file should have a file type of DIRECT. If it does not, specify the file type as well as the file name when you enter the DIRECTXA command.
    Note:
    1. By default, the DIRECTXA utility is located on the cross release utilities disk (PMAINT 551). This disk must be accessed to run the DIRECTXA utility.
    2. When writing a user directory, DIRECTXA does not overwrite the current directory but does write an alternate user directory. The directory pointer in cylinder 0 or block 1 is then changed to reference this new directory. It is advisable, therefore, to enter the DIRECTXA command twice. This assures that the directory you wish to use is available; otherwise, you may lose your directory again.
  5. Restore normal system operation.
    Once you recover the directory, you should do one of the following:
    • Log off and log back on using your normal user ID
    • Enter the SHUTDOWN command to shut down the system and then follow normal procedures for bringing it back up.
    In either case, once you are logged on under your normal user ID, enter the following command to enable other users to log on:
    enable all
    You must enter this command because you disabled all devices in Step 3.
Note:
  1. You can use this process to recover the z/VM® user directory at any time. However, if the directory source file is all right, simply enter the DIRECTXA command after you enter the IPL 190 command.
  2. If, after you recover the directory, you determine there are still problems with the source file (or if there are problems that need to be fixed before you can recover the directory), you may have to update the directory source file. For information on how to do this, see the z/VM: CP Planning and Administration.