[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | DECWINDOWS 26-JAN-89 to 29-NOV-90 |
| Notice: | See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit |
| Moderator: | STAR::VATNE |
|
| Created: | Mon Oct 30 1989 |
| Last Modified: | Mon Dec 31 1990 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3726 |
| Total number of notes: | 19516 |
3591.0. "DECWindos VooDoo kills Icon box" by SMPVAX::BLUNT (Growing older, but not up) Tue Nov 06 1990 00:59
Today, right at the "most critical time" after a powerfailure and
subsequent reboot, my customers VAXStation 3100m48 VAXCluster Console
lost what I call the "Icon Box." All the windows that had been created
"popped up" without their highlight/name bars. I couldn't access any
window to "pop" it to the surface, but the command "buttons" for each
window (when not occluded) worked correctly.
Now a little background; I'm dealing with a VAXCluster Console System
system, with VMS V5.3-2, 16mb of memory, three RZ23s, and the LARGE
monitor. We were just rebooting and had all the windows to all the
Cluster nodes (6 of 'em) "up." In this situation, there are too many
Icons to fit in the standard Icon box, so a scroll bar pops up on the
right edge. For ease of use, we expand the size of the Icon box to
eliminate the scrolling bar. Twice during the "resize," an operator
message brought up the OPA0 window. When the operator message appeared,
the Icon box (which was still in the process of being resized) just
flat disappears, and the screen takes on the appearance noted in the
first paragraph. First solution we tried was a reboot, but it isn't
acceptable, due to lost connections with the VCS "clients." Second
solution we tried was "Quitting" the session, and it, too, is unaccep-
table for the same reason.
Is there another bit of that 'ole DECWindows magic that can provide a
more acceptable recovery from this problem. I tried CSC, and they drew
a blank also (other than the things we tried)
Bob Blunt
SEGD/EIS
Iuka, MS
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3591.1 | | KONING::KONING | NI1D @FN42eq | Tue Nov 06 1990 12:30 | 4 |
| What you saw indicates that the Window Manager quit. You can rerun it to
recover, but of course you should find out what made it die and QAR accordingly.
paul
|
| 3591.2 | Some VCS hints | VINO::MCARLETON | Reality; what a concept! | Tue Nov 06 1990 13:52 | 33 |
| Re: .0
If you can get to the VCS icon, use MB2 to select SET HOST. This
should pop up a DECterm window over the other windows with a Username:
prompt in it. You can then log into the SYSTEM account and restart the
window manager. You may want to do something like this:
$create winmgr.com
$set display/create/node=0/transport=local
$run sys$system:decw$winmgr
ctrl-z
$run/detached/noauth/intput=winmgr.com/out=winmgr.log/process=winmgr -
_$ sys$system:loginout.exe
> Twice during the "resize," an operator message brought up the OPA0
> window.
I have my VS3100 VCS system set up with 'S3' set so that the printer
port is used as the alternate console. I have a VT330 connected to the
printer port to serve as the console for the VCS system. All OPA0:
messages show up on the VT330 and don't mess up my VCS display. Other
people have set up VMS to direct the OPA0: messages at the session
manager window. I don't know how to make this work.
I also have my icon box resized so that it is tall and narrow. Mine
is 132 pixels wide and 733 pixels tall and it sits on the left side of
the screen. This allows all of my CONNECT and MONITOR windows to stack
up from top to bottom on the left side of the screen. You can use the
resize button to stretch the icon box this way and then use Mouse
Button 2 in the icon window to save the settings.
Mike Carleton
VCS Project Leader
|