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

11-107
version-status Used to default the version to the latest test, production, or archival version of definitions.
The valid choices are:
Test
Production
Archival
Notethat the production and archival status are validonly if youare previewing the data and
not merging. The status is determined by the version-name parameter.
common-version-name Name of the version in the common domain to be linked to the specified version.
This parameter is used only if you are actually merging, the target version is not in the com-
mon domain, and LINK option is true. The default is the same as the source. If you are in
another common-version and want to default to the source common version name, specify
COMMON=!. Once the common-version-name is default to the source, it will remain default-
ing, until you specify another common-version-name. For more information concerning the
linking of versions, refer to Chapter 2.
Discussion
Before the merge process can begin, the environment to which the definitions or structure are to be merged
must be defined. The target dictionary must be a master dictionary. Once a parameter in the MERGE-TO
command is specified, its value will be retained until a new value is specified.
Example
>MERGE-TO DICTIONARY=sysdic.pub;
>>SCOPE=manager;
>>PASSWORD=mgr*;
>>VERSION=version-1;
>>OPEN-MODE=shared-update.
>
PREVIEW
Provides a preview of the results of a proposed merge, before the actual merge takes place.
Syntax
PREVIEW [STRUCTURE-ONLY] [.]
Parameters
STRUCTURE- ONLY If this parameter is specified, then only the dictionary structure will be previewed.
This parameter, if specified, must be on the same line as the PREVIEW command.
Discussion
This command allows you to see the consequences of a merge without actually modifying a dictionary.
Note that the preview process can only be used if the target dictionary is a master dictionary. This
commands generates a report that shows the results of the merge. If structure is being previewed, the
report will contain the following information:
Differences in the external names of entity types, relationship classes and attributes.