HP System Dictionary/XL General Reference Manual Vol 2 - Part 1 SDINIT (32256-90005)

10- 87
the source but not in the target.
The number of attributes associated with a particular entity type or relationship type in the source
dictionary may be different than the number of attributes associated with the same entity type or
relationship type in the target dictionary. If so, SDUTIL will preserve the ones that are already associated
in the target definition and add those that exist in the source dictionary, but not in the target dictionary.
Again, the reason for doing this is because deleting the attributes also deletes the attribute values of the
entities and relationships. All the above differences will be reported. You may make changes as desired
after SDUTIL completes the merge.
SCOPE CONFLICTS. The DA can merge security data such as scopes, scope entity associations and
scope relationship associations. When scopes are being merged, SDUTIL checks for the internal name of
the source scope in the target dictionary. If it does not exist, SDUTIL will create it with the same
characteristics as the source scope. However, if the scope already exists and the passwords and scope
rights are the same, SDUTIL will not change the target scope. If the external names or passwords are
different, SDUTIL will report the difference(s), but will not change the external name or the password. If
the scope-rights are different, SDUTIL will take its consistent approach of preserving the existing scope-
rights of the target dictionary scope, and add those from the source scope that do not exist in the target
scope. Again, the differences will be reported and you may make changes later as desired.
OCCURRENCE CONFLICTS. SDUTIL checks internal names to determine whether or not an entity
exists in the target dictionary.
• If an entity (internal name) already exists in the target dictionary, but its external name is differ-
ent than the external name in the source dictionary, SDUTIL will not change the external name in the
target dictionary. The reasons for not changing the external names are 1) it could cause conflicts with
other existing external names, 2) it will preserve external names on which some applications may de-
pend, and 3) changing the entity names will also change the relationships that involve the changed en-
tity names, which may be undesirable.
It is possible for an occurrence in the target dict ionary to have the same internal name as an occurrence
in the source dictionary, but have a different set of attribute values. When this happens, you will be giv-
en a set of options to choose from to handle this conflict. These options are explained in detail in the IN-
COMPATIBLE-DEFINITION option in the description of the MERGE-OPTIONS command in Chapter
3.
• If an entity (internal name) does not exis t, SDUTIL will create it. Note that even though the inter-
nal name of a new entity may not exist, there may be an existing entity that has the same external name
as the entity being created. When this happens, SDUTIL will take the action based upon the NAME-
CONFLICT option. See the description of the MERGE-OPTIONS command in Chapter 3 for details
about this option.
Common Version Linking. The local (source) version may be linked to a version in the common
domain, and occurrences in that local version may be linked to occurrences in a version in the common
domain. When you merge a version with links, you have the option of either keeping the links intact, or not
including them in the merge. If you do keep the links (set the link option to TRUE) and the target version
exists, it will be linked to the version being merged in. Occurrences will be created in this version as
necessary to support the links in the version being merged in, and those links will be copied as in the
source dictionary. If the target version does not exist, a new version containing the occurrences needed by
the links will be created in the common domain of the target dictionary. A link from the merged-in version
to this new common domain version will also be created. The occurrence linking will then be copied as in
the source dictionary.
If you set the link option to TRUE, the external name differences will be checked both on the local entity
and the common entity in the common domain. The linking structure of occurrences will be copied or
removed based on the source occurrences. If, for any reason, an occurrence cannot be linked to an
occurrence in the common domain, then the occurrence will exist as a local occurrence and will not be
linked to the occurrence in to the common version. Note that if you set the link option to TRUE while the
source version is not linked to a common version, any existing links to occurrences in the target version