Conference vaxaxp::vmsnotes

541.0. "operator.log missing" by MSAPG1::ENG () Mon Apr 28 1997 10:06

Hello all, I have a new installation for OpenVMS V6.2-1H3 on AXP Server 4100
SCSI Cluster. I have noticed that the sys$manager:operator.log file is not 
generated everytime system reboot at both nodes. But if I force it to create 
one by REPLY/ENABLE and REPLY/LOG, then only the operator.log file will be 
created until next reboot.

Is is normal for V6.2-1H3 SCSI Cluster ? The processes that are running are
listed at the end of this mail. Any help will be very much appreciated.

Best regards,
-Eng-

$ sho sys
OpenVMS V6.2-1H3  on node JEDI  22-APR-1997 15:02:35.52  Uptime  0 01:34:32
  Pid    Process Name    State  Pri      I/O       CPU       Page flts 
 Pages
20800401 SWAPPER         HIB     16        0   0 00:00:09.00         0 
     0
20800405 CONFIGURE       HIB      8       10   0 00:00:00.01        31 
    15
20800407 IPCACP          HIB     10       14   0 00:00:00.01        34 
    39
20800408 ERRFMT          HIB      8       70   0 00:00:00.06        46 
    60
20800409 CACHE_SERVER    HIB     16        3   0 00:00:00.00        24 
    34
2080040A CLUSTER_SERVER  HIB      8       15   0 00:00:00.02        55 
    82
2080040B OPCOM           HIB      7      373   0 00:00:00.12        70 
    34
2080040C AUDIT_SERVER    HIB      9      108   0 00:00:00.15       148 
   165
2080040D JOB_CONTROL     HIB      9      143   0 00:00:00.04        48 
    67
2080040E SECURITY_SERVER HIB     10       96   0 00:00:00.15       243 
   350
2080040F SMISERVER       HIB      9       41   0 00:00:00.08       111 
   143
20800410 TP_SERVER       HIB      8      381   0 00:00:00.62        71 
    88
20800413 LATACP          HIB     14       11   0 00:00:01.81        77 
    63
20800414 UCX$INET_ACP    HIB     10        8   0 00:00:00.02        73 
    35
20800415 RDMS_MONITOR    LEF     15      131   0 00:00:00.25       740 
    25
20800417 DECW$SERVER_0   HIB      6     1995   0 00:01:48.01       740 
   884
20800418 DTSESSION       LEF      6      901   0 00:00:00.95       827 
   387
2080041A WSREPORT        LEF      4     2074   0 00:00:02.24      3205 
   163
2080041B STUDENT1        LEF      6     3133   0 00:00:02.99      1941 
  2704
2080041F DTWM            COM      4     3497   0 00:00:09.98       665 
   802  S
20800421 DECW$TE_0421    COM      4      260   0 00:00:05.65       598 
   609
20800422 _FTA1:          LEF      8     8443   0 00:00:06.43     10759 
   121
2080042D NETACP          HIB     10      638   0 00:00:00.25        49 
    86
2080042E EVL             HIB      4      981   0 00:00:00.29        96 
    98  N
2080042F REMACP          HIB      8       18   0 00:00:00.00        33 
    22
20800437 CPOPER          LEF      6     1729   0 00:00:02.28      2360 
  3224
2080043E _FTA2:          CUR      7      602   0 00:00:00.67      1302 
    96

   Look for any dump files from OPCOM in SYS$SYSROOT:[*...], and look for
   odd settings in the SYLOIGICALS.COM procedure.

   There are some OPCOM-related ECO kits out -- some are rolled into kits
   for shadowing.  See the http://www.service.digital.com patch area.

    Eng,
    
    does this machine have a graphic adapter installed ? If so, the startup
    code thinks it's a workstation and disables the operator logfile. Edit
    SYLOGICALS.COM and add:
    
    	$ DEFINE/SYTEM OPC$LOGFILE_ENABLE TRUE
    
    And check the other OPC logicals, if you want anything else.
    
    Volker.

    Check this:
    
    $ write sys$output f$device("*","workstation","decw_output")
    
    If the output of this command is non-empty, VMS$DEVICE_STARTUP.COM
    will consider this node to be a WORKSTATION and will disable the
    operator logfile, disable OPA0 as operator console and
    SET TERM/NOBROADC OPA0:
    
    Volker.