Conference iosg::all-in-1_v30

3661.0. "CM_SITELOG.DAT not found and form CM$SITELOG2" by GIDDAY::SETHI (Recompense injury with justice) Tue Dec 14 1993 00:47

    Hi All,                  
    
    A customer has upgraded from 2.4 to 3.0 and is having a problem with
    the Customisation Management sub-system.  I have not found any notes or
    stars articles that remotely match the description of the problem.
    
    When the customer goes into the CM sub-system they get the following
    error:
    
    %OA-I-LASTLINE, Symbol OA$_SCM_ELE_NAM not found for form CM$SITELOG2
     %OA-I-LASTLINE, Symbol OA$_SCM_ELE_TYP not found for form CM$SITELOG2
     %OA-I-LASTLINE, Symbol OA$_SCM_ELE_LAN not found for form CM$SITELOG2
     %OA-I-LASTLINE, Symbol OA$_SCM_ELE_DATC not found for form CM$SITELOG2
    
    %OA-I-LASTLINE, Symbol OA$_SCM_ELE_AUT not found for form CM$SITELOG2
     %OA-I-LASTLINE, Symbol OA$_SCM_ELE_DISK not found for form CM$SITELOG2
     %OA-I-LASTLINE, Symbol OA$_SCM_ELE_LKFG not found for form CM$SITELOG2
     %OA-I-LASTLINE, Symbol OA$_SCM_ELE_DATM not found for form CM$SITELOG2
    
    followed by:
    
    %RMS-E-FNF, file not found
    -OA-E-DBEOR, Error opening CM$SITELOG - File
    USER2:[ALLIN1.DATA_SHARE]CM_SITELOG.DAT;
    -SYSTEM-W-NOSUCHFILE, no such file
    %OA-W-INVGET, Symbol "LAST_USER=CM$SITELOG.USER_EDITING[$CM_KEY]" not
    found
    %RMS-E-FNF, file not found
    -OA-E-DBEOR, Error opening CM$SITELOG - File
    USER2:[ALLIN1.DATA_SHARE]CM_SITELOG.DAT;
    -SYSTEM-W-NOSUCHFILE, no such file
    
    %RMS-E-FNF, file not found
    -OA-E-DBEOR, Error opening CM$SITELOG - File
    USER2:[ALLIN1.DATA_SHARE]CM_SITELOG.DAT;
    -SYSTEM-W-NOSUCHFILE, no such file
    
    I have found the Version 2.4 file called CM$SITELOG.DAT a 3.0 file has
    not been created.  The customer did not experience any problems during
    the upgrade and followed the CART faithfully.
    
    Please note that some of the error messages are missing for CM$SITELOG2
    I had a very bad dialin line.  I would be grateful for your help.
    
    Regards,
    
    Sunil
    
    PS - Sunil who has spent too much time away from ALL-IN-1 brains full
    of DEC MAILworks :-) !!!!

    sunil,
    
    CM$SITELOG *is* the v3.0 file - CM_SITELOG was the v2.4 one.
    
    The customer probably experienced a file conversion problem
    during A1$POSTINSTALL - you may find that rerunning it gives you an error
    such as CM028, CM035 etc...  there are STARS articles on the more
    popular ones.
    
    If not you can look up an article entitled something like
    Potential Customisation Management Error Messages
    or
    Preliminary document on migrating from CMA
    Both were really written by Simon Eijs and have yet to let me down
    
    I'd tell you more but some joker (idiot) has disabled my STARS account.
    so all this is coming purely from memory!!!
    
    From one of those you find a pointer to a .COM file called something
    like CM_POST_RUN.
    
    In that you comment out the scripts you need to run (the article will
    have told you which) e.g DO OA$LIB:CM_POST_CONVERT_SITELOG
    and then just run the .COm file and everything will be wonderful
    
    Or something like that anyway.
    
    regards,
    
    Andrew.D.Wicks
            

    Hi Andrew,
    
    The customer had no error messages when running the post-installation
    procedure.  I have asked the customer to rerun the post-installation
    procedure as it appeared that it had some how not touched CM even
    though it said it did.
    
    The customer is going to send me the logfile via x400 mail, I am unable
    to logon at the moment.
    
    Thanks for your help,
    
    Sunil