| Title: | VAX and Alpha VMS |
| Notice: | This is a new VMSnotes, please read note 2.1 |
| Moderator: | VAXAXP::BERNARDO |
| Created: | Wed Jan 22 1997 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 703 |
| Total number of notes: | 3722 |
Hi, OpenVMS VAX V6.2 a customer gets from time to time operator events like %%%%%%%%%%% OPCOM 20-MAR-1997 15:54:22.09 %%%%%%%%%%% (from node SERV02 at 20-MAR-1997 15:54:22.08) Message from user SYSTEM on SERV02 �<x98><x99>p<x99>�e�<HTJ><xA0>K<x80>T��<VTS>��<VTS>X?3Vte<OSC> %%%%%%%%%%% OPCOM 13-MAR-1997 00:19:09.83 %%%%%%%%%%% (from node SERV02 at 20-MAR-1997 00:19:09.81) Message from user SYSTEM on SERV02 �<x98><x99>p<x99>�e�<HTJ><xA0>K<x80>�<VTS>��<VTS>X>3Vte<OSC> After that, the console screen (VT420) is locked. An operator has to reset the screen. This messages do also appear with DECnet events 0.3 disabled. They appear only from node SERV02, not from node SERV01. Both nodes boot from the same system disk. (DSSI Cluster). On both systems is service enabled. There is no relationship between satellite booting and the operator messages. Some applikations, like Pathworks and an IBM terminal emulation are only started on node SERV02. Is there anybody who has had the same behavior? Regards Michael
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 530.1 | Find The Source... | XDELTA::HOFFMAN | Steve, OpenVMS Engineering | Fri Apr 25 1997 10:15 | 7 |
Find out what code -- it's probably an application or layered product -- is generating these OPCOMs, and fix it. Consider using use-of-privileges auditing -- for OPER -- and/or starting all but one of the installed products, until you can locate the code generating these OPCOMs. | |||||