| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 657.1 | try this | LESLIE::LESLIE | Andy ��� Leslie, CSSE | Sun Apr 23 1989 13:54 | 38 |
| $ set proc/priv=(oper,security) ! Necessary Privs
$
$! This command procedure should disable OPCOM output to OPA0
$! and enable it to the Session Manager Window. If you wish put these
$! three lines in your systartup_v5.com
$
$! They become redundant with VMS 5.2's treatment of OPCOM messages
$! on workstations in clusters and use of the new OPCOM logical names.
$
$ define sys$command opa0:
$ reply/disable
$ deassign sys$command
$
$loop: ! Ensures job isn't already running, and if it is, kills it.
$ pid = F$PID (context)
$ IF pid .EQS. "" THEN GOTO a_ok
$ IF F$GETJPI ("''pid'", "PRCNAM") .EQS. "Opcom2sm"
$ THEN
$ stop/id='pid'
$ goto a_ok
$ Endif
$ goto loop
$a_ok:
$ set proc/name="Opcom2sm"
$ Wait 00:01:00
$ SessionProcess = F$GetJpi( "", "Owner" )
$ Loop2:
$ Terminal = F$GetJpi( SessionProcess, "Terminal" )
$ If Terminal .nes. "" then goto TerminalKnown
$ Wait 00:00:05
$ Goto Loop2
$ TerminalKnown:
$ Define Sys$Command 'Terminal'
$ Reply/Enable
$ Deassign Sys$Command
$ X = F$SetPrv (Old_priv)
$ Exit
|
| 657.2 |
Will this help? | FUEL::graham | if ya want home cookin, stay home | Mon Apr 24 1989 18:58 | 19 |
|
re .0
>We are logging console messages to the screen (usually DECnet adjacency
>messages)....
> How do I turn of the console messages to the screen? Is this
> documented?
My knowledge of VMS 'things' is very little - but this is what I do to turn off
decnet console messages off under decnet-ultrix.
ncp define known logging state off
ncp set known logging state off
Also, X11 has a utility (for UNIX systems) called xcons that helps to direct
console messages to a terminal window. Is this available for VMS?
Kris..
|
| 657.3 | The real problem with the vertical stripes may lie with DECwindows | 42143::PITT | It's all in the dots .. ... .. . .. ... | Wed Apr 26 1989 11:50 | 16 |
| I'm interested to read the problem with vertical stripes, because I have seen it
too. I am running T5.2-413 on a VS3500. Initially I thought it must be a
memory problem, but now I'm not so sure. Incidentally, I QAR'ed it today in the
V52-IFT database, as number 281, just for the record. I hadn't noticed that it
was associated with use of the operator window, but it could be ... Anyone else
seen it?
Maybe also in the same area is a little problem with the keyboard that occurred
yesterday: I suddenly found that the Find/Insert/Remove/Select/Prev/Next keys
and the arrow keys did not work: hitting any one of them simply turned on the
"Wait" light on the keyboard. The same problem occurred with another keyboard.
Rebooting "fixed" the problem. Again, my first thought was a memory problem on
the VAXStation, but maybe not?
T
|
| 657.4 | | AITG::DERAMO | Daniel V. {AITG,ZFC}:: D'Eramo | Wed Apr 26 1989 20:00 | 16 |
| re .3
Maybe also in the same area is a little problem with the keyboard that occurred
yesterday: I suddenly found that the Find/Insert/Remove/Select/Prev/Next keys
and the arrow keys did not work: hitting any one of them simply turned on the
...
The loss of those keys usually means that you pressed ctrl-F3
(it's next to ctrl-F2 which toggles the operator window). Ctrl-F3
toggles you into and out of a state where the arrow keys move the
mouse (with eventual auto-repeat), and I suppose the Select key
acts like pressing the left button, etc. I thought that the wait
light stayed on when in that mode, though.
Dan
|
| 657.5 | Can't get command procedure to work | DEDLNE::SYSTEM | | Fri Jan 12 1990 12:22 | 11 |
| I tried running the command procedure posted in this note, and I can't seem
to get it to work. I ran it from a DCL command menu, and it disabled the
OPCOM messages, but it is not putting them in the session manager, or anywhere
else. Am I supposed to run the procedure before calling up DECwindows, or am
I doing something else wrong?
I have a VX3100, VMS 5.3, DW 2.0.
Thank you.
Andrew Richmond
|
| 657.6 | | QUARK::LIONEL | Free advice is worth every cent | Fri Jan 12 1990 13:22 | 29 |
| Here's what I do.
SYS$MANAGER:SYLOGICALS.COM is:
$ define/system opc$opa0_enable "FALSE"
$ exit 1
Then from my DECW$LOGIN.COM, I spawn the following:
$ Set Process/Name="SM_Opcom"
$ Wait 00:02:00 ! Wait for Session Manager to get Started
$ SessionProcess = F$GetJpi( "", "Owner" )
$ Loop:
$ Terminal = F$GetJpi( SessionProcess, "Terminal" )
$ If Terminal .nes. "" then goto TerminalKnown
$ Wait 00:00:05
$ Goto Loop
$ TerminalKnown:
$ Set Proc/Priv=(Oper,Security)
$ Def/User Sys$Command 'Terminal'
$ Reply/Enable
$ Set Proc/Priv=(NoOper,NoSecurity)
$ Exit
Andy's command procedure seems to be trying to do the above from SYSTARTUP -
I can't tell you why it doesn't work. But the above works for me.
Steve
|