| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2941.1 | | SMAUG::MENDEL | In some strange power's employ | Fri Jun 15 1990 13:45 | 7 |
| Writing to the SM's terminal (usually TWA1:) causes the information
to be displayed, but it takes SHARE to access the device, and the
output is munged a little.
I think there's another note in here somewhere about this.
Kevin
|
| 2941.2 | Can anyone point to the note in question? | KYOA::KOCH | My brother did not lose the election | Fri Jun 15 1990 14:20 | 8 |
| > Writing to the SM's terminal (usually TWA1:) causes the information
> to be displayed, but it takes SHARE to access the device, and the
> output is munged a little.
> I think there's another note in here somewhere about this.
If anyone can point to the note, this would help. Wouldn't
a better mechanism be a mailbox?
|
| 2941.3 | Look at note 73. | TMIS01::DORON | Doing my BEST !!! | Sun Jun 17 1990 04:30 | 3 |
| I have just read note #73 that puts the opcom messages into the SM's window.
May be this could help.
*-Doron-*
|
| 2941.4 | | HKOVC::TERENCE | From Middlesex, UWO | Tue Jun 19 1990 04:37 | 13 |
| <<< Note 2941.0 by KYOA::KOCH "My brother did not lose the election" >>>
-< How to send messages to Session Mgr window? >-
> Can someone point or tell me how to send messages to the
> session manager window from DCL? I want to this from a
> non-priviledged user account. When I start an application,
> it tell me "Starting DECterm" and I want my command procedure
> which does this to send messages to the status window giving
> info on what's going on...
$ define sys$output TWAn:
$ write sys$output "Have a nice day"
$ deassign sys$output
|
| 2941.5 | | STAR::KLEINSORGE | Fred Kleinsorge, VMS Development | Tue Jun 19 1990 10:12 | 7 |
|
Note that .4 is a hack and depends on knowing that TWA1 (or whatever)
is the session manager. The TW device is likely to go away, and the
session manager/terminal emulator may use another psuedo device. So
be prepared for any such hack to break.
|
| 2941.6 | | SMAUG::MENDEL | In some strange power's employ | Tue Jun 19 1990 13:38 | 9 |
| >>> Note that .4 is a hack and depends on knowing that TWA1 (or whatever)
>>> is the session manager.
One could use f$pid to loop through the system for a process
whose image name was DECW$SESSION, or whose process name was
f$user(), and then get the physical terminal device name of that
process, which results in the "TWA1:" under normal circumstances.
This reduces the hack-factor a little.
|