HP 3000 Manuals HP 3000 Manuals
The Upgrade Procedure
The System Dictionary upgrade procedure consists of the following steps.
Note that steps 5 and 6 are done only when upgrading an A.00.00 version
of the dictionary.
1. Locate all dictionaries to be upgraded.
2. Store backup copies of the dictionaries on tape.
3. Log on as the dictionary creator.
4. Run SDUPGRAD and reply to the prompts.
5. Delete any conflicting structures in each dictionary. (If
necessary.)
6. Run SDUPGRAD with INFO="CORESET". (If necessary.)
These steps are described in detail below.
Locating Dictionaries
The first step is to locate all dictionaries to be upgraded. Because the
System Dictionary database is named SYSDIC, you can easily locate all
dictionaries on a system by entering the command:
:LISTF SYSDIC.@.@,1
A sample output from the LISTF command is shown below:
ACCOUNT= ADMIN GROUP= PUB
FILENAME CODE ------------LOGICAL RECORD--------
SIZE TYP EOF LIMIT
SYSDIC PRIV 128W FB 25 25
ACCOUNT= SDUSER GROUP= RPG
FILENAME CODE ------------LOGICAL RECORD--------
SIZE TYP EOF LIMIT
SYSDIC PRIV 128W FB 25 25
:
In this example, the output shows that there are two dictionaries on the
system, one in the PUB group of the ADMIN account and one in the RPG
group in account SDUSER. Note that the SYSDIC file is an IMAGE database
root file with the file code "PRIV" .
Storing Dictionaries on Tape
The second step is to store all dictionaries that are to be upgraded on a
backup tape. This should be done before running SDUPGRAD.
WARNING If SDUPGRAD fails during the upgrade process, you may not be
able to recover the dictionary except from a backup tape.
You can make backup copies of all the dictionaries on a system by
entering the following commands:
:FILE T; DEV=TAPE
:STORE SYSDIC@.@.@;*T
Note that the at-signs (@) in SYSDIC@.@.@ cause the :STORE command to
capture all the System Dictionary files in all groups and accounts on the
system. For more information on the :STORE command, refer to the MPE XL
Commands Reference Manual (32650-90003).
Logging On
The third step is to log on as the creator of the dictionary that will be
upgraded. It is necessary to log on as the dictionary creator because
the TurboIMAGE subsystem which is called by the SDUPGRAD procedure to
purge and recreate the SYSDIC database will only allow that database to
be purged by its creator. For example, if the dictionary was created in
the PUB group of the ADMIN account by the user MGR, you must log on as
MGR.ADMIN,PUB.
SDUPGRAD does not prompt you for a dictionary name. It automatically
accesses the dictionary named SYSDIC in the logon group and account.
Running SDUPGRAD
The fourth step, after logging on to the appropriate group and account,
is to run SDUPGRAD and respond to a series of prompts.
The RUN Command. To run SDUPGRAD, enter the command:
:RUN SDUPGRAD.PUB.SYS
SDUPGRAD then displays the following banner:
HP System Dictionary SDUPGRAD HP32256v.uu.ff - (C) Hewlett-Packard Co. 1985
SDUPGRAD Prompts. SDUPGRAD first prompts to determine if a backup copy
of the dictionary has been stored on tape:
Has a backup for SYSDIC been made? (N/Y) >
If you reply "NO" to this prompt, SDUPGRAD will terminate.
NOTE Hewlett-Packard strongly recommends that you back up your
dictionary before running SDUPGRAD, as the program does not do a
backup for you. It simply gives you the opportunity to stop and
back up your dictionary before upgrading it. If SDUPGRAD fails,
there may be no way to recover your dictionary except from a backup
tape.
SDUPGRAD next prompts for the password of the Dictionary Administrator
scope:
DA scope password > (Password will not be echoed to the screen)
If you fail to supply the correct password after three tries, SDUPGRAD
will terminate. For security reasons, SDUPGRAD does not echo the
password to the list device. SDUPGRAD then prompts for the desired store
file medium:
Store file to tape or disc? (T/D) >
The store file is used for temporary storage of the dictionary contents
during the upgrade process. If you enter "D" (disc) for the storage
medium, SDUPGRAD will create an unnamed new file for the store file. If
you enter "T" (tape), SDUPGRAD will instruct you to mount a tape and
reply at the console. SDUPGRAD will issue a console request using the
tape file name STORE.
If there is a shortage of disc space in the group, account, or system
where the dictionary resides, you should select "TAPE" for the store
file.
Upgrade Operation. After you respond to the prompts, SDUPGRAD begins the
upgrade operation. The contents of your dictionary are unloaded to the
store file on tape or disc, as you specified. Two messages are displayed
during the unloading operation:
System Dictionary Unloading Begins
System Dictionary Unloading Ends
Next, SDUPGRAD purges the dictionary database (SYSDIC) and creates a new
one. The new database will have expanded capacities to accommodate the
new core set if upgrading a version A.00.00 dictionary. SDUPGRAD invokes
the TurboIMAGE utility DBSCHEMA, which displays these messages:
HP32215v.uu.ff
NUMBER OF ERROR MESSAGES: 0
ROOT FILE SYSDIC CREATED
SDUPGRAD then loads the contents of the store file into the expanded
dictionary. Two messages are displayed during the loading operation:
System Dictionary Loading Begins
System Dictionary Loading Ends
If upgrading a version A.00.00 dictionary, SDUPGRAD next adds the core
set extensions listed in Table 1-1 through Table 1-4. During the core
set additions, these messages are displayed:
System Dictionary Core Set Additions Begins
New edit values added to attribute CONSTANT-TYPE
New edit values added to attribute ELEMENT-TYPE
New edit values added to attribute FILE-TYPE
New edit values added to attribute IMAGE-DATABASE-TYPE
New edit values added to attribute IMAGE-DATASET-TYPE
System Dictionary Core Set Additions Ends
When an upgrade from a version A.00.00 dictionary is complete, SDUPGRAD
displays these messages:
Core Set Attributes Added : 21
Core Set Entity Types Added : 9
Core Set Relationship Classes Added : 0
Core Set Relationship Types Added : 29
Core Set Domains Added : 0
The dictionary is now ready for use. The upgraded dictionary can be used
with existing System Dictionary applications and utilities. You can also
modify their applications to use the new core set definitions for HPSQL,
HPIMAGE, or COBOL Level 88, if desired.
SDUPGRAD Example
A sample SDUPGRAD session is shown below. In this example, the user
replied "YES" to the backup prompt. The user then entered (but SDUPGRAD
did not echo) the password of the Dictionary Administrator scope. The
user then chose disc storage as the store file medium. Note that the
first three lines after the banner are prompts requiring responses from
the user. The rest is program output.
:run sdupgrad.pub.sys
HP System Dictionary SDUPGRAD HP32256v.uu.ff -(C) Hewlett-Packard
Co. 1985
Has a backup for SYSDIC been made? (N/Y) > y
DA scope password > (Password will not be echoed to the screen)
Store file to tape or disc? (T/D) > d
System Dictionary Unloading Begins
System Dictionary Unloading Ends
HP32215v.uu.ff
NUMBER OF ERROR MESSAGES: 0
ROOT FILE SYSDIC CREATED.
System Dictionary Loading Begins
System Dictionary Loading Ends
The following information will be sent to the screen only if upgrading
from a version A.00.00 dictionary.
System Dictionary Core Set Additions Begins
New edit values added to attribute CONSTANT-TYPE
New edit values added to attribute ELEMENT-TYPE
New edit values added to attribute FILE-TYPE
New edit values added to attribute IMAGE-DATABASE-TYPE
New edit values added to attribute IMAGE-DATASET-TYPE
System Dictionary Core Set Additions Ends
Core Set Attributes Added : 21
Core Set Entity Types Added : 9
Core Set Relationship Classes Added : 0
Core Set Relationship Types Added : 29
Core Set Domains Added : 0
END OF PROGRAM (Will always be sent to the screen.)
:
Conflicting Structures
NOTE This step is required only when upgrading a version A.00.00
dictionary. Skip this step if your dictionary is version A.00.01
or later.
The purpose of this step is to delete all existing structures which have
the same names as any structures which will be added to the dictionaries
by the upgrade procedure. These include customized entity types,
relationship types, or attributes that conflict with the new additions to
the core set which are listed in Table 1-1 through Table 1-4.
You may also need to delete additional custom definitions from a
dictionary if it contains nearly the maximum number of entity types,
relationship types, or attributes allowed.
Information on deleting attributes and entity types is located in the
descriptions of the DELETE ATTRIBUTE and DELETE ENTITY-TYPE commands in
the HP System Dictionary/XL SDMAIN Reference Manual, (32256-90001).
NOTE Any relationship types in the dictionary which are listed in Table
1-2 will automatically be deleted when the entity types listed in
Table 1-1 are deleted.
Deleting an entity type or relationship type causes all entities or
relationships of that type to be deleted also.
The REPORT ENTITY and REPORT RELATIONSHIP commands may be used to get a
listing of those entities and relationships which belong to specific
entity types or relationship types. These reports can be sent to the
line printer to keep a record of these entities or relationships. There
are two reasons for deleting the conflicting definitions:
1. System Dictionary maintains two sets of internal numbers, one for
the core set and one for user customizations. User customized
definitions that match any of the structures in Table 1-1 through
Table 1-3 must be deleted so that the internal numbers will be
consistent for all dictionaries.
2. Hewlett-Packard reserves the prefix "HP" for extensions to the
core set. To ensure that your dictionary can be upgraded in
future versions, do not use the prefix "HP" when creating
customized entity types, relationship classes, attributes, scopes,
or domains.
Making Room For the Core Set. The maximum number of entity types,
relationship types, and attributes allowed in System Dictionary are
listed in Table 2-1.
Table 2-1. System Dictionary Maximums
-----------------------------------------------------------------------------
| Dictionary Structures | Added in A.00.02 | Maximum |
-----------------------------------------------------------------------------
| Attributes | 21 | 1024 |
| Entity Types | 9 | 256 |
| Relationship Types | 29 | 512 |
-----------------------------------------------------------------------------
In the unlikely event that a dictionary is already approaching any of
these limits, you may have to delete some of the entity types,
relationship types, or attributes to make room for the new core set. The
"Added" column in table 1-5 indicates the number of new structures that
will be added by SDUPGRAD. If this number causes one of the maximums to
be exceeded, SDUPGRAD will terminate with an error.
SDUPGRAD appends new attribute edit values to the edit lists of certain
existing core set attributes (see Table 1-4). The edit list of an
attribute cannot exceed 256 bytes. Thus, if an attribute has a byte
length of 8, it can have up to 32 edit values. If you have added a large
number of edit values to any of the attributes in Table 1-4, some of them
may have to be deleted to make room for the new core set edit values. To
determine an attribute's byte length and number of edit values, use the
DISPLAY ATTRIBUTE command as described in the HP System Dictionary SDMAIN
Reference Manual (32256-90001).
Running With INFO='CORESET'
SDUPGRAD includes an INFO option that allows a dictionary upgrade to be
resumed after an error condition has been encountered and corrected.
When to Use the Info Option. SDUPGRAD will fail if it encounters any of
these conditions:
* The dictionary contains structures that conflict with the new core
set (SDERR 5306, 5307, 5310, or 5311).
* The addition of the new core set structures would exceed one of the
dictionary maximums listed in Table 2-1, or would cause an attribute
edit list to exceed 256 bytes (SDERR 5321, 5322, 5323, or 5325).
For each of these error conditions, the recommended action is to correct
the problem and continue the upgrade by running SDUPGRAD with
INFO="CORESET" .
WARNING Do not run SDUPGRAD with INFO="CORESET" unless you encounter one
of the errors mentioned above. Other uses of the INFO option
may cause SDUPGRAD to fail. After the failure the dictionary
may only be recoverable from a backup tape.
How to Use the INFO Option. To run SDUPGRAD with the INFO="CORESET"
option, enter the command:
:RUN SDUPGRAD.PUB.SYS;INFO="CORESET"
When INFO="CORESET" is invoked, SDUPGRAD simply loads the new core set
structures into the existing dictionary database "as is." No attempt is
made to expand the dictionary capacities, since this was already done in
the previous SDUPGRAD run (before it encountered the error).
INFO='CORESET' Example
The following example shows a sample SDUPGRAD session using
INFO="CORESET" , and upgrading a version A.00.00 dictionary.
:RUN SDUPGRAD.PUB.SYS;INFO="CORESET"
HP System Dictionary SDUPGRAD HP32256v.uu.ff -(C) Hewlett-Packard
Co. 1985
DA scope password > (Password will not be echoed to the screen)
System Dictionary Core Set Additions Begins
New edit values added to attribute CONSTANT-TYPE
New edit values added to attribute ELEMENT-TYPE
New edit values added to attribute FILE-TYPE
New edit values added to attribute IMAGE-DATABASE-TYPE
New edit values added to attribute IMAGE-DATASET-TYPE
System Dictionary Core Set Additions Ends
Core Set Attributes Added : 21
Core Set Entity Types Added : 9
Core Set Relationship Classes Added : 0
Core Set Relationship Types Added : 29
Core Set Domains Added : 0
END OF PROGRAM
:
Note that you are required to make only one entry: the scope password of
the Dictionary Administrator. When you enter the correct password,
SDUPGRAD proceeds with the core set upgrade.