[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 |
2920.0. "set display creates invalid WSA device" by TINCUP::KOLBE (The dilettante debutante) Tue Jun 12 1990 19:47
I'm having a problem with the set display command. I start two sessions
with autostart that use the command file below. The first window that
comes up works fine. The second window, and any subsequent windows, have
invalid WSA devices. I use this same procedure with a submit/remote to
create sessions on my boot node and they work fine and get valid WSA
devices.
When I do a show log DECW$DISPLAY I'll get back a value but a show
device WSA will not list it. The window this creates works like a
DECterm while the first window that comes up, with the valid WSA
device, works fine as a DW window. The other valid WSA device in the
example I show is attached to a DECtse window which always seems to
work even thought it just does a create/term.
Is there a sysgen parameter or some other control that determines how
many WSA devices I can create? Why don't I get an error message
instead of a phoney device? liesl
"DECW$DISPLAY" = "_WSA10:" (LNM$JOB_8043F610)
Device Device Error
Name Status Count
WSA0: Offline 0
WSA1: Online 0
WSA8: Online 0
$!
$ set verify
$ def sys$print nl:
$!
$ set display/create/node=xaipe
$ wait 0:0:10
$!
$ node = f$getsyi("nodename")
$!
$ x_position = 0
$!
$ if node .eqs. "GLDCMP" then x_position = 56
$ if node .eqs. "PITKIN" then x_position = 86
$!
$ create/term -
/detach -
/wind=(title="''node'", -
x_position='x_position', -
rows=35, -
icon="''node'")
$!
T.R | Title | User | Personal Name | Date | Lines |
---|
2920.1 | ?EXEC fixed it | TINCUP::KOLBE | The dilettante debutante | Wed Jun 13 1990 14:11 | 2 |
| Well, we found it. The /EXEC was not used on the set display and this
caused the problem. liesl
|