Managing CA VM:Secure in a Single System Image Complex › SSI Installation Considerations › Converting non-SSI to SSI

Converting non-SSI to SSI

This method starts with a non-SSI VM system, where you have already installed CA VM:Secure. You proceed by following the IBM procedure “Converting a z/VM System to a Single-Member z/VM SSI Cluster” from the CP Planning and Administration document. The required CA VM:Secure steps are as follows:

1. During the step “Update the User Directory”, use CA VM:Secure commands to change USER directory entries to IDENTITY directory entries for any directory entry that you want to run concurrently on multiple members of the cluster. Restructure these virtual machine definitions by moving MDISK and other statements from the IDENTITY to a SUBCONFIG entry.
   1. Change the type of a USER directory entry to an IDENTITY using the CHGENTRY command, as follows:

      CHGENTRY entry IDENTITY
      

   2. Create the needed SUBCONFIG entry by using an ADDENTRY command of the form:

      ADDENTRY NAME-1 ( IN NAME ON *
      

   3. Move needed MDISK definitions from the IDENTITY to the SUBCONFIG by using a TRANSFER command of the form:

      TRANSFER NAME 191 NAME-1 191
      

   4. Move other required statements from an IDENTITY to a SUBCONFIG using the EDIT command.

   At this point you convert the VMSECURE directory entry into an IDENTITY with SUBCONFIG format. For more information on the requirements for the product server, see Distributed Server Definition.

2. Instead of performing the step “Change the User Directory to SSI-Enabled” by running DIRECTXA, you will use product facilities to accomplish this conversion as follows:
   1. LOGON to the product server and issue the END command if it was running.
   2. ACCESS the product source directory minidisk (usually 01B0).
   3. Execute the SSIENAB utility program. It retrieves the SSI member name from the running system, and converts all BUILD statements on the source directory minidisk from the form “BUILD ON *” to the form “BUILD ON membername” convert the source to SSI Enabled format.

      Note: For more information on the SSIENAB utility, see the Reference Guide.

      Use the following form of the command:

      SSIENAB ON filemode
      

      filemode

      Specifies the CMS file mode letter where the source directory minidisk is accessed.

   4. Add an SSINODE statement to the PRODUCT CONFIG file.

      Note: For more information on the statement, see the Reference Guide.

      Use the following form of the command:

      SSINODE membername
      

   5. IPL CMS to bring up the product server. It will perform a SOURCE start to rewrite the CP Object Directory in SSI Enabled format.