Converting non-SSI to SSI

Administration Guide › Managing CA VM:Director 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:Director. Follow 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:Director steps are as follows:

For any directory entry that you want to run concurrently on multiple members of the cluster, perform the following actions. During the “Update the User Directory” step, perform the following actions:
- Change USER directory entries to IDENTITY directory entries by using CA VM:Director commands.
- 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, by using the following format of the CHGENTRY command:
```
CHGENTRY entry IDENTITY
```
2. Create the needed SUBCONFIG entry by using the following format of the ADDENTRY command:
```
ADDENTRY NAME-1 ( IN NAME ON *
```
3. Move needed MDISK definitions from the IDENTITY to the SUBCONFIG by using the following format of the TRANSFER command:
```
TRANSFER NAME 191 NAME-1 191
```
4. Move other required statements from an IDENTITY to a SUBCONFIG using the EDIT command.
5. Convert the VMDIRECT directory entry into an IDENTITY with SUBCONFIG format.
For more information about the requirements for the product server, see Distributed Server Definition.
Instead of performing the “Change the User Directory to SSI-Enabled” step by running DIRECTXA, 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. This utility performs the following actions:
  - Retrieve the SSI member name from the running system.
  - Convert all BUILD statements on the source directory minidisk from the form “BUILD ON *” to the form “BUILD ON membername”.
    These steps convert the source to SSI Enabled format.
  Note: For more information, see the SSIENAB utility in 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 about the statement, see the Reference Guide.
  
  Use the following form of the command:
```
SSINODE membername
```
5. IPL CMS to bring up the product server. This action performs a SOURCE start to rewrite the CP Object Directory in SSI Enabled format.