HP 3000 Manuals

HP System Dictionary XL Gen. Ref. Vol. 2-Part 4 SDUTIL

SDUTIL Examples 

The following examples demonstrate user input for some typical operations
which may be done while using SDUTIL, and are provided for your guidance.


NOTE  In these examples, SDUTIL keywords and commands are shown in
      uppercase, and user-defined variables are shown in lowercase.  Note
      that System Dictionary does not require you to use upper and lower
      case as shown here.  You may enter commands, keywords, variables,
      and their abbreviations in whichever case you choose, as System
      Dictionary automatically upshifts everything except passwords.
      Passwords, therefore, must be entered exactly as defined in the
      dictionary.


Compiling / Archiving a dictionary 

Frequently used versions can be compiled into a compiled dictionary for
faster performance.  You may also compile selected versions of different
domains into a compiled dictionary for archival.

Example.  The following example shows compiling/archiving two versions
into a compiled dictionary named 'acctng'.

     >FROM DICTIONARY=sysdic.pub; 
     >>SCOPE=accounting-manager; 
     >>PASSWORD=amgr; 
     >>VERSION=general-ledger; 
     >>DOMAIN=accounting; 
     >>OPEN-MODE=read-allow-read. 
     >
     >COMPILE-TO DICTIONARY=acctng. 
     >
     >COMPILE 
     >
     >FROM version=payroll. 
     >
     >COMPILE 
     >

Merging a Version 

A version in a domain can be merged into a new or an existing version.

Example 1.  This example shows merging a source version into a new target
version.  If the version exists on the target, do not merge but skip it.

     >FROM DICTIONARY=sysdic.pub; 
     >>SCOPE=accounting-manager; 
     >>PASSWORD=amgr; 
     >>DOMAIN=accounting; 
     >>VERSION=version2; 
     >>OPEN-MODE=read-only. 
     >
     >MERGE-TO DICTIONARY=sysdic.pub; 
     >>SCOPE=accounting-manager; 
     >>PASSWORD=amgr; 
     >>DOMAIN=accounting; 
     >>VERSION=version1; 
     >>OPEN-MODE=exclusive-update. 
     >
     >MERGE-OPTIONS VERSION-CONFLICT=skip. 
     >
     >MERGE 
     >

Example 2.  This example shows merging a source version into an existing
target version.  The target version name is the same as the source
version name.  If the version exists in the target, merge source
occurrences in.

     >FROM DICTIONARY=sysdic.pub; 
     >>SCOPE=accounting-manager; 
     >>PASSWORD=amgr; 
     >>DOMAIN=acct1; 
     >>VERSION=version1; 
     >>OPEN-MODE=read-only. 
     >
     >MERGE-TO DICTIONARY=sysdic.pub; 
     >>SCOPE=accounting-manager; 
     >>PASSWORD=amgr; 
     >>DOMAIN=acct2; 
     >>VERSION=!; 
     >>OPEN-MODE=exclusive-update. 
     >
     >MERGE-OPTIONS VERSION-CONFLICT=merge. 
     >
     >MERGE 
     >

Merging Structure 

Structure can only be merged, if the source and target dictionaries are
not the same.  You can either merge structure only or occurrences as
well.

Example 1.  This example shows merging a source version to another
version and at the same time, merging the structure.  Since
complete-structure is not specified, only the structure involving the
occurrences of the source version will be merged.

     >FROM DICTIONARY=acctng; 
     >>SCOPE=accounting-manager; 
     >>PASSWORD=amgr; 
     >>DOMAIN=accounting; 
     >>VERSION=version1; 
     >>OPEN-MODE=read-only. 
     >
     >MERGE-TO DICTIONARY=sysdic; 
     >>SCOPE=accounting-manager; 
     >>PASSWORD=amgr; 
     >>DOMAIN=!; 
     >>VERSION=!; 
     >>OPEN-MODE=exclusive-update. 
     >
     >MERGE 
     >

Example 2.  This example shows merging the complete structure of the
source compiled dictionary into the target dictionary.

     >FROM DICTIONARY=acctng; 
     >>SCOPE=accounting-manager; 
     >>PASSWORD=amgr; 
     >>DOMAIN=accounting; 
     >>VERSION=version1; 
     >>OPEN-MODE=read-only. 
     >
     >MERGE-TO DICTIONARY=sysdic; 
     >>SCOPE=accounting-manager; 
     >>PASSWORD=amgr; 
     >>OPEN-MODE=customization. 
     >
     >MERGE-OPTIONS COMPLETE-STRUCTURE=true. 
     >
     >MERGE STRUCTURE-ONLY 
     >

Merging a Version across Systems 

If the target dictionary cannot be accessed directly, you can compile the
source version(s) into a compiled dictionary, transport the compiled
dictionary to the target system and then merging the versions into the
target system.

Example.  This example shows compiling a source version into a compiled
dictionary and then merge the version from the compiled dictionary to the
target dictionary.  Only the variable length attribute 'edit-mask' is
merged.

     >FROM DICTIONARY=sysdic.pub; 
     >>SCOPE=accounting-manager; 
     >>PASSWORD=amgr; 
     >>DOMAIN=accounting; 
     >>VERSION=version1; 
     >>OPEN-MODE=read-allow-read. 
     >
     >COMPILE-TO DICTIONARY=acctng. 
     >
     >COMPILE-OPTIONS INCLUDE-VAR-ATTRIBUTE=edit-mask. 
     >
     >COMPILE 
     >

The compiled dictionary 'acctng' is then transported to the target system
and the version is merged to the same version and domain name as the
source.

     >FROM DICTIONARY=acctng; 
     >>SCOPE=accounting-manager; 
     >>PASSWORD=amgr; 
     >>DOMAIN=accounting; 
     >>VERSION=version1; 
     >>OPEN-MODE=read-only. 
     >
     >MERGE-TO DICTIONARY=sysdic; 
     >>SCOPE=accounting-manager; 
     >>PASSWORD=amgr; 
     >>DOMAIN=!; 
     >>VERSION=!; 
     >>OPEN-MODE=exclusive-update. 
     >
     >MERGE 
     >

Previewing a Merge 

You can preview the results of a merge, before the actual merge takes
place.

Example.  This example shows previewing a merge operation.

     >FROM DICTIONARY=sysdic.pub; 
     >>SCOPE=accounting-manager; 
     >>PASSWORD=amgr; 
     >>VERSION=accounts-payable; 
     >>DOMAIN=accounting; 
     >>OPEN-MODE=read-only. 
     >
     >MERGE-TO DICTIONARY=sysdic.accting; 
     >>SCOPE=personnel-manager; 
     >>PASSWORD=pmgr; 
     >>VERSION=payroll; 
     >>DOMAIN=personnel; 
     >>OPEN-MODE=read-only. 
     >
     >PREVIEW 
     >

MPE/iX 5.0 Documentation