Maintain a System Registry

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

Maintain a System Registry

You can maintain the system registry.

To maintain a system registry

Click the System Registry tab, and select Non-Sysplex Systems, Sysplexes, Shared DASD Clusters, or Staging Systems from the tree at the left.
The detailed information appears at the right.
Select the system to maintain.
Update the Name as needed.
Limits: Maximum 8 characters.
Update the Comments as needed.
Limits: Maximum 255 characters.
Update the CCI System ID:
Note: CA recommends that the CCI System ID is not updated.

Limits: Maximum 8 characters.
For Shared DASD or SYSPLEX system only, select the Contact System. This is system where the Shared DASD location or FTP location. The FTP location should be set to the contact system URI. The contact system is used for remote credentials.
For example, assume 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 you set the Contact System to CO11, but you are contacting to XX61 and it will fail because spawn will be started on CO11 but we will look for the output on XX61 because that is where the FTP location was set.

Note: z/OS Version is set by CA MSM.

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.

This procedure was created to help customers that 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.

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 allow the specification of an optional list of VOLSERs used during the allocation of zFS container data sets for USS parts.
Select the Action from the Actions 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 steps will show how the validation failed. See How to Investigate a Failed Validation.
- Validation Rules
  - For a Non-Sysplex system that single system is validated and the last step summaries, verifies and confirms the validation.
  - For a Sysplex system each system within the Sysplex is validated as an individual step and the last step summarizing, verifying, and confirming the validation.
  - For Shared DASD Cluster each Non-Sysplex system is validated, each Sysplex system is validated as describe in the Sysplex Rule and the last step summarizing, verifying, and confirming the validation.
  Note: A Staging system is not validated.
  
  Note: When a system is validated status appears in the Status Field.
  
  This table shows the system validation results and actions.

Result	Action
Validated	System is available, status is updated as valid, and system registry is updated with results from validation.
Validation in Progress	System status is updated to in progress.
Validation Error	System status is updated to error. See How to Investigate a Failed Validation.
Not Validated	This system has not been validated yet.
Not Accessible	The system has not been validated because it is no longer available or was not found in the CCI Network.
Validation Conflict	System has been contacted but the information entered then different then the information retrieved.

Error details
When a validation is in error the Error details button appears. Click this button to find the reason for this conflict. See How to Investigate a Failed Validation.

Note: The error reason is kept in local memory. If the "Please validate the system again." message 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. See How to Investigate a 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.

Email CA about this topic