HP 3000 Manuals HP 3000 Manuals
Utiltiy Program Operation (contd.)
Error Messages (contd.)
>>SHOW
[REV BEG]
Displays information about the database on a terminal or line printer.
This can include a list of processes that have the database open, the
status of locks in the database, the log identifier and flags, the
current buffer specifications, and the setting for the critical item
update option. Displays the capacity expansion information for the
database and the data sets. If you are using ALLBASE/Turbo CONNECT,
>>SHOW displays the names of any ALLBASE/SQL database environments
(DBEnvironments) to which the database is attached. This command should
be used with care because it obtains exclusive control of the database
for several seconds preventing all other access.
Syntax
{ALL }
{BUFFSPECS }
{CAPACITY }
{CIUPDATE }
{DEVICE }
{FLAGS }
>>SH[OW] dbname [.group[.account]] [/maint word] {LANGUAGE } [OFFLINE]
{LOCKS }
{LOGID }
{LOGINFO }
{MAINT }
{PASSWORDS }
{SUBSYSTEMS}
{USERS }
[REV END]
For example:
SHOW ORDERS/SELL ALL OFFLINE
where ORDERS is the database name and SELL is the maint word.
Parameters
dbname is the name of a TurboIMAGE/XL database root file
catalogued in the current session or job's account
and logon group. If you have account manager (AM)
capability, you can qualify the database with the
group name. If you have system manager (SM)
capability, you can qualify the database with the
group and account name.
group is the group where the database resides. To
qualify the database name by group, you must have
AM or SM capability. If you have AM capability and
want to qualify the database name by group, the
database must have a maintenance word as you will
be required to supply one.
account is the account where the database resides. To
qualify the database name by account, you must have
SM capability.
maint word is the current maintenance word for the database.
The database creator or the user with SM capability
can omit the maintenance word.
[REV BEG]
ALL displays all the information provided with MAINT,
BUFFSPECS, LANGUAGE, LOCKS, USERS, LOGID,
SUBSYSTEMS, FLAGS, and the last-stored date.
Displays number of detail data sets using dynamic
expansion capacity. Also, if the database is
attached to any ALLBASE/SQL database environments
(DBEnvironments) via the ALLBASE/Turbo CONNECT
product, the DBEnvironment names are displayed
(refer to the ALLBASE/Turbo CONNECT Administrator's
Guide for information).
BUFFSPECS displays the current buffer specifications which
can be either the TurboIMAGE/V default setting or
the values specified with the DBUTIL >>SET command
for those databases that will be migrated to MPE V;
the TurboIMAGE/XL default setting is not displayed.
Refer to the discussion of BUFFSPECS in the earlier
section on the >>SET command and also in "Moving
from MPE/iX to MPE V" in appendix H.
CAPACITY displays, for all data sets, capacity information
including dynamic capacity fields. Information
includes: data set name, type, number of entries,
entries as a percentage of the maximum capacity for
the data set, maximum capacity, current capacity,
initial capacity, incremental number of entries and
whether or not dynamic capacity expansion is used.
CIUPDATE displays the setting for the critical item update
option. Valid settings are DISALLOWED, ALLOWED,
and ON.
DEVICE displays the TurboIMAGE/XL root and data sets and
where files reside (device class name or logical
number) for a database.
FLAGS displays the state (enabled or disabled) of the
logging, roll-back, ILR, recovery, restart,
subsystem access, AUTODEFER, access, dumping,
HWMPUT, PREFETCH, MUSTRECOVER, and third-party
indexing (TPI) options. If MUSTRECOVER is enabled,
the flags option also displays a message if the
database needs recovery. In addition, it displays
the last database store date, and information on
whether the database has been modified since the
last-stored date (DBSTORE flag).
LANGUAGE displays state of the native language declaration
for the database.
LOCKS displays the status of locks currently obtained (or
requested).
LOGID displays the current MPE/iX log identifier for the
database.
LOGINFO displays information about all types of logging
available with TurboIMAGE/XL.
MAINT displays the maintenance word, if any.
PASSWORDS displays the access class numbers from 1 through 63
together with the passwords assigned to them. (You
must be the database creator.)[REV END]
SUBSYSTEMS indicates whether subsystems, including user
programs, can access the TurboIMAGE/XL database
and, if access is allowed, whether it is read only
or both read and write. Subsystem access is
enforced by the subsystem.
USERS displays a list of the processes that have the
database open with the program file name and other
information. (Refer to examples below.)
OFFLINE requests that the information be listed on the line
printer. The formal designator for the list file
is DBUTLIST. (Passwords and maintenance word will
not be printed.)
The >>SHOW database name USERS command can be executed at any time. The
remaining >>SHOW commands can be executed at any time except when another
process has the database opened in an exclusive access mode (mode 3 or
7).
Example (Show Users)
:RUN DBUTIL.PUB.SYS
:
>>SHOW ORDERS USERS
1 2 3 4 5
PIN PATH EXECUTING PROGRAM JOBNUM MODE
21 1 INVENTRY.IMAGE.DATAMGT #S116 1
22 1 BROWSE.IMAGE.DATAMGT #S118 5
28 1 BROWSE.IMAGE.DATAMGT #S112 5
29 1 INVENTRY.IMAGE.DATAMGT #S115 1
31 1 ORDENTRY.IMAGE.DATAMGT #S117 1
Example Discussion
The columns of information are described as follows:
1 The Process Identification Number (PIN). This is a number assigned to
a process by the operating system when the process is created. The
table above indicates that the process has opened the ORDERS
database.
2 The access path number. The access paths for each process are
numbered consecutively beginning with 1. Refer to the discussion of
access paths in chapter 4.
3 The name of the program file, its group and account.
4 The number of the job or session in which the process is running.
5 The access mode in which the database is open.
[REV BEG]
DBUTIL does not call DBOPEN so it is not listed as an executing program.
Example (Show All)
:
>>SHOW ORDERS ALL Display all information for ORDERS database.
For database ORDERS
MAINTENANCE WORD: SELL
Access is enabled.
Autodefer is disabled.
Dumping is disabled.
Rollback recovery is disabled.
Recovery is enabled.
ILR is disabled.
Mustrecover is enabled.
Logging is enabled.
Prefetch is disabled.
Indexing is disabled.
HWMPUT is disabled.
Restart is disabled.
Database last stored on MON, JAN 10, 1994, 1:09 PM
Database has not been modified since last store date.
Subsystem access is READ/WRITE.
CIUPDATE is disallowed.
Dynamic capacity expansion is used for 2 detail sets.
LOGID: ORDERLOG is valid
Password is correct
XM log set: default XM user log set for volume set volname
XM log set type: circular
XM log set size: 32 megabytes
The language is 0:NATIVE-3000
BUFFER SPECIFICATIONS:
50(1/120)
No other users accessing the database
>>
[REV END]
where volname is the name of the volume set in which the database
resides.
Example Discussion
The listing above indicates that the current buffer specifications
provide for 50 buffers to be allocated when there are between 1 and 120
concurrent users of the database. On TurboIMAGE/XL the buffer
specifications remain fixed, so the information shown in the above
listing is useful only for databases that will be migrated to an MPE V
system. The list above also shows that the database is enabled for
roll-forward recovery, logging, MUSTRECOVER, and user access. In the
example, PREFETCH and third-party indexing (TPI) are disabled, critical
item update (CIUPDATE) is disallowed, and the restart flag is disabled.
The restart flag is set by DBRECOV when the user has requested to suspend
recovery between log files. The logid is shown, the password is
verified, and the maintenance word is displayed. The messages that
appear during the SHOW command can vary depending on what information is
available on the database. If the maintenance word and logid are not
present, the following messages display:
Logid is not present.
Maintenance word is not present.
The message regarding the transaction manager (XM) log set will also
vary. The following message is printed if the database is not attached
to transaction manager:
XM log set: this database is not attached to an XM log set
The following message is printed if the database does not support NLS:
This database has been created before support of Native Languages.
If an error has occurred during dynamic roll-back recovery, the following
message is displayed:
Database is logically inconsistent.
The following message is printed if the database is attached to an
ALLBASE/SQL database environment (DBEnvironment) via the ALLBASE/Turbo
CONNECT (ATC) product:
Attached to these HP SQL DBEnvironments:
DBEname
DBEname
Refer to the ALLBASE/Turbo CONNECT Adminstrator's Guide for more
information.[REV BEG]
The example displays, "Dynamic capacity expansion is used for 2 detail
sets." Enable this feature for new databases by using the capacity
parameters for detail data sets. See chapter 3 for more information.
Enable this feature for existing databases by using DBChange Plus or a
third party utility. Refer to the MPE/iX Release 5.0 Communicator for
information on using DBChange Plus.
Example (Show Capacity)
:
>>SHOW ORDERS CAPACITY
No. of %Max --------------Capacity-------------- Dyn
Data Set Name Type Entries Cap Maximum Current Initial Increment Exp
CUSTOMER M 20 10 200 200 0 0 NO
DATE-MASTER A 111 53 211 211 0 0 NO
PRODUCT M 15 5 300 300 0 0 NO
SALES D 100 2 5012 140 140 70 YES
SUP-MASTER M 60 30 200 200 0 0 NO
INVENTORY D 4998 1 500000 5000 5000 10000 YES
>>
The example shows Maximum, Current, Initial and Increment Capacities.
The "%Max Cap" column shows how full the data set is as a percent of the
maximum capacity for that set. "Dyn Exp" column shows whether dynamic
capacity expansion is enabled or not. Enable this feature for new
databases by using the capacity parameters when defining detail data
sets. See chapter 3 for more information. Enable this feature for
existing databases by using DBChange Plus or a third party utility.
Refer to the MPE/iX Release 5.0 Communicator for information on using
DBChange Plus to specify expansion parameters for an existing
TurboIMAGE/XL database.
[REV END]
Format of Show Device List
The following example lists the TurboIMAGE/XL files for the ORDERS
database, along with the data set names and the device where each
resides. In the following example, the root file ORDERS and the data
sets are shown. The file devices are listed as specified with the device
class names. The ORDERS05 data set was moved using the DBUTIL >>MOVE
command to logical device number 3; the device class name is displayed.
Example (Show Device)
>>SHOW ORDERS DEVICE
For database ORDERS
Volume set: volname
MPE/iX File Name Data Set Name Device
ORDERS.IMAGE.DATAMGT DISC
ORDERS01.IMAGE.DATAMGT Date-Master DISC1
ORDERS02.IMAGE.DATAMGT Customer DISC1
ORDERS03.IMAGE.DATAMGT Product DISC1
ORDERS04.IMAGE.DATAMGT Sup-Master DISC2
ORDERS05.IMAGE.DATAMGT Inventory DISC3
ORDERS06.IMAGE.DATAMGT Sales DISC2
>>
where volname is the name of the volume set in which the database
resides.
Format of Show Locks List
DBUTIL lists the locking information sequentially by locking level:
database locks followed by data set locks, followed by data entry locks.
The names of locked entities (for example, the database, data set, or
lock descriptor for data entries) appear in uppercase followed by a list
of other processes waiting at that locking level. DBUTIL indicates in
lowercase the reason each process is waiting. This message is preceded
by a hyphen so that it can be identified on terminals or listings from a
line printer without lowercase.
If the term (PENDING) appears after a locked entity, it indicates that
the lock has been obtained but control cannot be returned to the caller
until other locks have been released. The same process identification
will appear elsewhere in the list together with an explanation of why it
is waiting.
Infrequently, the term (TEMP) may appear. TurboIMAGE/XL places a
temporary lock on a data set while it processes an existing data entry
lock request. Temporary locks occur only when a user requests data entry
locks on different items. Whenever the lock item changes, TurboIMAGE/XL
must wait until all existing locks on the current lock item are cleared
before it places a lock on the new lock item. During the wait the lock
is termed "TEMP." These locks are held very briefly and only under rare
circumstances. The Process Identification Numbers (PINs) and job/session
numbers listed are the same as those shown by MPE/iX commands, such as
SHOWJOB and SHOWQ.
Example 1 (Show Locks)
:
>>SHOW ORDERS LOCKS OFFLINE List the status of locks requested and held in the ORDERS database on the line printer.
The line printer listing looks similar to this:
HP30391C.00.00 TurboIMAGE/XL: DBUTIL THURS, SEP 21, 1989, 5:06 PM
For database ORDERS
PIN/ PROGRAM
LOCKED ENTITY - ( - waiting process) PATH NAME JOBNUM
1
DATA SET SALES 30/1 BROWSE #S126
2
-waiting for data set unlock: 17 INVENTRY #S128
-waiting for data set unlock: 32 ORDENTRY #S129
-waiting for data set unlock: 21 ORDENTRY #S118
3
DATA SET CUSTOMER 30/1 BROWSE #S126
DATA SET INVENTORY 30/1 BROWSE #S126
Example 1 Discussion
1 Indicates process 30 (program BROWSE executing in session 126) has
the SALES data set locked through access path 1.
2 Shows a queue of processes waiting for the SALES data set to unlock.
For example, in the first line, process 17 (program INVENTRY
executing in session 128) is waiting. Because it is listed first in
the queue, it will be the next process to resume execution after the
SALES data set is unlocked. It could be waiting to place a lock on
the data set or entries in the set.
3 Indicates process 30 (program BROWSE, session 126, access path 1) has
the CUSTOMER data set locked. No processes are waiting for the lock
to be released.
Example 2 (Show Locks)
Here is another example of a locking list that might appear when the
>>SHOW LOCKS command is entered.
HP30391C.00.00 TurboIMAGE/XL: DBUTIL THURS, SEP 21, 1989, 5:15 PM
For database ORDERS
PIN/ PROGRAM
LOCKED ENTITY - ( - waiting process) PATH NAME JOBNUM
1
DATABASE (PENDING) 22 BROWSE #S118
-waiting for zero locks within database: 22 BROWSE #S118
2
DATA SET INVENTORY 29/1 INVENTRY #S115
3
SALES: QUANTITY<= 50 28/1 BROWSE #S112
4
CUSTOMER: CUST-NAME = DON'S MERCANTILE 31/1 ORDENTRY #S117
Example 2 Discussion
1 Indicates process 22 (program BROWSE, session 118) has requested a
lock on the database and yet it cannot continue until existing locks
held in the database are released. In this example, the reason for
the pending lock is listed on the line below.
2 Indicates process 29 (program INVENTRY, session 115, access path 1)
has the INVENTORY data set locked.
3 Indicates that process 28 (program BROWSE, session 112, access path
1) has all entries in the SALES data set with QUANTITY less than or
equal to 50 locked.
4 Indicates process 31 (program ORDENTRY, session 117, access path 1)
has all entries in the CUSTOMER data set with LAST-NAME equal to
DON'S MERCANTILE locked.
All subsequent requests for locks must be made to wait until process 22
releases its database lock.
>>VERIFY
Reports whether a remote database-access (RDBA) file is activated or
deactivated and checks the validity of the RDBA file.
Syntax
>>V[ERIFY] database-access file name
For example:
VERIFY ORDDBA
where ORDDBA is the database-access file name.
Parameter
database-access file name is the name of a remote database-access file.
Example
:RUN DBUTIL.PUB.SYS Initiate DBUTIL execution.
:
>>VERIFY ORDDBA Enter >>VERIFY command and database-access file name.
Database-access file
ORDDBA is ACTIVATED
>>
When an RDBA file is activated, it is changed to a privileged file and
cannot be edited; it is changed back to an editor file when it is
deactivated.