HP 3000 Manuals HP 3000 Manuals
Utility Program Operation (contd)
>>DISABLE
Disables the access, automatic deferred output, data prefetching,
dumping, ILR, indexing, MUSTRECOVER, logging, and recovery options.
Syntax.
>>DI[SABLE] database name[/maint word] FOR option[,option...]
For example:
DISABLE ORDERS FOR LOGGING,RECOVERY
where ORDERS is the database name, and LOGGING and RECOVERY are the
options.
Parameters.
database name is the name of a TurboIMAGE/XL database root file
created in the current session or job's account and
logon group.
maint word is the maintenance word defined by the database
creator when the database is created with DBUTIL.
This word must be supplied by anyone other than the
database creator.
option is an option from the list provided and described
below. More than one option can be specified.
Options.
ACCESS disables user access to the database.
AUTODEFER disables automatic deferred output for the
database. AUTODEFER must be disabled if ILR or
roll-back recovery is to be enabled for a database.
DSEM disables the use of Dependency Semaphore employed
to increase concurrency of modification intrinsics
(DBPUT, DELETE, and DBUPDATE with CIU ON).
DUMPING disables the automatic dumping of the user's stack
and the database control block in the event of a
TurboIMAGE/XL abort. Unless requested by
Hewlett-Packard support representatives, under most
circumstances dumping should be disabled. When
enabled, DUMPING creates files (before
TurboIMAGE/XL aborts) that can prove helpful in
determining the cause of such problems as a
corrupted control block.
HWMPUT disables DBPUT action of placing entries at the
high-water mark first, instead of at the delete
chain head.
ILR disables Intrinsic Level Recovery facility.
INDEXING disables third-party indexing (TPI) for the
database. Third-party indexing provides the
capability to do generic key searches, multiple
keyword retrievals, and sorted sequential searches
on any database. Refer to your vendor
documentation for information on TPI.
LOGGING disables the database roll-forward logging
facility. Roll-back and MUSTRECOVER must be
disabled first.
MUSTRECOVER disables the MUSTRECOVER option for the database.
Logging is not affected by disabling MUSTRECOVER.
If the database needs recovery when you disable
MUSTRECOVER, you are prompted to confirm the
DISABLE command. If you respond to continue, the
consistency of the database cannot be guaranteed.
To ensure database consistency, respond with N,
recover the database, and then disable MUSTRECOVER
after recovering the database.
PREFETCH disables the prefetching of data blocks required by
the DBPUT and DBDELETE intrinsics under certain
conditions. Refer to "Coordinating Additions to a
Database" or "Coordinating Deletions from a
Database" in chapter 4 for additional information.
RECOVERY disables the database roll-forward recovery
facility.
ROLLBACK disables the database roll-back logging facility.
However, logging will not be automatically
disabled. To disable logging, use the >> database
name FOR LOGGING command. Otherwise, logging
(roll-forward) will remain enabled.
Default Conditions.
Access is Enabled
Autodefer is Disabled
Dumping is Disabled
HWMPUT is Disabled
ILR is Disabled
Indexing is Disabled
Logging is Disabled
Mustrecover is Disabled
Prefetch is Disabled
Recovery is Disabled
Roll-Back is Disabled
Example.
:RUN DBUTIL.PUB.SYS
:
>>DISABLE ORDERS FOR ACCESS
Access is Disabled
>>
>>DROPINDEX
[REV BEG]
The DROPINDEX command drops the associated B-Tree index file and updates
the root file. When using the ALL option and there is no master dataset,
a warning is generated, but the command is considered to be successful.
Syntax.
{ALL }
>>DROPI[NDEX] database name [/maintword] FOR { setnamelist}
{setnumlist }
For example:
>>DROPINDEX ORDERS FOR 2
where ORDERS is the database name and 2 is set# 2.
Parameters.
database name is the name of a TurboIMAGE/XL database.
maintword is the maintenance password.
setnamelist is the name of the set list.
setnumlist is the number of the set list.
ALL means all master data sets for the database.
Example.
>>DROPINDEX ORDERS/secret FOR 2
Dropping index from set# 2 (#entries = 84,164, capacity = 188,517)
Done.
[REV END]
>>ENABLE
Enables the access, automatic deferred output, data prefetching, dumping,
ILR, indexing, MUSTRECOVER, logging, and recovery options.
Syntax.
>>EN[ABLE] database name[/maint word] FOR option[,option...]
For example:
ENABLE RETAIL FOR LOGGING
where RETAIL is the database name and LOGGING is an option.
Parameters.
database name is the name of a TurboIMAGE/XL database being
enabled.
maint word is the maintenance word defined by the database
creator when the database is created with DBUTIL.
This word must be supplied by anyone other than the
database creator.
option is an option from the list provided and described
below. More than one option can be specified.
Options.
ACCESS enables user access to the database.
AUTODEFER enables automatic deferred output for the database.
With deferred output the MPE/iX transaction manager
is not used to log database modifications to the
transaction manager log file. Instead, AUTODEFER
uses the MPE/iX file system default mode. This
mode keeps data pages in memory for as long as
possible until either lack of memory or the closing
of a file causes the pages to be written to disk.
In this mode a system failure can cause the loss of
database integrity. ILR is not compatible with
AUTODEFER; therefore, deferred output should be
used only in a batch situation where the database
has been backed up prior to batch processing. ILR
must be disabled prior to enabling AUTODEFER.
AUTODEFER can be used to increase I/O performance
by disabling Transaction Management (XM). However,
ILR and roll-back recovery must be disabled. You
must consider performance and the ability to
recover data when determining whether to use
AUTODEFER. Roll-forward logging can be used to
preserve consistency.[REV BEG]
DSEM enables use of Dependency Semaphore for increased
concurrency of modification intrinsics (DBPUT,
DELETE, and DBUPDATE with CIU ON).[REV END]
DUMPING is an option for Hewlett-Packard support use,
development, and debugging only. When enabled, the
TurboIMAGE/XL abort procedure copies the user's
stack and the database control blocks to files if a
TurboIMAGE/XL procedure aborts.
HWMPUT enables DBPUT action of placing entries at the
high-water mark first, instead of at the delete
chain head.
ILR enables the Intrinsic Level Recovery facility.
TurboIMAGE/XL maintains structural integrity
without ILR enabled.
INDEXING enables third-party indexing (TPI) for the database
if not already done by the third-party software
when configuring the database for TPI. Third-party
indexing provides the capability to do generic key
searches, multiple keyword retrievals, and sorted
sequential searches on any database. Refer to your
vendor documentation for information on TPI.
LOGGING enables the database roll-forward logging facility.
MUSTRECOVER enables the MUSTRECOVER option for the database.
If logging is not already enabled, it is
automatically enabled when MUSTRECOVER is enabled.
While MUSTRECOVER is enabled, the database cannot
be accessed after a system failure until the
database is recovered with roll-forward or
roll-back recovery.
PREFETCH enables the prefetching of data blocks required by
the DBPUT and DBDELETE intrinsics under certain
conditions. Refer to "Coordinating Additions to a
Database" or "Coordinating Deletions from a
Database" in chapter 4 for additional information.
RECOVERY enables the database for recovery.
ROLLBACK enables the database roll-back logging facility. A
warning displays if the log file does not exist,
and the database remains disabled for roll-back
recovery. If logging is not in effect already, it
will be enabled automatically.
Default Conditions.
Access is Enabled
Autodefer is Disabled
Dumping is Disabled
HWMPUT is Disabled
ILR is Disabled
Indexing is Disabled
Logging is Disabled
Mustrecover is Disabled
Prefetch is Disabled
Recovery is Disabled
Roll-Back is Disabled
Example.
:RUN DBUTIL.PUB.SYS
:
>>ENABLE ORDERS FOR RECOVERY
Recovery is Enabled
>>
>>ERASE
Reinitializes all data sets in the database to their empty condition and
resets all flags except the access, PREFETCH, and recovery flags (refer
to the discussion of the DBUTIL >>ENABLE command earlier in this
chapter).
The data sets remain as catalogued MPE/iX files. To execute DBUTIL to
reinitialize the data sets, you must be the database creator or supply
the correct maintenance word. This utility function should be performed
before data that was saved by DBUNLOAD is loaded back into the database
unless it was re-created.
After DBUTIL has completely reinitialized the data sets, it prints a
confirmation message on the list file device.[REV BEG]
NOTE The ERASE command erases any associated B-Tree index (.idx) files,
but will not delete them.
[REV END]
Syntax.
>>ER[ASE] database name [/maint word]
For example:
ERASE ORDERS/SELL
where ORDERS is the database name and SELL is the maint word.
Parameters.
database name is the name of a TurboIMAGE/XL database being
erased.
maint word is the maintenance word defined by the database
creator when the database is created with DBUTIL.
This word must be supplied by anyone other than the
database creator.
Example.
:RUN DBUTIL.PUB.SYS Initiate DBUTIL execution.
:
>>ERASE ORDERS/SELL Enter >>ERASE command, database name, and maintenance word.
Database ORDERS has been ERASED
>>
DBUTIL reinitializes all the data sets in the ORDERS database to binary
zeroes. With the exception of the access, PREFETCH, and recovery flags,
the database flags are reset to their default conditions. The logging
and MUSTRECOVER options are disabled if they were previously enabled.
NOTE The execution of utilities is not logged. If you use DBUTIL to
erase the database, the >>ERASE command automatically disables
logging, ILR, third-party indexing, MUSTRECOVER, and roll-back
recovery.
>>EXIT
Terminates DBUTIL execution.
Syntax.
>>E[XIT]
Example.
>>CREATE ORDERS Create a database.
Database ORDERS has been CREATED
>>EXIT
If no other DBUTIL functions are to be performed, terminate DBUTIL with >>EXIT command.
END OF PROGRAM
>>HELP
Displays each of the DBUTIL commands.
>>H[ELP] [commandname]
Parameter.
commandname is the name of a specific DBUTIL command whose
format you want to display. The name can be
abbreviated to the minimum command abbreviation
permitted by DBUTIL.
If you do not specify a command, the >>HELP command
lists the names of all valid DBUTIL commands.
If you specify a command, the correct syntax for
that command is displayed.
Example. [REV BEG]
>>HELP
Commands are:
ACTIVATE ADDINDEX CREATE DEACTIVATE DETACH
DISABLE DROPINDEX ENABLE ERASE EXIT
HELP MOVE PURGE REBUILDINDEX RELEASE
SECURE SET SHOW VERIFY REDO
Commands may be abbreviated.
For help on a particular command type: 'HELP command name'.
>>HELP CREATE
C[REATE] database name [/maint word]
>>
[REV END]
>>MOVE
Moves TurboIMAGE/XL files across devices within the same volume set.
Syntax.
>>M[OVE] TurboIMAGE/XL file name TO device
For example:
MOVE ORDERS05 to DISC2
where ORDERS05 is the file name and DISC2 is a device.
Parameters.
file name is a TurboIMAGE/XL root file, data set, or ILR
file. Enter the file name only; no group/account
specification is allowed. The user must be the
creator of the file.
device is the class name of the MPE/iX device or the
number of the logical device to which the
TurboIMAGE/XL file should be moved. The device
must be a member of the volume set on which the
database resides.
Discussion.
It is recommended that you store the database with the DBSTORE command
prior to executing a MOVE command. This precaution is advisable in the
event a system failure occurs during the move operation. When a move has
been initialized, the process checks the root file flag to determine if
the database has been modified since the last backup copy was made. The
program prompts the user to continue or to terminate the MOVE command and
proceed with a DBSTORE of the database before moving TurboIMAGE/XL files
to another device. If the user responds NO to the continue prompt, the
following message is printed on the terminal:
MOVE operation stopped.
The following steps outline the process involved in moving TurboIMAGE/XL
files from one device to another. The move process does the following:
1. Retrieves information from the old file. Old indicates the file
on the originally specified device.
2. Checks the device specified by the user for validity and
existence, and determines if there is sufficient space for the new
file. (New indicates the file being moved to another device.)
3. Checks the root file to determine the database state.
4. Copies the old file to the new file.
5. Sets the flag in the root file.
6. Purges the old file, then saves the new file.
7. Resets the flag in the root file.
[REV BEG]
For jumbo datasets, the MOVE command enables you to move either the chunk
control file or a specific chunk data file to a different device.
The MOVE command does not allow a B-Tree index (".idx") file to be
moved.[REV END]
Example.
>>MOVE ORDERS05 to 3
Database last stored on FRI, SEP 22, 1989, 8:32 PM
Database has been modified since last store date.
The database should be backed up before doing a MOVE operation.
Do you still want to continue the MOVE operation (Y/N)? Y
Starting file copy ...
... file copy completed.
Purging old copy of file "ORDERS05"
New copy of file "ORDERS05" saved as a permanent file
File "ORDERS05" moved to device 3
The data set ORDERS05 has been moved to logical device number 3. This
file is the INVENTORY data set and was originally assigned device class
named DISC2 in the schema.
To obtain a listing of where all the data sets for the database reside,
do a
>>SHOW ORDERS DEVICE
>>PURGE
Purges the root file and all the data sets of the referenced database.
If you use third-party indexing, the >>PURGE command also purges any
existing third-party index files regardless of third-party indexing being
enabled or disabled.
Purging removes the files from the catalog and returns the disk space to
the system. As with >>ERASE, you must be the database creator or must
provide the maintenance word to use DBUTIL with the >>PURGE entry.
Before running the DBRESTOR program to restore a database, use this
utility function to purge the database.
If DBUTIL successfully purges the database, it prints a confirmation
message on the list file device.
[REV BEG]
NOTE The PURGE command purges any associated B-Tree index (.idx) files.
[REV END]
Syntax.
>>P[URGE] database name [/maint word] [DETACH]
For example:
PURGE ORDERS/SELL
where ORDERS is the database name and SELL is the maint word.
Parameters.
database name is the name of a TurboIMAGE/XL database being
purged.
maint word is the maintenance word defined by the database
creator when the database is created with DBUTIL.
This word must be supplied by anyone except the
database creator when using DBUTIL to access the
database.[REV BEG]
DETACH is an option specific to the IMAGE/SQL users. This
option detaches the database from all ALLBASE/SQL
database environments (DBEnvironments) to which it
is attached via IMAGESQL. When DETACH is not used,
the database is purged without detaching from the
DBEnvironment(s). For more information, refer to
the IMAGE/SQL Administration Guide.[REV END]
Unexpected Results
The following messages are printed if an unexpected situation occurs
(refer to appendix A for other error messages):
-----------------------------------------------------------------------------------------------------
| | |
| Message | Meaning |
| | |
-----------------------------------------------------------------------------------------------------
| | |
| No root file, >>PURGE operation | DBUTIL was unable to locate the root file, but will |
| proceeding | attempt to purge data set, if any. |
| | |
-----------------------------------------------------------------------------------------------------
| | |
| Data set XXXXk has been purged | DBUTIL successfully purged the root file and the n |
| | data sets of the database. However, DBUTIL also |
| | discovered and purged an unexpected data set named |
| | XXXXk, where k is a number greater than the number |
| | of data sets defined for the database (n). |
| | |
| Data set XXXXk is missing | DBUTIL successfully purged the root file and all |
| | existing data sets but data set XXXXk is |
| | unexpectedly missing. In this case k is less than |
| | the number of data sets defined for the database. |
| | |
-----------------------------------------------------------------------------------------------------
| | |
| Incomplete purge | An error occurred while DBUTIL was attempting to |
| | purge the database and any Third-party indexing |
| | files. The specific error message is printed above |
| | this one. Some of the data sets and, if |
| | applicable, index files have been purged. |
| | |
-----------------------------------------------------------------------------------------------------
| [REV BEG] | |
| | |
| Detach failed from DBEname | This message is returned if you are using |
| | IMAGE/SQL. DBUTIL was unable to detach the |
| | TurboIMAGE/XL database from the ALLBASE/SQL |
| | database environment (DBEnvironment) to which it |
| | was attached. However, DBUTIL will continue |
| | executing the >>PURGE command. For more |
| | information, refer to the IMAGE/SQL Administration |
| | Guide.[REV END] |
| | |
-----------------------------------------------------------------------------------------------------
Example.
:RUN DBUTIL.PUB.SYS Initiate DBUTIL execution.
:
>>PURGE ORDERS Enter >>PURGE command and database name assuming there is no maintenance word.
[REV BEG]
The next messages are returned if you are using IMAGE/SQL, and the DETACH
option is used with the >>PURGE command.[REV END]
Database has been detached from these HP SQL DBEnvironments:
DBEname.group.account
DBEname.group.account
Database has been PURGED
DBUTIL confirms that the user is logged on with the same user name,
account, and group which were used to create the database. It then
determines whether the root file exists and if so, purges the root file
and any files named ORDERS01, ORDERS02, and so forth. Even if the root
file does not exist, any data sets with file names based on the root file
name are purged.
>>REBUILDINDEX
[REV BEG]
REBUILDINDEX rebuilds the B-Tree index file for a specified dataset that
should have an index file.
When using the ALL option and there is no master dataset, a warning is
generated, but the command is considered to be successful.
The KSAM file built by REBUILDINDEX has the Native Language Support
language specified to match the language of the database, if the key is a
text (X or U) data type.
Syntax.
{ALL }
>>REBUILDI[NDEX] database name [/maintword] FOR {setnamelist}
{setnumlist }
For example:
REBUILDINDEX ORDERS FOR 3
where ORDERS is the database name, and 3 is set# 3.
Parameters.
database name is the name of a TurboIMAGE/XL database.
maintword is the maintenance password.
ALL means all master data sets for the database.
setnamelist is the name of the set list.
setnumlist is the number of the set list.
Example 1.
>>REBUILDINDEX ORDERS/secret FOR SalesrepName,Region,District
Example 2.
>>REBUILDINDEX ORDERS/secret FOR 3
Rebuilding index for set# 3 (#entries = 18,784, capacity = 21,943)
Done.
[REV END][REV BEG]