HP 3000 Manuals HP 3000 Manuals
Reinitializing the Dictionary
If you currently have a dictionary, but want to change either the
password or any of the capacities, then you will need to reinitialize the
dictionary using SDINIT. You can only do this, however, if you were the
creator of the dictionary. Prior to doing this, it is always advisable
to store the dictionary using the DBSTORE program which resides in the
PUB group of the SYS account. Therefore, in the event that some problem
occurs during reinitialization, you have a complete back of the current
dictionary. Refer to the TurboIMAGE Reference Manual (32215-90050) for
detailed instructions for running DBSTORE. Once the database is stored,
you must choose the Reinitialization option in response to the following
prompt in order to reinitialize the dictionary:
Initialization / Reinitialization (I/R) >
The Dictionary Password
Before you can begin reinitializing the dictionary, you must supply the
dictionary database password. This is the password which the dictionary
was given at initialization time. If you enter [[RETURN]] or if you make
a mistake when entering the old password, you will be reprompted. If you
do not enter the correct password after being prompted three times,
SDINIT automatically terminates. For security reasons, the echo will be
turned off for the response to the password prompts:
Dictionary database old password >
Once the correct old password is entered, the next prompt that appears
allows you to change the dictionary database password:
Dictionary database new password >
Verification of new password >
If you enter [[RETURN]] in response to the new password prompt, the old
password will be used. If you enter a new password and do not type in
the same password at the Verification of new password > prompt, the
following message will appear and you will again be prompted for the new
password and verification:
Verification of password failed (SDERR 2205)
The Dictionary Password
The next prompt that appears allows you to change the capacities.
Change dictionary capacities? (N/Y) >
If you want to change the existing capacities, enter "Y" , and follow the
steps under the heading "New Capacities" (next page).
If you have changed the existing password, but want to keep the existing
capacities, enter "N" or [[RETURN]], and follow the steps under the
heading "Current Capacities" (next page).
Current Capacities. At this point, if either of the files named SDTEMP1
or SDTEMP2 exists, you will be prompted for permission to overwrite them.
SDTEMP1.groupname.accountname already exists. Is it okay to overwrite (N/Y)?
SDTEMP2.groupname.accountname already exists. Is it okay to overwrite (N/Y)?
If you answer "N" to either of these prompts, SDINIT will terminate, and
the password will not be changed.
If you answer "Y" to both of these prompts, the password will be changed,
and no further user interaction will be required.
New Capacities. At this point, if the file SDPASS already exists, you
will then be prompted for permission to overwrite.
SDPASS.groupname.accountname already exists. Is it okay to overwrite (N/Y)?
If you answer "N" to this prompt, SDINIT will terminate.
The next prompt that appears allows you to specify where the current
dictionary contents will be stored while reinitialization is being done:
Dictionary store file on Tape or Disc? (T/D) >
If you have a limited amount of disc space, you may want to request
storage of the contents to tape, because the store file can be quite
large. If you do choose tape ("T" ), SDINIT uses a labeled tape which
allows MPE to manage the tape handling. This means that all messages to
mount the tape, etc., will appear on the operator's console.
If, however, you enter "D" and a file named SDRSTORE already exists,
SDINIT prompts you with:
SDRSTORE.groupname.accountname already exists. Is it okay to overwrite (N/Y)?
If you answer "N" , SDINIT will terminate. If you answer "Y" or
[[RETURN]], the following prompt will appear displaying the current
dictionary capacities (where xxx is the current capacity):
_______________________________________________________________________
| |
| Capacity for ALIASES is xxx |
| Capacity for user defined ATTRIBUTES is xxx |
| Capacity for user defined ENTITY TYPES is xxx |
| Capacity for user defined RELATIONSHIP CLASSES is xxx |
| Capacity for user defined binary RELATIONSHIP TYPES is xxx |
| Capacity for user defined N-ary RELATIONSHIP TYPES is xxx |
| Capacity for average no. attributes associated to ET & RT is xxx|
| Capacity for DOMAINS is xxx |
| Capacity for ENTITY names is xxx |
| Capacity for total versions of ENTITIES is xxx |
| Capacity for binary RELATIONSHIPS is xxx |
| Capacity for N-ary RELATIONSHIPS is xxx |
| Capacity for total versions of RELATIONSHIPS is xxx |
| Capacity for FIXED LENGTH ATTRIBUTE DATA is xxx |
| Capacity for FIXED LENGTH ATTRIBUTE EDIT DATA is xxx |
| Capacity for VARIABLE LENGTH ATTRIBUTE LINES is xxx |
| Capacity for SCOPES is xxx |
| Capacity for SCOPE/ENTITY associations is xxx |
| Capacity for SCOPE/RELATIONSHIP associations is xxx |
| Capacity for SCOPE/DOMAIN associations is xxx |
| Capacity for VERSIONS is xxx |
| Capacity for VERSION LOGGING is xxx |
| |
| Are the capacities correct? (Y/N) > |
_______________________________________________________________________
For an explanation of each of these capacity prompts, see the paragraphs
in this chapter under "Defining the Capacities."
If your answer is "N" to the prompt Are the capacities correct? (Y/N) >,
the following prompt will appear (where xxx is current 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 > |
__________________________________________________________________________
As you did when initializing the dictionary, you are now free to change
any of the capacities. You can 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 all desired changes have been made, if the file SDTEMP1 already
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 respond "N" , SDINIT will terminate.
You are now ready to submit the job stream.
Submitting the Job Stream
Once all changes are complete, the following prompt is displayed:
Input Priority of Job Stream (8) >
Specify the input priority for the job stream using a value from 1 (the
lowest priority) to 13 (the highest priority). The default priority is 8
and is entered if you hit [[RETURN]]. If, therefore, you want to defer
the job, enter a low input priority number, such as 3.
The next prompt that appears enables you to specify the output priority
of the job stream:
Output Priority of Job Stream Listing (8) >
As with the input priority, the output priority default is 8, with valid
responses of 1 (the lowest priority) to 13 (the highest priority). The
default is used if [[RETURN]] is entered.
You are now prompted for passwords at the user, group, and account
levels. If you used passwords at any of these levels when you logged on,
you must now enter them. 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 reinitialization process
If you would like to complete the reinitialization process on line
instead of in batch mode, enter:
RUN SDINIT.PUB.SYS; INFO="BUILD"; PARM=3
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)
You will receive both the MPE job number and the SDINIT job stream
message:
#J383
System Dictionary Reinitialization 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
reinitialization messages.
When the job stream begins execution, the following message will appear:
System Dictionary Reinitialization Begins
At this point, if you requested tape storage of the database, the tape
handling messages will appear on the operator's console. Refer to the
system operator's manual Storing and Restoring Files (32650-90038) for
instructions concerning these messages.
If reinitialization is completed successfully, the following message is
displayed:
System Dictionary Reinitialization Completed
In addition, an output listing which prints out a report on dictionary
capacities will be produced. If any error occurred during
reinitialization, a recovery message will be displayed at your terminal.
If, however, you do not receive a message at your terminal, check the
output listing since messages are also written to $STDLIST.
Sequence of Operations
There are three possible reinitialization changes which you may make to a
dictionary:
1) Change only the database password, 2) Change only the dictionary
capacities, and 3) Change both the password and the capacities.
If only the password is changed, reinitialization will be complete as
soon as all of the prompts are answered. If, however, either the
capacities alone, or the capacities and the password are changed, SDINIT
initiates the following sequence of operations:
1. The contents of the dictionary are unloaded.
2. The DBUTIL utility is run to purge the existing dictionary.
3. The dictionary is rebuilt with a new password and/or capacities.
4. The dictionary contents are reloaded.
Although these operations are totally transparent to you, if an error
occurs during reinitialization, the point at which it occurred determines
how you are to recover. This is explained below under the heading
"SDINIT Reinitialization Recovery" .