| 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 |
Hello, I have read the replies to 1972, 1910 & 1857 and they all deal with this however in those cases they were trying to figure out how to disable OPA0 and I am trying to figure out how to re-enable it... I have a VAXstation II that I have been using with OPA0 enabled (I have a printer connected to the console port and like to have a record of my OPCOM messages go there). I just recently however reconfigured the system and added another workstation thus making it now a cluster and the VAXstation II became the boot node. From what I have gleamed in the previous replies the VAXcluster software is more clever now (5.3) and assumes that if you are in a cluster and are a workstation then you don't want opcom messages to OPA0. While I realize this is great for most people (I perfer this for my satelite workstation too) I can't figure out how to re-enable them on the boot node. I have tried the following.... SET TERM OPA0:/BROAD/BRDCSTMBX/PERM DEFINE/SYSTEM OPC$OPA0_ENABLE T I am now thinking that my problem may be a sysgen parameter WS_OPA0 this is currently 0 is that it? Thanks and regards, Peter BTW - In case you are wondering I have discovered that booting the VAXstation II from a dumb terminal attatched to the console port (you have to press BREAK first) allows you to log in etc and then once the system is up I disconnect the VT220 and connect a printer and VIOLA I have hardcopy for my opcom messages and my workstation screen was no longer trashed either.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1982.1 | STAR::MCLEMAN | Jeff McLeman, VMS Development | Mon Jan 01 1990 13:39 | 3 | |
Try putting the OPC$OPA0_ENABLE equal to TRUE in SYLOGICALS.COM in
SYS$MANAGER. THis will execute before opcom starts.
| |||||
| 1982.2 | Do I need to reboot?? | MUTTON::LAMB | Peter Lamb - FSG Santa Clara | Tue Jan 02 1990 15:39 | 6 |
> Try putting the OPC$OPA0_ENABLE equal to TRUE in SYLOGICALS.COM in
> SYS$MANAGER. THis will execute before opcom starts.
To get this to work do I then have to reboot?
Peter
| |||||
| 1982.3 | STAR::MCLEMAN | Jeff McLeman, VMS Development | Tue Jan 02 1990 15:45 | 1 | |
Yes. | |||||
| 1982.4 | Still no go | PJVAX::LAMB | Peter Lamb - FSG Santa Clara | Fri Jan 05 1990 01:27 | 20 |
Hello,
It still doesn't work! Below I have a copy of my SYLOGICALS.COM
Also after I boot I SET TERM OPA0:/BROAD/BRDCSTMBX/PERM
$!
$ A=f$logical("SYS$NODE")
$ LOC = F$LOCATE(":",A)
$ node=F$EXTRACT(1,LOC-1,A)
$ if (node .eqs. "PJVAX") THEN DEFINE/SYSTEM OPC$OPA0_ENABLE TRUE
The node name is PJVAX and when I do a sho logical after the boot
it is defined as true.
Any other ideas?
Regards,
Peter
| |||||
| 1982.5 | UFP::MURPHY | A bug? Use the source, Luke! | Sun Jan 07 1990 11:14 | 1 | |
Don't set it BRDCSTMBX. | |||||
| 1982.6 | f$GETSYI("SCSNODE") | DCWS06::RIMMER | Schaung ma moi, gei........ | Mon Jan 08 1990 06:48 | 10 |
Re .4 Is SYS$NODE really defined by the time SYLOGICALS is run? It's normally defined when starting the network so unless you're running STARTNET in SYLOGICALS there's something amiss here. A safer option for clusters is to use SCSNODE to provide you with the current nodename. hth - Marcus | |||||