[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | POLYCENTER Console Manager |
Notice: | Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS: |
Moderator: | CSC32::BUTTERWORTH |
|
Created: | Thu Aug 06 1992 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 1541 |
Total number of notes: | 6564 |
170.0. "Debugging Console Manager" by ZENDIA::DBIGELOW (Innovate, Integrate, Evaporate) Thu Jan 20 1994 15:41
To turn on debugging, use the following:
OpenVMS
=======
Define/System CONSOLE$DEBUG xx
OSF/1 & ULTRIX
setenv CONSOLE_DEBUG xx
Do the definition BEFORE you start Console Manager (on any
platform).
The value of xx will be a string containing one or more
of the following items (some are self explanatory, the
others I will indicate what they do)...
ALL - this turns on everything, effectively all
the ones below
API - debugging for the callable interface
ENS - for ENS
SHM - for the shared memory routines
C3 -
EVENTLIST -
DAEMON - Console controller daemon - LOTS
of meaningless output, be carefull!!
EDIT - Both editors, doesnt do much except
create a backup copy of the database
when it is opened.
Some of these will screw up the user interfaces, e.g. defining
ALL the doing a connect will cause your screen to display a
lot of meaningless data and your console output will be lost
somewhere amongst it.
Subsequent baselevels, releases of the software will increase
the size of this list and the amount of data output.
Please try to keep this internal to digital, I dont want
lots of SPR's saying performance is lousy because someone
has turned this stuff on!!
Oh yeah, the definitions are case sensitive on ALL platforms,
Uppercase is a must.
Cheers,
Phil
T.R | Title | User | Personal Name | Date | Lines
|
---|