HP 3000 Manuals HP 3000 Manuals
Initializing the Dictionary
The Dictionary Password
Once you have chosen the Initialization option, you will be asked to
supply a password which will be used to create the dictionary. Because
the dictionary is, itself, a database, this is the database password
which the TurboIMAGE subsystem uses to create the database. It should
not be confused with the scope password which is the password you
specifies when accessing the dictionary. For security reasons, the echo
is turned off for entry of the password:
Dictionary database password >
If you enter [[RETURN]] instead of a password you will be reprompted.
Note that System Dictionary follows the MPE operating system convention
of allowing only three incorrect passwords to be entered. The SDINIT
program will therefore terminate at the third incorrect entry.
When the correct password is entered, the dictionary will prompt for
verification.
Verification of password >
The Verification of password> prompt allows you to check the correctness
of the first password entry. If you enter [[RETURN]] or if you do not
enter the same password in response to this prompt, the following message
will appear and you will again be prompted for the password and
verification:
Verification of password failed (SDERR 2205)
Knowledge of this password should be limited to the Dictionary
Administrator (DA) in order to protect dictionary security and integrity.
The SDPASS File
At this point, if the file SDPASS already exists, you will be prompted
for permission to overwrite.
SDPASS.groupname.accountname already exists. Is it okay to overwrite (N/Y)?
If you answer "N" , SDINIT will terminate. If the answer is "Y" , SDPASS
will be overwritten.
Defining the Capacities
The Default Capacities. Once the database password has been entered,
System Dictionary displays the following list of the HP-defined
dictionary default capacities. You may use all of the default values for
these capacities by responding "Y" or [[RETURN]] to the Are the
capacities correct? (Y/N) > prompt, or you may choose to change these
capacities. If you decide to make changes and respond "N" , you will be
allowed to alter any or all of the values. See the paragraph below
entitled "User-Defined Capacities." A definition of each of the
capacities is shown on the following page.
_____________________________________________________________________
| |
| Capacity for ALIASES is 2000 |
| Capacity for user defined ATTRIBUTES is 50 |
| Capacity for user defined ENTITY TYPES is 25 |
| Capacity for user defined RELATIONSHIP CLASSES is 10 |
| Capacity for user defined binary RELATIONSHIP TYPES is 45 |
| Capacity for user defined N-ary RELATIONSHIP TYPES is 5 * |
| Capacity for average no. attributes associated to ET & RT is 2|
| Capacity for DOMAINS is 16 |
| Capacity for ENTITY names is 3000 |
| Capacity for total versions of ENTITIES is 5000 |
| Capacity for binary RELATIONSHIPS is 4900 |
| Capacity for N-ary RELATIONSHIPS is 100 |
| Capacity for total versions of RELATIONSHIPS is 7000 |
| Capacity for FIXED LENGTH ATTRIBUTE DATA is 12000 |
| Capacity for FIXED LENGTH ATTRIBUTE EDIT DATA is 100 |
| Capacity for VARIABLE LENGTH DATA is 5000 |
| Capacity for SCOPES is 32 |
| Capacity for SCOPE/ENTITY associations is 500 |
| Capacity for SCOPE/RELATIONSHIP associations is 500 |
| Capacity for SCOPE/DOMAIN associations is 100 |
| Capacity for VERSIONS is 32 |
| Capacity for VERSION LOGGING is 1000 |
| |
| Are the capacities correct? (Y/N) > |
_____________________________________________________________________
* N-ary relationship types are any relationship types involving 3 to 6
entity types, in contrast to binary relationship types which are
relationship types between only 2 entity types.
Table 2-1. System Dictionary Capacities
---------------------------------------------------------------------------------------------
| | |
| CAPACITY | DESCRIPTION |
| | |
---------------------------------------------------------------------------------------------
| | |
| ALIASES | The total number of alias names for all |
| | entity and relationship occurrences. |
| | |
---------------------------------------------------------------------------------------------
| | |
| ATTRIBUTES | These are the structural components of the |
| | dictionary database and are whatever |
| ENTITY TYPES | numbers you want to specify. The total |
| | number of these items already defined in |
| RELATIONSHIP CLASSES | the HP-provided core set will be |
| | automatically added in. |
| Binary RELATIONSHIP TYPES | |
| | |
| N-ary RELATIONSHIP TYPES | |
| | |
---------------------------------------------------------------------------------------------
| | |
| Average number of attributes associated to | The average number of user-defined |
| | attributes associated to ENTITY TYPES and |
| ET and RT | RELATIONSHIP TYPES. The total number of |
| | HP-defined attribute-type pairs is |
| | automatically added in. |
| | |
---------------------------------------------------------------------------------------------
| | |
| DOMAINS | The total number of domain definitions. |
| | The total number of HPdefined domains is |
| | automatically added in. |
| | |
---------------------------------------------------------------------------------------------
| | |
| ENTITY names | The total number of entity names, including |
| | synonyms. |
| | |
---------------------------------------------------------------------------------------------
| | |
| Total versions of ENTITIES | The total number of versions of all |
| | entities. There can be many versions of |
| | the same entity. |
| | |
---------------------------------------------------------------------------------------------
| | |
| Binary RELATIONSHIPS | The total number of binary or N-ary |
| | relationship occurrences. |
| N-ary RELATIONSHIPS | |
| | |
---------------------------------------------------------------------------------------------
| | |
| Total versions of RELATIONSHIPS | The total number of all versions of all |
| | binary and N-ary relationships. There can |
| | be many versions of a relationship. |
| | |
---------------------------------------------------------------------------------------------
| | |
| FIXED LENGTH ATTRIBUTE DATA | The total number of 40-byte buffers of |
| | attribute data for all entity and |
| | relationship occurrences. To estimate this |
| | capacity, use the following guideline: |
| | Capacity for fixed length attribute data = |
| | (Average attribute length * Average number |
| | of attributes associated to ET and RT/40) |
| | [rounded off to next digit] * (Total |
| | versions of all entities + Total versions |
| | of all relationships). |
| | |
---------------------------------------------------------------------------------------------
Table 2-1 System Dictionary Capacities (continued)
---------------------------------------------------------------------------------------------
| | |
| CAPACITY | DESCRIPTION |
| | |
---------------------------------------------------------------------------------------------
| | |
| FIXED LENGTH ATTRIBUTE EDIT DATA | The maximum number of 40-byte buffers for |
| | storing additional edit text data that you |
| | expect to have in the dictionary. There is |
| | a 40-byte buffer associated by default with |
| | each attribute defined in the dictionary. |
| | This capacity is the total number of |
| | additional buffers needed to store |
| | attribute edit text in excess of the |
| | default. |
| | |
---------------------------------------------------------------------------------------------
| | |
| VARIABLE LENGTH ATTRIBUTE DATA | The maximum number of 80-character lines |
| | you expect to have in the dictionary. If |
| | you have only one variable length attribute |
| | and that attribute has, on the average, 3 |
| | lines of text, and 50 definitions use this |
| | attribute, this capacity should be (3*50), |
| | or 150. |
| | |
---------------------------------------------------------------------------------------------
| | |
| SCOPES | The total number of scope definitions. |
| | |
---------------------------------------------------------------------------------------------
| | |
| SCOPE/ENTITY associations | The total number of associations between |
| | entities and scopes. |
| | |
---------------------------------------------------------------------------------------------
| | |
| SCOPE/RELATIONSHIP associations | The total number of associations between |
| | relationships and scopes. |
| | |
---------------------------------------------------------------------------------------------
| | |
| SCOPE/DOMAIN associations | The total number of associations between |
| | domains and scopes. |
| | |
---------------------------------------------------------------------------------------------
| | |
| VERSIONS | The total number of version definitions. |
| | |
---------------------------------------------------------------------------------------------
| | |
| VERSION LOGGING | The total number of version status changes |
| | to be made to all versions. |
| | |
---------------------------------------------------------------------------------------------
User-Defined Capacities. If you answered "N" to the prompt Are the
capacities correct? (Y/N) > you will be given the chance to change the
capacities with the following prompt (where xxx is the default capacity):
__________________________________________________________________________
| |
| 1 ALL |
| 2 Capacity for ALIASES is xxx |
| 3 Capacity for user defined ATTRIBUTES is xxx |
| 4 Capacity for user defined ENTITY TYPES is xxx |
| 5 Capacity for user defined RELATIONSHIP CLASSES is xxx |
| 6 Capacity for user defined binary RELATIONSHIP TYPES is xxx |
| 7 Capacity for user defined N-ary RELATIONSHIP TYPES is xxx |
| 8 Capacity for average no. attributes associated to ET & RT is xxx|
| 9 Capacity for DOMAINS is xxx |
| 10 Capacity for ENTITY names is xxx |
| 11 Capacity for total versions of ENTITIES is xxx |
| 12 Capacity for binary RELATIONSHIPS is xxx |
| 13 Capacity for N-ary RELATIONSHIPS is xxx |
| 14 Capacity for total versions of RELATIONSHIPS is xxx |
| 15 Capacity for FIXED LENGTH ATTRIBUTE DATA is xxx |
| 16 Capacity for FIXED LENGTH ATTRIBUTE EDIT DATA is xxx |
| 17 Capacity for VARIABLE LENGTH ATTRIBUTE DATA is xxx |
| 18 Capacity for SCOPES is xxx |
| 19 Capacity for SCOPE/ENTITY associations is xxx |
| 20 Capacity for SCOPE/RELATIONSHIP associations is xxx |
| 21 Capacity for SCOPE/DOMAIN associations is xxx |
| 22 Capacity for VERSIONS is xxx |
| 23 Capacity for VERSION LOGGING is xxx |
| 24 DONE |
| |
| Enter code > |
| |
__________________________________________________________________________
You can now alter the capacity of any item by entering the appropriate
code number next to that item. Valid responses are code numbers 1
through 24, [[RETURN]], and [[CONTROL]] Y. Any other response will result
in an error and Enter code> will be reprompted.
* If you enter code 1, you will be prompted for a new capacity for each
of the dictionary components. After the last item is prompted, the
entire capacity list is displayed, giving you another chance to
verify its correctness. If you enter [[CONTROL]] Y while being
prompted for the capacities, SDINIT will discontinue prompting and
list the current capacities, allowing you to verify the list.
* If you enter any number from 2 to 23, you may alter a specific
capacity. If, for example, you enter code 3, the prompt will be:
New Capacity for user defined ATTRIBUTES (xxx) >>
If you enter [[RETURN]] or [[CONTROL]] Y to this prompt, the default
value will be used.
* The prompt Enter code > is repeated until a [[RETURN]], code 24, or
[[CONTROL]] Y is entered. If any of these responses are entered, the
capacities are listed, allowing you to verify them.
Once the capacities are correct, you are then prompted for external and
internal names for the first version in the common domain and the DA
scope, and then the password for the DA scope. All of these names are
user-supplied. Any names that are meaningful to your particular
application can be used. Every definition in the dictionary, whether it
is a structural component such as entity type or an actual entity
occurrence, has both an internal name and an external name associated
with it. The internal name can never change and is designed to be used
by software products which interface with the dictionary and rely on a
given name for identification purposes. The external name is intended
for end users of the dictionary and can be changed through the SDMAIN
program. If not specified, the internal name defaults to the same name
as the external name. Once, however, the internal name is chosen, the
only way to change the name is to initialize a new dictionary with a
different internal name. For a complete discussion of scopes, versions,
and domains, refer to Chapter 4 of the HP System Dictionary/XL General
Reference Manual, Volume 1 (32256-90004). The echo is turned off for
entry of the password.
__________________________________________________
| |
| External name of version in common domain >|
| Internal name of version in common domain >|
| External name of DA scope > |
| Internal name of DA scope > |
| Password for DA scope > |
| Verification of DA password > |
__________________________________________________
If you enter [[RETURN]] or do not type in the same password at the
Verification of DA password> prompt, the following message will appear
and you will again be prompted for the password and verification:
Verification of password failed (SDERR 2205)
Once you have supplied names in response to the above prompts, SDINIT
will list the names which you have entered (indicated here by xxx's),
thus allowing you to verify them:
_______________________________________________________
| |
| External name of version in common domain is xxx|
| Internal name of version in common domain is xxx|
| External name of DA scope is xxx |
| Internal name of DA scope is xxx |
| Are the names correct? (Y/N) > |
_______________________________________________________
If you answer "N" to Are the names correct? (Y/N) >, you will then be
reprompted starting with
External name of version in common domain >.
If you answer "Y" , and SDTEMP1 exists, you will be prompted for
permission to overwrite it, as shown below.
SDTEMP1.groupname.accountname already exists. Is it okay to overwrite (N/Y)?
If you answer "N" to this prompt, SDINIT will terminate.
Submitting the Job Stream
You have now completed the process of supplying the necessary
initialization information and the only step that now remains to be done
is to submit the job stream which completes the initialization process.
If your response was "Y" to the prompt Are the names correct? (Y/N) >,
you should now see the following prompt:
Input Priority of Job Stream (8) >
Here, you specify the input priority for the job. If [[RETURN]] is
entered, the default value of 8 which is shown in the prompt will be
used. Otherwise, you can enter any priority from 1 (the lowest priority)
to 13 (the highest priority). You can, therefore, defer the execution of
the job if necessary.
You must now specify an output priority for the job stream listing:
Output Priority for Job Stream Listing (8) >
As with the input priority, the default for the output priority is also 8
and will be used if [[RETURN]] is pressed. Otherwise, priority values
from 1 (the lowest priority) to 13 (the highest priority) can be used,
allowing you to defer the listing if necessary.
You are now prompted for any passwords which exist at the user, group,
and account levels. For security reasons, the echo is turned off for
entry of the passwords:
User Password >
Group Password >
Account Password >
If you used passwords at any of these levels when you logged on, you must
now enter them. You can specify whether you want the job stream to be
automatically submitted or not.
Automatically Submit Job Stream? (Y/N) >
If you answer "N" , the following message will be displayed on the
screen, and SDINIT will terminate.
Submit SDSTREAM job to complete initialization process
If you would like to complete the initialization process on line instead
of in batch mode, enter:
RUN SDINIT.PUB.SYS; INFO="BUILD"; PARM=1
If you answer "Y" to the prompt Automatically Submit Job Stream? (Y/N)
>and if any of the entered passwords are invalid, you will receive the
following message and will again be prompted to enter the valid
passwords:
Unable to stream special job stream (SDERR 2264)
Otherwise, you will receive both the MPE job number and the SDINIT job
stream message, as follows:
#J383
System Dictionary Initialization Job Stream Submitted
Job Stream Messages. Once the job stream is successfully submitted, you
will receive the following messages as long as you remain logged on to
the same user and account under which the job was submitted. If,
however, you switch users or accounts, you will not receive any of the
initialization messages.
When the job begins execution, the following message appears:
System Dictionary Initialization Begins
If SDINIT completes successfully, the following message is displayed:
System Dictionary SYSDIC Created
In addition, an output listing which lists a report on dictionary
capacities and core set definitions will be produced.
If any error occurred during initialization, an error message will be
displayed at your terminal. Messages are also written to the output
listing of SDINIT. If for any reason you did not receive the completion
message at your terminal, check the output listing for any errors. If
errors occurred, correct them and then run SDINIT again.