HP 3000 Manuals HP 3000 Manuals
Utility Program Operation (contd.)
>>REDO
Redo the previous command or the previous nth command. Redo follows
exactly the MPE/iX REDO syntax. REDO, LISTREDO, and DO work for DBUTIL
the same was as the MPE/iX commands.
Syntax.
>>REDO [n]
For example:
>>REDO 8
where 8 is the eighth previous command.
Parameter.
n is the backwards count of the command being
repeated.
[REV END]
>>RELEASE
Suspends file system security provisions for the database root file and
data sets, allowing access to the database from other groups and
accounts. If you use third-party indexing, the >>RELEASE command
suspends the file system security provisions for any existing index
files.
Syntax.
>>R[ELEASE] database name
For example:
RELEASE ORDERS
where ORDERS is the database name.
Parameter.
database name is the name of a TurboIMAGE/XL database.
Discussion.
The >>RELEASE command suspends file system security provisions for all of
the database files at the file, group, and account levels, but leaves
TurboIMAGE/XL security and MPE/iX privileged file security intact.
Releasing the file system security allows the database to be accessed by
users from other groups and accounts, without relinquishing the privacy
of all other files in the database group. Only the creator of the
database can release security. In addition, the group's home volume set
must be mounted.
The database file security remains suspended until the creator issues a
>>SECURE command. Suspension remains valid after job termination, or
system failure followed by a system boot.
[REV BEG]
The RELEASE command applies to the associated B-Tree index (.idx) files.
[REV END]
>>SECURE
Restores security provisions that were released by a >>RELEASE command
for the database root file and data sets. If you use third-party
indexing, the >>SECURE command restores the security provisions for any
existing index files.
Syntax.
>>SE[CURE] database name
For example:
>>SECURE ORDERS
where ORDERS is the database name.
Parameter.
database name is the name of a TurboIMAGE/XL database being
secured.
Discussion.
The >>SECURE command reinstates the file system security provisions for
the entire database. These security provisions can only be suspended by
the >>RELEASE command. Only the creator of the database can successfully
issue the >>SECURE command. In addition, the group's home volume set
must be mounted.
[REV BEG]
The SECURE command applies to the associated ".idx" files.
[REV END]
>>SET
Changes or removes the maintenance word; only the database creator can
change or remove the maintenance word. The >>SET command also sets the
log identifier into the root file, modifies access class passwords, sets
a subsystem flag, and sets the critical item update (CIUPDATE) option.
For databases that will be migrated to MPE V, the >>SET command specifies
the number of input/output buffers to be allocated by TurboIMAGE in the
Database Buffer Area Control Block (DBB) depending on the number of users
concurrently accessing the database.
Syntax. [REV BEG]
>>SET database name [/maint word]
{BUFFSPECS=num buffers (from-users/ to-users)}
{ [,num buffers(from-users/to-users)]... }
{LOGID=log identifier }
{MAINT=maintenance word }
{ {NONE} }
{SUBSYSTEMS={READ} }
{ {RW } }
{ }
{PASSWORD classnum=[password] }
{LANGUAGE=language id }
{ {DISALLOWED} }
{CIUPDATE={ALLOWED } }
{ {ON } }
{ }
{BTREEMODE1={ON } [,[WILDCARD=]c] }
{ {OFF} }
[REV END]
For example:
SET ORDERS MAINT=SELL
or
SET ORDERS/SELL CIUPDATE=DISALLOWED
where ORDERS is the database name and SELL is the maintenance word.
Parameters.
database name is the name of a TurboIMAGE/XL database root file
catalogued in the current session or job's account
and logon group.
maint word is the current maintenance word for the database,
and must be given by anyone using DBUTIL to access
the database other than the database creator.
BUFFSPECS is for MPE V compatibility only, because the
TurboIMAGE/XL buffer specifications are fixed. For
databases that will be migrated to MPE V, it sets
the number of buffers to be allocated by TurboIMAGE
in the Database Buffer Area `Control Block (DBB).
Refer to "Moving from MPE/iX to MPE V" in appendix
H for a discussion of BUFFSPECS and a description
of its parameters.
LOGID sets the MPE/iX log identifier. The log identifier
is obtained using the MPE/iX GETLOG command. Note
that DBUTIL prompts for the logid password
specified in the GETLOG command before it checks
the validity of the log identifier. Entry of the
correct logid password causes the valid log
identifier to be stored in the root file and used
whenever the logging capability is enabled.
However, if the log identifier is left blank, it is
removed from the database.
MAINT sets the maintenance word for the database. The
maintenance word is the new maintenance word for
the database. If omitted, the currently defined
maintenance word is removed and the database has no
maintenance word. Only the database creator can
change or remove the maintenance word.
SUBSYSTEMS sets subsystem access to the database. The
following options are valid:
NONE is the option used to
prohibit use of any subsystem
(for example, QUERY) on
TurboIMAGE/XL.
READ is the option that allows
only read access to the
database by subsystems. The
subsystem checks the root
file flag to determine what
access a subsystem is
allowed.
RW is the option that allows
read/write access to the
database by subsystems. The
subsystem checks the root
file flag to determine what
access a subsystem is
allowed.
PASSWORD sets the password. The following parameters are
used with the PASSWORD parameter.
classnum is the access class whose
password is being changed.
It can be a number from 1 to
63, inclusive.
password is the new password being
assigned to a particular
access class. Up to 8
characters are allowed. If
omitted, any password
previously assigned to that
class is removed. (You must
be the database creator.)
LANGUAGE sets the native language for the database. The
following parameter is used with the LANGUAGE
parameter:
language id is the number that identifies
the native language. Refer
to the Native Language
Support Programmer's Guide
for name and number
information. The message
"Language changed" appears
after using the >>SET command
to change the language ID.
This command can be issued
only on a virgin root file or
an empty database.[REV BEG]
____________________________
NOTE When reloading the
database, the language
must match the language
ID stored in the backup
media. A DBLOAD issued
in a job fails if the
language of the media
differs from the
database language. A
DBLOAD in session mode
provides a prompt to
allow you to complete
the DBLOAD operation
when you reply Y.
____________________________
[REV END]
CIUPDATE sets critical item update for the database. The
following option settings are valid:
[REV BEG]
DISALLOWED prevents any process from
using the critical item
update option on this
database.[REV END]
[REV BEG]
ALLOWED indicates that programmatic
enabling of the option is
possible through a call to
DBCONTROL mode 5, but
programs that do not make
this call are prevented from
using critical item update on
this database. Programs that
enable the option do so
temporarily for the duration
of the process but can
subsequently disable it
through a call to DBCONTROL
mode 6.
____________________________
NOTE ALLOWED is now the
default setting. It
was DISALLOWED in
releases prior to
C.07.00.
____________________________
[REV END]
ON allows all processes to use
the critical item update
option on this database
without the need to call
DBCONTROL mode 5. Any
process can explicitly
disable the option
temporarily for the duration
of the process through a call
to DBCONTROL mode 6 but can
subsequently enable it
through a call to DBCONTROL
mode 5. This setting allows
the critical item update
option to be disabled in
selected programs while
enabling it for the majority.
Critical item update is useful for those processes
that need to update the values of detail data set
search or sort items; master data set key items
cannot be updated regardless of the CIUPDATE
setting.
[REV BEG]
BTREEMODE1 sets the root file flag for B-Trees to ON or OFF.
If it is ON, then a DBFIND mode 1 on ASCII types
having a B-Tree index (explicit or implicit) and
having the wildcard character in the argument will
be treated as a B-Tree search. If set to OFF, then
a DBFIND mode 1 will not be treated as a B-Tree
search, even if the item has a B-Tree. See chapter
11, "B-Tree Indices," for more detailed information
on BTREEMODE1.
WILDCARD is set with any printable ASCII character for c.
When doing a B-Tree DBFIND, mode-1-style arguments
are scanned to find the first occurrence of the
current wildcard character in the argument text.
If the wildcard is not found, a non- B-Tree search
is done (even if the DBFIND mode was 21). If the
wildcard is found, the rest of the argument text is
ignored.
__________________________________________________
NOTE This does not match the functionality of "@"
in commands such as the MPE LISTF, but does
match the functionality of current TPI
implementations.
__________________________________________________
If the wildcard character is found at character k+1
(1-based), then the qualified entries will consist
of all keys that match the argument in character
positions 1..k.
When not doing a B-Tree find (even when mode=1 and
BTREEMODE1=ON; or mode=10), the entire argument,
including any wildcard characters, will be treated
as the actual argument for a DBFIND mode 1.
The length of the argument may not exceed the item
length.[REV END]
Example 1.
:RUN DBUTIL.PUB.SYS Initiate DBUTIL execution.
:
>>SET ORDERS MAINT Remove current maintenance word.
Maintenance word changed
>>
Example 2. [REV BEG]
:RUN DBUTIL.PUB.SYS Initiate DBUTIL execution.
:
>>SET ORDERS CIUPDATE=ON Indicates that processes can update the values of detail data set search or sort items in the
ORDERS database without a need to do DBCONTROL mode 5.
CIUPDATE is ON. DBUTIL confirms the setting.
[REV END][REV BEG]
Example 3.
:RUN DBUTIL.PUB.SYS Initiate DBUTIL.
:
>>SET ORDERS BTREEMODE1 = ON,% Sets BTREEMODE1 option on for B-Tree search for DBFIND mode 1 on X or U type having a B-Tree
index (explicit or implicit) and in the presence of a wildcard character in the argument.
Sets the wildcard character as % in the ORDERS database.
[REV END]