| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 269.1 | | ZENDIA::DBIGELOW | Innovate, Integrate, Evaporate | Thu May 26 1994 20:45 | 14 |
| It should support LAT. We've seen a problem with the event window not
coming up properly, but the C3 should. We'll have to look into this.
As for converting from VCS, there is a program in the kit whick makes
an ascii file which you 'import' into the database from an option on
the File pulldown menu. The program is:
CONSOLE$IMAGE:CONSOLE$VCS_CONVERT.EXE
It will prompt you for the required inputs.
Cheers,
Dave
|
| 269.2 | | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Mon Jun 06 1994 19:06 | 8 |
| >Q1. PCM doesn't appear to like to display the C3 window using LAT, is
> this a restriction or am I doing something wrong ?
This is not a problem. The VT1200 and VXT 2000 are both LAT capable of
course. Can you post an error message or some such?
Regs,
Danm
|
| 269.3 | LAT C3 to remote VT1200 ACCVIOs | COMICS::V03W07::RINGI | Everyone thinks I'm paranoid | Thu Jul 28 1994 12:07 | 29 |
|
OpenVMS VAX V6.0
DECwindows Motif V1.1
POLYCENTER Console Manager V1.5
Running a command procedure with:
$ SET DISPLAY/CREATE/NODE=LAT_xxxxxxxxxxxx/TRANSPORT=LAT
$ CONSOLE C3
creates a display open on a VT1200, but then causes an access violation
reason mask = 01, virtual address = 201C00008, PC = 000284BE, PSL = 03C00000
Improperly handled condition, image exit forced.
No problems using,
$ SET DISPLAY/CREATE/NODE=LAT_xxxxxxxxxxxx/TRANSPORT=LAT
$ MC DECW$CLOCK
The problem only seems to be with the Console Manager.
Is this a known problem? If not, how can I trouble-shoot?
/Ian
|
| 269.4 | | OPG::PHILIP | And through the square window... | Thu Jul 28 1994 12:49 | 9 |
| Ian,
Does the same thing happen with the eventlist window?
Our C3 maintainer is out on holiday until next week,
can this wait until then?
Cheers,
Phil
|
| 269.5 | Fighting that Fire | COMICS::V03W07::RINGI | Everyone thinks I'm paranoid | Mon Aug 01 1994 16:24 | 14 |
|
Pardon my ignorance, but as the DAEMONS startup option starts the Console
Controller and ENS Daemons, doesn't the C3 failure stop the Eventlist from
starting? So would the following be valid:
$ CONSOLE EVENTLIST /NODE=display-name /TRANSPORT=LAT
I may well be supporting PCM, but I havn't actually got it installed anywhere
yet!!
/Ian
PS. When is the C3 maintainer back?
|
| 269.6 | | OPG::PHILIP | And through the square window... | Mon Aug 01 1994 16:31 | 21 |
| Ian,
The C3 maintainer should be back today, but he resides in the
U.S. so will actually start work any time now.
The C3 failure will stop the eventlist running in "C3" mode, that
is as a subprocess of the C3, however, you should be able to
execute an interactive eventlist via the
$ CONSOLE EVENTLIST/NODE=xxx/TRANSPORT=LAT
method, this will cause it to start in "interactive" mode.
What I am trying to determine here is if this is a C3 specific
problem or whether it is a problem with all the PCM X-Window
interfaces.
Cheers,
Phil
|
| 269.7 | Try this | ZENDIA::DBIGELOW | Innovate, Integrate, Evaporate | Mon Aug 01 1994 17:09 | 47 |
| Back. Not quite sure waht the probelm is. There's a debug you can turn
on. This should tell us approximately where the error is. try the
following command:
$ define CONSOLE$DEBUG C3
It will dump a lot of data to your terminal.
Optionally, (and a guess), you can cut and paste the following into a
file called CONSOLE$C3.DAT which must reside in your login dorectory.
HEADER:
X: 11
Y: 31
WIDTH: 521
HEIGHT: 411
PANE1_HEIGHT: 323
PANE2_HEIGHT: 53
HSCROLL: 75
VSCROLL: 0
BACKGROUND: #ABABC7C78282
PERIPHERAL_FOREGROUND: #F5F5EDED0000
AUTOSTART EVENT LIST: N
ICONIFY C3 AT STARTUP: N
CRITICAL_COLOR: #FFFF00000000
CRITICAL_BELL: 1
CRITICAL_VOLUME: 50
MAJOR_COLOR: #FFFF0000FFFF
MAJOR_BELL: 1
MAJOR_VOLUME: 50
MINOR_COLOR: #FFFFA5A50000
MINOR_BELL: 1
MINOR_VOLUME: 50
WARN_COLOR: #FFFFFFFF0000
WARN_BELL: 1
WARN_VOLUME: 50
CLEAR_COLOR: #0000FFFF0000
CLEAR_BELL: 1
CLEAR_VOLUME: 50
IND_COLOR: #ADADD8D8E6E6
IND_BELL: 1
IND_VOLUME: 50
KEEP_HIGHEST_PRIORITY: NO
ENS_TIMER: 30
SYSTEM_DLICK_OPTION: EVENT HISTORY
END:
|
| 269.8 | Eventlist accvios too | COMICS::V03W07::RINGI | Everyone thinks I'm paranoid | Tue Aug 02 1994 15:39 | 15 |
|
Following .-1.
The Eventlist experiment (.-2) returned:
CM Eventlist : Alloc colour (1) could not allocate colour Grey
Then Access violation.
Reason Mask = 01, Virtual Address = 201C0008, PC = 00021D16, PSL = 03C00000
Improperly handled condition, image exit forced.
|
| 269.9 | | OPG::PHILIP | And through the square window... | Tue Aug 02 1994 16:32 | 6 |
| Ian,
Is this a monochrome, or colour VT1200?
Cheers,
Phil
|
| 269.10 | | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Tue Aug 02 1994 19:36 | 4 |
| Uh.. there never was a color VT1200 to my knowledge. The first color
X-term we sold was the VT1300 followed by the VXT 2000.
Dan
|
| 269.11 | | OPG::PHILIP | And through the square window... | Tue Aug 02 1994 20:30 | 7 |
|
Well, I wasnt sure, the reason I ask is that the accvio is straight after
trying to allocate a color (Grey)!! Ah well, back to the drawing board.
Cheers,
Phil
|
| 269.12 | \ | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Wed Aug 03 1994 00:34 | 4 |
| Also, how much can you do about this since the product doesn't
support monochrome displays?
Dan
|
| 269.13 | | OPG::PHILIP | And through the square window... | Wed Aug 03 1994 10:35 | 10 |
|
We cant do anything, but its the only thing I can
think of which will cause this problem, we cant
reproduce it here on our VXT's and I havnt heard
of any other customers with this kind of problem
on VXT's.
Cheers,
Phil
|
| 269.14 | | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Wed Aug 03 1994 18:44 | 4 |
| We have a VT1200 around here some where. Just for grins I'll try it and
see what happens.
Dan
|
| 269.15 | Setting expectations | 42441::V03W07::RINGI | Everyone thinks I'm paranoid | Thu Aug 25 1994 11:59 | 206 |
|
Sorry, I'm still here...
Is this monochrome restriction doc'd in the SPD?
/Ian
BOPR> set display/create/transport=lat/node=lat_08002b1db233
BOPR> define console$debug c3
BOPR> console c3
C3: DEBUG enabled
C3: CM System List (5 systems in database)
BCOMMS
BCWHF1
BEV6
BSCS2
BWMU1
C3: Display name = _WSA24:
C3: Setting up Motif
C3: Turning on XSynchronize
C3: CONSOLE$USER_DEFAULTS not defined
C3: reading database from file wrkd$:[techsup]CONSOLE$C3.DAT
C3: Setting default values
1 priority color = Red
2 priority color = Magenta
3 priority color = Orange
4 priority color = Yellow
5 priority color = Green
6 priority color = LightBlue
C3: header dump
X ........................: 11
Y ........................: 31
Width ....................: 521
Height ...................: 411
Pane1_height .............: 323
Pane2_height .............: 53
H scroll bar .............: 75
V Scroll bar .............: 0
Background ...............: 1
Autostart Event List .....: 0
Iconify at startup .......: 0
Critical color ...........: 0
Critical bell count ......: 1
Critical bell volume .....: 50
Major color ..............: 1
Major bell count .........: 1
Major bell volume ........: 50
Minor color ..............: 0
Minor bell count .........: 1
Minor bell volume ........: 50
Warn color ...............: 1
Warn bell count ..........: 1
Warn bell volume .........: 50
Clear color ..............: 1
Clear bell count .........: 1
Clear bell volume ........: 50
Indeterminate color ......: 1
Indeterminate bell count .: 1
Indeterminate bell volume : 50
Keep highest Priority ....: 0
ENS Timer ................: 30
Double Click option ......: 0
C3: Icon record
type ...........: 2
name ...........: BCOMMS
info ...........:
pixmap_filename : GENERIC.XBM
State ..........: UNKNOWN
label widget ...: 0
pixmap .........: 0
bitmap .........: 0
gc .............: 0
x ..............: 10
y ..............: 50
width ..........: 0
height .........: 0
lock widget ....: 0
last_priority ..: 0
break_key ......: P
escape_key .....: G
exit_key .......: E
refresh ........: W
C3: Icon record
type ...........: 2
name ...........: BCWHF1
info ...........:
pixmap_filename : GENERIC.XBM
State ..........: UNKNOWN
label widget ...: 0
pixmap .........: 0
bitmap .........: 0
gc .............: 0
x ..............: 98
y ..............: 50
width ..........: 0
height .........: 0
lock widget ....: 0
last_priority ..: 0
break_key ......: P
escape_key .....: G
exit_key .......: E
refresh ........: W
C3: Icon record
type ...........: 2
name ...........: BEV6
info ...........:
pixmap_filename : GENERIC.XBM
State ..........: UNKNOWN
label widget ...: 0
pixmap .........: 0
bitmap .........: 0
gc .............: 0
x ..............: 184
y ..............: 50
width ..........: 0
height .........: 0
lock widget ....: 0
last_priority ..: 0
break_key ......: P
escape_key .....: G
exit_key .......: E
refresh ........: W
C3: Icon record
type ...........: 2
name ...........: BSCS2
info ...........:
pixmap_filename : GENERIC.XBM
State ..........: UNKNOWN
label widget ...: 0
pixmap .........: 0
bitmap .........: 0
gc .............: 0
x ..............: 269
y ..............: 50
width ..........: 0
height .........: 0
lock widget ....: 0
last_priority ..: 0
break_key ......: P
escape_key .....: G
exit_key .......: E
refresh ........: W
C3: Icon record
type ...........: 2
name ...........: BWMU1
info ...........:
pixmap_filename : GENERIC.XBM
State ..........: UNKNOWN
label widget ...: 0
pixmap .........: 0
bitmap .........: 0
gc .............: 0
x ..............: 354
y ..............: 50
width ..........: 0
height .........: 0
lock widget ....: 0
last_priority ..: 0
break_key ......: P
escape_key .....: G
exit_key .......: E
refresh ........: W
C3: HOME defined as wrkd$:[techsup]
C3: Message log filename = wrkd$:[techsup]CONSOLE$C3_TECHSUP_msg.log
C3: Wed Aug 3 12:04:38 1994: Known configuration:
C3: System count: 5
C3: Peripheral count: 0
C3: Text count: 0
C3: Line count: 0
C3: setting MDS default values
C3: Initing CM icon
%SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=201C0008, PC=000284BE, PSL=03C00000
Improperly handled condition, image exit forced.
Signal arguments Stack contents
Number = 00000005 00000000
Name = 0000000C 201C0000
00000001 7FF16844
201C0008 00000000
000284BE 201C0000
03C00000 7FF16844
7FF16824
0002886E
00401E10
00401E10
Register dump
R0 = 004079F8 R1 = 8083A000 R2 = 201C0000 R3 = 00401E10
R4 = 00000ED8 R5 = 00000200 R6 = 00000000 R7 = 000043A8
R8 = 00003D90 R9 = 00000001 R10= 00003850 R11= 00000000
AP = 7FF16720 FP = 7FF166E0 SP = 7FF1675C PC = 000284BE
PSL= 03C00000
BOPR> lo
TECHSUP logged out at 3-AUG-1994 12:04:57.20
|
| 269.16 | | OPG::PHILIP | And through the square window... | Thu Aug 25 1994 12:23 | 11 |
| Ian,
Yes, the monochrome restiction is in the SPD
(or was last time I looked).
Dan,
Did you manage to check this out?
Cheers,
Phil
|
| 269.17 | SPD | COMICS::V03W07::RINGI | Everyone thinks I'm paranoid | Thu Aug 25 1994 16:10 | 20 |
|
SOFTWARE COMPONENTS
PCM consists of the following components:
.
.
.
o Central Control Coordinator (C3) Interface - An X-Windows OSF/Motif[R]
interface that provides a logical view of the controlled systems.
From this interface, system managers can monitor all console ac-
tivities and respond to events detected on the console. Console events
are reflected by the node icons in the display and direct the sys-
tem manager to systems needing attention. Other interactive inter-
faces can also be activated from the central control coordinator
Interface.
Note: Only Color Graphic display terminals are supported.
/Ian
|
| 269.18 | | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Thu Aug 25 1994 19:45 | 7 |
| >Did you get a chance to try this.
Yep! And the C3 isn't very useful either! Matter of fact it also
accvio'd!
Regs,
Dan
|