| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 508.1 | A possibility | ZENDIA::DBIGELOW | Innovate, Integrate, Evaporate | Thu Dec 08 1994 01:55 | 22 |
| Arlan,
The most your customer can do is to pariallly monitor the PCM
platform. However, the most that they would be able to do is to monitor
their own console events and the only way that comes quickly to mind
is to create a psuedo-terminal which invoke 'reply/enable' This would
cost them 1 license unit which they may or may not deem valuable.
They would only be getting one half of the functionality. That is, they
could not connect to the console to perform any maintence type work on
the system, such as halting and rebooting. (Well, they could halt it
but it would be suicidal).
If you can verify that they do have a console port on the back of
the PCM host platform, then the real way to go is to install PCM on
another platform and have that system monitor the PCM system. They
could redirect the product's functionality back to the host platform
through the use of DECwindows. The cost would be the same but the
functionality would be more robust.
Hope this helps. Perhaps others might have some alternate solutions.
Dave
|
| 508.2 | console ?? | 17219::LEEDS | From VAXinated to Alphaholic | Thu Dec 08 1994 20:06 | 19 |
| According to the Alphanotes conference, the 3000 does have a serial console
port which can be enabled by changing a jumper on the mother board. I'm not
sure what else it affects when this jumper is changed - ie: does it disable
something PCM might need (like the graphics head) ???
<<< VAXAXP::NOTES$:[NOTES$LIBRARY]ALPHANOTES.NOTE;1 >>>
-< Alpha Support conference >-
================================================================================
Note 3976.1 DEC3000/300X console port? 1 of 3
IJSAPL::KNOL "isn't every bug a bit wrong" 9 lines 21-JUN-1994 02:00
-< yes you can use it >-
--------------------------------------------------------------------------------
A 3000-300 has an alternate console port, you have to change a jumper
on the systemboard. If used as a server box without "head, kbd and
mouse,you have to install a 15 pin D-plug on the keyboard/mouse
connector with pins 2 and 3, 6 and 7 connected, otherwise the system
won't auto_boot (fails kbd/mouse test 50)
|
| 508.3 | | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Thu Dec 08 1994 22:31 | 27 |
| > ie: does it disable something PCM might need (like the graphics head) ???
No it doesn't. What happens is the OPA) device is now the serial port
instead of the graphics head. Motif will still operate normally.
To further build upon what Dave said...
People wanted to do the same things with VCS. Let's say you wire the
console to a decserver port and then configure the system into the PCM
config so that the PCM engine is now managing it's own console. Guess
what happens if the PCM engine hangs or gets into a situation where you
must manually reboot it from the console? Since you no longer have PCM
running to access the PCM engines console, your forced to bring a
terminal over and plug it into the console port and deal with the
situation. The bottom line is - don't do it!!! Do what
Dave said and create a pseudo-node that runs a command file that does
SPAWN followed by REPLY/ENABLE. You can now scan all OPCOM messages
etc. for events. If the customer pushes back and mentions hardware
specific messages such as HALT codes the reponse is as above. If the
machine running PCM halts and it's montoring itself it can't
detect the event anyway since PCM is no longer running!!!!!!
Now it is fully legal for two different PCM engines to manges each
others console.
Regs,
Dan
|