Conference orarep::nomahs::dec_data_distributor

201.0. "Monitor process fails with FILE_IO_ERROR" by CSC32::HENNING (A rose with no thorns) Tue Apr 02 1996 15:19

    Hi,
    
    A customer who *just* installed DDAL V6.0 on his system is executing 
    DDAL$START_TR_MON to start the transfer monitor.  No errors occur
    during execution of the procedure, but the monitor process is
    immediately deleted.  The log file includes these lines:
    
    %DDAL-E-FILE_IO_ERROR, file IO error was encountered with log file
    -DDAL-E-CANT_WRITE_LOG_, cannot write to the log file
    -CMA-W-NORMAL, normal successful completion
    -PRV-W-NORMAL, normal successful completion
    %RDB-F-BUG_CHECK, internal consistency check failed
    -DDAL-I-BUGFILCRE, Data Distributor bugcheck dump file
    SYSENG$DISK1:[TRDB]DDAL_BUGCHECK.DMP;1 was created
    -DDAL-E-FILE_IO_ERROR, file IO error was encountered with log file
    -DDAL-E-CANT_WRITE_LOG_, cannot write to the log file
    -RMS-E-CRE, ACP file create failed
    -NONAME-W-NOMSG, Message number 00000000
    -SYSTEM-F-BADOWNER, owner UIC is invalid; object ownership not changed
    -ECWP-W-NORMAL, normal successful completion
    
    The system is running OpenVMS VAX V6.1, Rdb V6.1.
    
    The BADOWNER message may reflect an invalid 'account' identifier 
    (ie. [100,*]).  Am checking with customer on this. 
    
    The messages came from the monitor log file -- to which "log file" do
    the FILE_IO_ERROR and CANT_WRITE_LOG_ messages refer?
    
    
    Thanks for your help,
    Mary

    
    The FILE_IO_ERROR and CANT_WRITE_LOG messages apply to the transfer
    monitor's log file.  The transfer monitor's log file location is
    specified by the customer as one of the parameters in the command
    procedure DDAL$START_TR_MON.COM.  Check protections on that directory.
    Also, if a search-list logical is used rather than a straight directory
    specification, maybe that will give problems.