Installing Your Product Using CA MSM › Setting System Registry › Change a System Registry

Change a System Registry

You can change the system registry if you have Monoplexes with the same sysplex name (for example: LOCAL). Instead of showing multiple LOCAL sysplex entries which would need to be expanded to select the correct Monoplex system, the CA MSM System Registry shows the actual Monoplex System name at the top level Sysplex Name.

Follow these steps:

1. Click the System Registry tab, and select Non-Sysplex Systems, Sysplexes, Shared DASD Clusters, or Staging Systems from the tree on the left side.

   Information about the systems that you selected appears on the right side.

2. Select the system to change.

   Detailed information about the system appears on the right side.

3. Update the following information as needed. The information that you update is dependent on whether you are changing a Non-Sysplex System, Sysplex, Shared DASD Cluster, or Staging System.
4. Depending on the type of system, do one of the following:
   • For Shared DASD or sysplex system only, select the contact system, which is the system where the Shared DASD or FTP is located. The FTP location should be set to the contact system URI. The contact system is used for remote credentials.

     For example, if the contact system is set to CO11, FTP location URI is set to XX61 and the remote credentials are set up for CO11, the deployment could fail because your remote credentials might not be the same on both systems (CO11 and XX61) and, because you set the Contact System to CO11 but you are contacting to XX61, a spawn will be started on CO11 but CA MSM will look for the output on XX61 because that is where the FTP location was set.

     Note: Monoplexes are stored in the Sysplex registry tree but with the name of the Monoplex System and not the Monoplex Sysplex name. For example, a system XX16 defined as a Monoplex, with a sysplex name of LOCAL. It will be depicted in the System Registry as a Sysplex with the name of XX16. This sysplex will contain one system: XX16.

     The FTP and DATA Destinations at the system level are not used when the Sysplex is a Monoplex. The only FTP Location and Data Destinations that are referenced are those defined at the Sysplex Level.

   • For Staging systems, enter the GIMUNZIP volume and/or zFS candidate volumes.

     The zFS candidate volumes let you specify an optional list of VOLSERs used during the allocation of zFS container data sets for USS parts.

5. Select one of the following actions from the Actions drop-down list in the General bar:

   Cancel

   Cancel this maintenance.

   Save

   Save the changes to this maintenance.

   Validate

   Validate authenticates this entry.

   Note: The validation process is done in steps; each system in this request is validated with the last step summarizing, verifying, and confirming the validation. If the validation fails this step shows how the validation failed. You can investigate the failed validation.

   Validation Rules

   • For a Non-Sysplex system, that single system is validated and the last step summarizes, verifies, and confirms the validation.
   • For a Sysplex system, each system within the Sysplex is validated as an individual step and the last step summarizes, verifies, and confirms the validation.
   • For Shared DASD Cluster each Non-Sysplex system is validated, each Sysplex system is validated as described in the Sysplex Rule and the last step summarizes, verifies, and confirms the validation.

   Note: A Staging system is not validated.

   When a system is validated, the status appears in the Status field.

   The following are the system validation results:

   Validated

   Indicates that the system is available, status is updated as valid, and system registry is updated with results from validation.

   Validation in Progress

   Indicates that the system status is updated to in progress.

   Validation Error

   Indicates that the system status is updated to error, and you can investigate the failed validation.

   Not Validated

   Indicates that this system has not been validated yet.

   Not Accessible

   Indicates that the she system has not been validated because it is no longer available or was not found in the CCI Network.

   Validation Conflict

   Indicates that the system has been contacted but the information entered then different then the information retrieved.

   Error Details

   When there is a validation conflict, the Error details button appears. Click this button to find the reason for this conflict. You can investigate the failed validation.

   Note: The error reason resides in local memory. If the message Please validate the system again appears, the local memory has been refreshed and the error has been lost. To find the conflict again, validate this system again.

   Conflict Details

   When a validation is in conflict, the Error details button appears. Click this button to find the reason for this conflict. You can investigate the failed validation.

   Note: The conflict reason is kept in local memory. If the "Please validate the system again." message appears, the local memory has been refreshed and the conflict has been lost. To find the conflict again, validate this system again.