Resolving object-definition conflicts after converting

The conversion process converts every object into one record in the Shared Repository data set.

Because each object can have only one record within the Shared Repository, but be a member of more than one group, you might encounter object-definition conflicts. If a conflict is encountered, it is identified on the CSM Conversion Log data set (Migrating-a-CSM-database-from-a-previous-release).

An object-definition conflict can occur when an object already has a record in the Shared Repository and the object is being converted as a member of a different group with different definitions (see Table 1).

Table 1 shows all possible definitions for an object. The first column contains the object definitions that can be different for each group. The second column contains the object definitions that must be identical for all groups containing this object.

Table 1. Object definitions

Do not have to match in the repository

Must match within the repository

Parents

Client

Server

Schedules

  • Object Type
  • Restart Only
  • Verify Force Down
  • Start Command/EXEC
  • User Post Start EXEC
  • Stop Command/EXEC
  • User Post Stop EXEC
  • Cancel Command/EXEC
  • Recovery Command/EXEC
  • Start Command Time Out
  • Stop Command Time Out
  • Start Command Limit
  • Start Event Text ID and Type
  • Stop Event Text ID and Type
  • Abnormal Termination Events
  • TSO Send User ID
  • Pager Contact
  • Pager Info
  • Alert Queue
  • Rules Generation

You can resolve a conflict by starting CSM and by using the CSM Object Definition panel to edit each object and ensure that the object definitions for each object in every group match exactly (with the exception of the object’s Parents, Clients, Servers and Schedules).

If you do not want each object in every group to have identical definitions, you can also resolve a conflict by using variables in CSM object definitions that can resolve to different values for the different groups on different BBI-SS PASs. The definition can contain MainView AutoOPERATOR SHARED variables. For more information, refer to the section 'Using Variables in the Object Definition Fields' in the MainView AutoOPERATOR Solutions Guide.

Another way to resolve a conflicts is to place the new group into a different Shared Repository data set.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*