Preparing to Recover the User Directory

Preparing to recover the user directory involves the following tasks:
  • Getting a printed copy of the directory entries for the following minidisks:
    • The minidisk containing the CMS system disk
    • The minidisk containing the directory source file
    • The minidisk containing the system configuration file.
  • Preventing new users from linking to these minidisks
  • Removing existing links to the minidisks
  • Setting up your virtual machine.

Before you start to recover the directory, you must:

  1. Get a printed copy of the directory entry for:
    • The CMS system disk (usually MAINT 190)
    • The minidisk containing the CMS file that is used to update the directory.

    You must also find out the volume identifier and the virtual device number assigned to the DASD pack that contains the object directory. This information is specified on the DIRECTORY control statement (which is the first statement in the directory source file) and is necessary to recover the user directory.

  2. Find out the real device number of your virtual console. Enter:
    query userid
    where userid is your user ID. CP responds with your user ID and the real device number of your virtual console.
  3. Prevent any new users from logging on. Enter:
    disable all
  4. Reenable your virtual console:
    enable rdev
    where rdev is the real device number of the display you are using for your virtual console.

    If you do not enter this command and somehow you are disconnected, you cannot log back on. You will have to reload the system to log on again.

  5. If there are no links to any of the volumes, proceed to step 9.

    Otherwise, find out which users are linked to minidisks on the volumes. Later in this procedure, enter the DEFINE MDISK command for each of the volumes. If there are any links to the volumes, the DEFINE MDISK command does not complete successfully.

    To find out which users are linked to minidisks on a volume, enter:
    query system rdev
    where rdev is the real device number of the DASD on which the volume resides.

    CP's response lists all of the users who are linked to minidisks on the volume and the virtual device numbers each user assigned to the minidisks. Note both the users and the virtual device numbers.

  6. Ask all users to detach the minidisks from their virtual machines. For example, for each volume, enter:
    warning all problem with the user directory
    warning all please detach link to volid
    where volid is the volume identifier of the selected volume.

    Enter QUERY SYSTEM commands to determine when all users have detached their minidisks on the three volumes.

  7. If users do not detach their minidisks in a reasonable amount of time, try to log off each of the users by entering:
    force userid
    where userid is the ID of a user who still has a link to one of the minidisks.

    If you are unable to log off the users with the FORCE command, contact your support personnel. At this point, you must perform a system restart from your processor complex's system console. A system restart produces a dump that your support personnel may wish to use to diagnose the problem with the FORCE command.

  8. Enter the following command to ensure that your virtual console is operating in VM mode:
    terminal mode vm
  9. Make sure you have enough storage to IPL CMS and to update the user directory.

    Later in the procedure, IPL CMS (as 190). You must have 20 MB of virtual storage to do so. This should also be enough storage to allow you to use the DIRECTXA command successfully. If you IPL a named system, (CMS) 16 MB of storage may suffice. However, if you IPL 190, then you will need 20 MB of storage.

    To find out how much storage you have in your virtual machine, enter:
    query virtual storage
    If you want to change this amount to 20 MB, enter:
    define storage 20m
    Note: If you cannot define enough storage for your virtual machine, reload the system with the NODIRECT option. See Bringing Up the System Without a User Directory (NODIRECT). The NODIRECT option gives you (as the default system operator) 2047 MB of virtual storage, which should be enough to update the directory.

You are now ready to start the directory update process.