HP 3000 Manuals HP 3000 Manuals
Tools on the Database Server
Monitoring Activity with HP GlancePlus/XL Program
HP GlancePlus/XL allows you to monitor a job, session, or process on
MPE/iX. The GlancePlus screens display statistics on how different system
resources are used. For information, refer to the HP GlancePlus/XL
User's Manual.
Monitoring ALLBASE/SQL Activity with SQLMON
SQLMON is a component of ALLBASE/SQL and monitors the activity of an
ALLBASE/SQL DBEnvironment. SQLMON summarizes the activity for the entire
DBEnvironment, or focuses on individual sessions, programs, or database
components. For information, refer to the ALLBASE/SQL Performance and
Monitoring Guidelines.
Avoiding Deadlocks with SET USER TIMEOUT
A non-detectable deadlock situation can occur when your application
software connects to multiple DBEnvironments at the same time. To avoid
a non-detectable deadlock situation, use the ALLBASE/SQL SET USER TIMEOUT
statement to specify the amount of time your application will wait if a
requested database resource is unavailable. For detailed information,
refer to the "SQL Statements" chapter in the ALLBASE/SQL Reference Manual
and the "Transaction Management with Multiple DBEnvironment Connections"
chapter in the ALLBASE/SQL Advanced Application Programming Guide.
If you think your application has encountered a deadlock situation, you
can use the ALLBASE/SQL TERMINATE USER statement to abort the client
connection.
Checking the Listener Log File
To check the listener log file, HPDANSLG (for NS) or HPDAARLG (for ARPA),
use the PRINT command. This can be done when the listener is not running
or if the listener was started with the DEBUG option. For example:
: PRINT HPDANSLG.PUB.SYS
The listener log file shows the date and time when the listener was
started or restarted. It then shows the client node name of the user
that has been successfully connected by the listener and the client
version. The client version indicates whether the client is on an MPE/iX
system (-) or on an HP-UX (*) system. Listener error codes are also
shown. Refer to the ALLBASE/SQL Message Manual for descriptions of
listener error codes.
The listener log file is a circular file that holds 1000 entries. The
last entry in the file is the most recent.
Here is an example of a typical listener log file:
MON, JUL 30, 1993. 9:01 AM: ***** ALLBASE / NET LISTENER *****
MON, JUL 30, 1993. 9:01 AM: - ALLBASE/NET LISTENER FOR ARPA IS
ALREADY ACTIVE.
MON. JUL 30, 1993. 9:05 AM: Client: #S54 Server: Client
NodeName: MATE.DBMS.HP Client Version: -CLIVER001
MON. JUL 30, 1993. 9:07 AM: Idtfy_clnt CF_GET_PROFILE
ClientNode MATE.DBMS.HP ClientLogin MANAGER.SYS.PUB
not found: 26002
MON. JUL 30, 1993. 9:07 AM: Hpdadvr IDTFY_CLNT: 26002
MON. JUL 30, 1993. 9:07 AM: Hpdadvr SHUTDOWN CIRCUIT
with error 26002
MON. JUL 30, 1993. 9:07 AM: Hpdadvr FATAL_ERROR
The first line of the listener log file shows the date and time of when
the listener was started.
The next line shows the date and time of an attempt to restart the
listener.
The following two lines show that a successful connection was made.
The last five lines show an unsuccessful attempt to make a connection.